Overview
The node automates browser actions by interacting with a remote browser automation service via HTTP API calls. It supports multiple operations such as navigating to URLs, clicking elements, typing text, waiting for selectors, pressing keys, executing custom scripts, and closing tabs within specified browser profiles and tabs.
This node is beneficial in scenarios where automated web interactions are needed without manual browser control, such as:
- Automated testing of web pages.
- Web scraping or data extraction workflows.
- Automating repetitive browser tasks like form filling or navigation.
- Running custom JavaScript on web pages to extract or manipulate data.
For example, you can use it to navigate to a product page, wait for the price element to appear, extract the price using a script, and then close the tab — all automatically.
Properties
| Name | Meaning |
|---|---|
| Profile | The browser profile identifier to use for the operation. Profiles isolate browser sessions. |
| Tab ID | Optional identifier of the browser tab to target. If omitted, a new tab may be used/created. |
| Script | (Only for Execute Script operation) The JavaScript code to run inside the browser context. |
Note: The above properties apply specifically to the "Execute Script" operation. Other operations have additional properties (not requested here).
Output
The node outputs JSON objects containing details about the executed operation:
- For Execute Script operation, the output JSON includes:
data: The result returned from evaluating the provided script in the browser context.profileId: The browser profile used.tabId: The tab targeted (may be empty if not specified).operation: The string"executeScript".status:"success"if the operation completed successfully.
Other operations output similar JSON structures indicating success status, profile, tab, and operation type.
No binary data output is produced by this node.
Dependencies
- Requires an external browser automation service accessible via an API endpoint (
serverUrl), configured through credentials. - The node sends HTTP requests to this service to perform browser actions.
- Requires an API key or authentication token credential to access the browser automation server.
- The server URL must be set in the node's credentials configuration.
Troubleshooting
- Missing Server URL: If the server URL is not found in credentials, the node will throw an error. Ensure the API endpoint is correctly configured.
- Invalid Profile or Tab ID: Using incorrect or non-existent profile or tab IDs may cause failures. Verify these identifiers exist on the automation server.
- Script Errors: Syntax errors or runtime exceptions in the provided script may cause the operation to fail or return unexpected results.
- Timeouts or Network Issues: Communication problems with the automation server can cause request failures.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
To resolve issues:
- Confirm credentials and server URL are correct.
- Validate input parameters carefully.
- Check the automation server logs for more detailed error information.
- Test scripts independently before running them in the node.
Links and References
- Puppeteer Documentation (commonly used for browser automation)
- n8n HTTP Request Node Documentation
- General browser automation concepts: https://developer.mozilla.org/en-US/docs/Web/API/Automation