Auto BrowserInstall

Overview

The "Auto Browser" node automates browser actions by interacting with a remote browser automation service via API calls. It supports various operations such as navigating to URLs, clicking elements, typing text, waiting for selectors, pressing keys, executing scripts, and closing tabs within a specified browser profile.

This node is beneficial in scenarios where automated web interactions are needed without manual browser control, such as:

• Automated testing of web applications.
• Web scraping or data extraction workflows.
• Automating repetitive browser tasks like form filling or navigation.
• Running custom JavaScript on web pages remotely.

For example, you can use this node to navigate to a product page, wait for a price element to appear, extract the price using a script, and then close the tab — all automatically.

Properties

Note: Only the "Navigate" operation uses the "URL" property.

Output

The node outputs JSON objects containing details about the performed operation:

• profileId: The browser profile used.
• tabId: The identifier of the browser tab/page involved.
• url: The URL navigated to (only for "navigate" operation).
• operation: The operation performed (e.g., "navigate").
• status: The status of the operation, typically "success" or "error".
• data: For the "executeScript" operation, contains the result of the executed script.
• error: If an error occurs and the node is set to continue on failure, this field contains the error message.

The node does not output binary data.

Dependencies

• Requires an external browser automation API service accessible via a server URL configured in the node credentials.
• The node needs an API key credential to authenticate requests to this service.
• The service endpoint is expected to support RESTful HTTP methods (POST for actions, DELETE for closing tabs).

Troubleshooting

• Missing Server URL: If the server URL is not found in credentials, the node will throw an error. Ensure the API credential is properly configured with the correct server URL.
• Invalid Profile or Tab ID: Using incorrect or non-existent profile or tab IDs may cause failures in operations.
• Timeouts: Waiting for selectors might time out if the selector never appears; increase the timeout or verify the selector correctness.
• API Errors: Network issues or invalid API responses from the browser automation service will cause errors. Check connectivity and service health.
• Continue On Fail: If enabled, the node will output error details instead of stopping execution, useful for debugging.

Links and References

• Puppeteer Documentation — For understanding browser automation concepts similar to those used here.
• n8n HTTP Request Node — For details on how HTTP requests are made internally.
• Your browser automation service's API documentation (not provided here) for specific action parameters and usage.