Actions7
- Content Actions
- Navigation Actions
Overview
The node provides automation capabilities to interact with websites using a cloud-based browser instance. Specifically, for the Navigation > Navigate to URL operation, it connects to an already opened browser session via a WebSocket address and navigates that browser to a specified URL. It supports options to control how the navigation waits for page load events and the maximum timeout duration.
This node is beneficial in scenarios where you want to programmatically control a browser session remotely, such as automating web testing, scraping dynamic content, or orchestrating multi-step browsing workflows without managing local browser instances.
Example use case:
- After opening a browser instance (via a prior "Open Browser" operation), navigate to a target website URL to prepare for further interactions like clicking elements or extracting content.
Properties
| Name | Meaning |
|---|---|
| WebSocket Address | The browser WebSocket address string returned from the "Open Browser" operation; used to connect to the existing browser session. |
| URL to Navigate | The full URL string to which the browser should navigate. |
| Navigation Options | Options controlling navigation behavior: • Wait Until: When to consider navigation finished. Options: load, domcontentloaded, networkidle0, networkidle2.• Timeout (Ms): Maximum time in milliseconds to wait for navigation before timing out. |
Output
The output JSON object includes:
title: The title of the loaded webpage after navigation.url: The final URL of the page after navigation (may differ due to redirects).content: The full HTML content of the loaded page.status: A status message indicating success, e.g.,"Navigation successful".
No binary data is output for this operation.
Dependencies
- Requires an active cloud browser service accessible via API with a valid API token credential.
- Uses Puppeteer library to connect to the remote browser instance through the provided WebSocket address.
- The node expects the WebSocket address to be obtained from a prior "Open Browser" operation within the same workflow or externally.
Troubleshooting
Common issues:
- Invalid or expired WebSocket address: Ensure the WebSocket address is current and corresponds to an open browser session.
- Navigation timeout: If the page takes too long to load, increase the "Timeout (Ms)" value or adjust the "Wait Until" option.
- Network errors or unreachable URLs: Verify the URL is correct and accessible from the cloud browser environment.
Error messages:
"No WebSocket address received from the browser service": Indicates failure to obtain a valid WebSocket address during browser opening; check the "Open Browser" step."The operation 'goto' for resource 'navigation' is not supported": Means the operation name or resource was incorrectly specified.- Timeout errors during navigation: Adjust timeout settings or verify network connectivity.
Links and References
- Puppeteer Documentation – For understanding browser automation concepts used internally.
- Cloud browser service API documentation (refer to your provider) for details on browser session management and WebSocket addresses.