Actions7
- Content Actions
- Navigation Actions
Overview
The node provides automation capabilities to interact with websites using a cloud-based browser instance. Specifically, the "Navigate to URL" operation under the "Navigation" resource allows users to control an already opened browser session by navigating it to a specified URL. This is useful in scenarios where you want to programmatically direct a browser to load a new webpage as part of a larger workflow, such as scraping content, testing web pages, or automating web interactions.
Practical examples include:
- Navigating a browser session to a login page before performing automated login steps.
- Directing the browser to a product page to capture screenshots or extract data.
- Automating navigation through multiple pages in a web application for testing or data collection.
Properties
| Name | Meaning |
|---|---|
| WebSocket Address | The browser WebSocket address obtained from a previously opened browser instance; required to connect and control the browser. |
| URL to Navigate | The target URL that the browser should navigate to. |
| Navigation Options | Options controlling navigation behavior: |
| - Wait Until: When to consider navigation finished. Options: Load, Domcontentloaded, Networkidle0, Networkidle2. Default is Load. | |
| - Timeout (Ms): Maximum time in milliseconds to wait for navigation to complete. Default is 30000 ms (30 seconds). |
Output
The output JSON object includes the following fields after successful navigation:
title: The title of the loaded webpage.url: The final URL after navigation (may differ due to redirects).content: The full HTML content of the loaded page.status: A string indicating success, e.g., "Navigation successful".
This output provides comprehensive information about the navigated page, enabling further processing or decision-making in workflows.
Dependencies
- Requires an active cloud browser service accessible via API with a valid API token credential.
- The node uses Puppeteer library internally to connect to the browser instance via the provided WebSocket address.
- Proper configuration of the cloud browser API credentials in n8n is necessary.
- The browser instance must be opened beforehand (e.g., via the "Open Browser" operation) to obtain the WebSocket address.
Troubleshooting
- No WebSocket address received: Ensure that the browser instance was successfully opened and the WebSocket address is correctly passed to this node.
- Timeout errors during navigation: Adjust the "Timeout (Ms)" property if the page takes longer to load.
- Navigation failures or incorrect page content: Verify the URL is correct and accessible from the cloud browser environment.
- Connection issues to browser: Confirm the WebSocket address is valid and the cloud browser service is running without network restrictions.
- If the node throws an error about unsupported operations, verify that the Resource is set to "Navigation" and Operation to "Navigate to URL".
Links and References
- Puppeteer Documentation – For understanding browser automation concepts used internally.
- Cloud browser service API documentation (refer to your cloud browser provider's docs) for details on opening browser instances and managing sessions.