Wait For

Node type: wait_for · Version: 1 · Category: Browser Wait for page state or an element. 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

Synchronize with a dynamic element, text, URL, response, download, or page load state.
Replace fragile fixed delays with a bounded observable condition.

Example: Wait for an export to become ready

Wait up to 60 seconds for the recorded Download report button to become visible.

Example settings

{
  "waitFor": "element_visible",
  "locator": {
    "primary": {
      "kind": "role",
      "value": "button",
      "name": "Download report"
    },
    "alternatives": []
  },
  "delayMs": 1000,
  "timeoutMs": 60000
}

This shows the important settings, not a complete exported node. The locator is shortened for readability; use the recorder to create the complete structured locator bundle.

Choose the event that actually proves readiness.
Record a locator or provide the conditional URL/text fields.
Keep a finite timeout and inspect diagnostics when it expires.

Configuration

Field	Type	Default	What it controls
`waitFor`	string	`"element_visible"`	Browser event or state that must occur. Values: `time`, `element_visible`, `element_hidden`, `text_present`, `url_matches`, `download_begins`, `network_response`, `page_load_state`.
`locator`	locator	`null`	Recorded locator bundle. sndbox prefers accessible role/name data and retains fallbacks.
`delayMs`	number	`1000`	Time delay in milliseconds.
`timeoutMs`	number	`30000`	Maximum time for this operation in milliseconds.
`text`	any	—	Text that must be present on the page. Shown when `waitFor` is `text_present`.
`urlPattern`	any	—	URL pattern matched against navigation or network activity. Shown when `waitFor` is `url_matches` or `network_response`.
`loadState`	any	—	DOM ready, page loaded, or network idle. Values: `dom_ready`, `page_loaded`, `network_idle`. Shown when `waitFor` is `page_load_state`.

Workflow JSON

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

Default node configuration

{
  "type": "wait_for",
  "version": 1,
  "configuration": {
    "waitFor": "element_visible",
    "locator": null,
    "delayMs": 1000,
    "timeoutMs": 30000
  }
}

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

time uses delayMs; element modes use the locator; URL, network, and load-state modes expose their corresponding fields.
Completion means the selected condition was observed, not that every background task on the page finished.
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

network_idle is unsuitable for pages with continuous network activity.
A text condition can match hidden or repeated content differently than an element visibility check.

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: Wait for an export to become ready

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Wait for an export to become ready

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Wait for an export to become ready

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides