Skip to main content
Node type: navigate · Version: 1 · Category: Browser Load a URL in the active 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

  • Load the next page in an active managed browser session.
  • Wait for an initial page milestone before interaction begins.

​
Example: Open a report page

Navigate to the portal and wait until the DOM is ready, with a 30-second bound.
Example settings
This shows the important settings, not a complete exported node.
  1. Connect from Open Browser or another action in the same session path.
  2. Choose the weakest readiness condition that is sufficient.
  3. Add Wait For when a specific dynamic control must become available.

​
Configuration

​
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 URL must be inside the workflow’s approved network boundary.
  • dom_ready, page_loaded, network_idle, and element_visible describe different milestones and can complete at different times.
  • 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 may never arrive on pages with analytics, streaming, or polling.
  • A successful navigation does not guarantee that a later dynamic element is ready.

​
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.