Open Browser

Node type: open_browser · Version: 1 · Category: Browser Start a managed Chromium 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

Start the managed session required by downstream browser actions.
Reuse an isolated profile for sites that need persisted sign-in state.

Example: Open a headless reporting session

Use a prepared profile, a 1280 by 800 viewport, and a ten-minute session cap.

Example settings

{
  "profileId": "reporting-profile",
  "headed": false,
  "initialUrl": "https://portal.example.com",
  "viewport": {
    "width": 1280,
    "height": 800
  },
  "defaultTimeoutMs": 30000,
  "closeAutomatically": true,
  "keepOpenAfterManualTest": false,
  "maximumDurationMs": 600000
}

This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector. Local paths must be selected, mapped from a trusted path, or covered by the runner’s approved boundary.

Create and test an isolated profile in Settings.
Place Open Browser upstream of every browser action.
Leave automatic cleanup enabled for scheduled and failure paths.

Configuration

Field	Type	Default	What it controls
`profileId`	string	`""`	Managed browser profile selected in Settings.
`headed`	boolean	`true`	Show the managed browser during a manual run. Scheduled runs default to headless.
`initialUrl`	string	`""`	Optional first URL opened with the session.
`viewport`	object	`{"width":1280,"height":800}`	Browser viewport width and height. The editor accepts 320–3840 by 240–2160 pixels.
`defaultTimeoutMs`	number	`30000`	Default browser operation timeout, from 100 to 120000 milliseconds.
`closeAutomatically`	boolean	`true`	Clean up the session when the workflow succeeds or fails.
`keepOpenAfterManualTest`	boolean	`false`	Keep a manually tested session open for inspection.
`maximumDurationMs`	number	`1800000`	Maximum managed browser session duration.

Create an isolated browser profile in Settings before running this node.

Sessions are cleaned up after success or failure when closeAutomatically is enabled.

Workflow JSON

The editor stores this node with the following implemented default configuration:

Default node configuration

{
  "type": "open_browser",
  "version": 1,
  "configuration": {
    "profileId": "",
    "headed": true,
    "initialUrl": "",
    "viewport": {
      "width": 1280,
      "height": 800
    },
    "defaultTimeoutMs": 30000,
    "closeAutomatically": true,
    "keepOpenAfterManualTest": false,
    "maximumDurationMs": 1800000
  }
}

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

Port	Type	Required	Description
`result`	`any`	No	Result

Execution behavior

The node establishes session context used by downstream browser nodes in the same control path.
Manual runs can be headed, while scheduled runs default to headless behavior.
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 profile already locked by another browser process may not open.
Keeping sessions open after tests is useful for debugging but can leave state that makes later tests unrepresentative.

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.

Node reference

Triggers

Logic

Data

Network

Browser

Communication

System

When to use this node

Example: Open a headless reporting session

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Open a headless reporting session

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Open a headless reporting session

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides