Skip to main content
Node type: close_browser · Version: 1 · Category: Browser Close the active managed session. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Release a managed session before a long non-browser tail of the workflow.
  • Make the intended browser lifecycle explicit in the graph.

​
Example: Close after capturing evidence

Place Close Browser after the final Screenshot or Download File node.
  1. Connect it in the same control path as Open Browser.
  2. Ensure no later node needs the session.
  3. Keep Open Browser’s automatic cleanup enabled as a failure-path fallback.

​
Configuration

Any remaining managed sessions are cleaned up when the workflow ends.

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • The active managed session is closed and cannot be used by later browser actions.
  • Workflow-end cleanup still handles remaining sessions when automatic cleanup is enabled.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • A browser node after Close Browser fails because its session context is gone.
  • Close Browser is useful for clarity, but it should not be the only cleanup protection.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Managed browser worker

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.