Actions6
Overview
This node integrates with the BrowserAI API to manage and interact with automated browser tasks. Specifically, the "Get Task Results" operation retrieves the results of a previously executed task using its session ID. This is useful for workflows that need to process or analyze the output generated by browser automation tasks, such as scraping data, running scripted interactions, or monitoring web content changes.
Practical examples include:
- Fetching the outcome of a web scraping task to extract product prices or reviews.
- Retrieving results from an automation script that fills forms or performs repetitive actions on websites.
- Collecting data after a crawler automation has run to feed into further processing or reporting nodes.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the task session whose results you want to retrieve. |
Output
The node outputs a JSON object containing the full response from the BrowserAI API for the requested task results. This typically includes all data produced by the task execution, such as scraped content, logs, or any structured output defined by the task.
If the task produces binary data (e.g., screenshots or files), this would be included in the output accordingly, but based on the static code, the node primarily returns JSON data representing the task results.
Dependencies
- Requires an API key credential for authenticating with the BrowserAI API.
- The node makes HTTP requests to
https://browser.ai/api/v1/. - Proper configuration of the API key credential within n8n is necessary for successful communication.
Troubleshooting
- Missing or invalid Session ID: If the session ID is not provided or incorrect, the API call will fail. Ensure the session ID corresponds to an existing task.
- API authentication errors: If the API key is missing, expired, or invalid, the node will return authorization errors. Verify the API key credential setup.
- Network issues: Connectivity problems to the BrowserAI API endpoint can cause request failures. Check network access and proxy settings if applicable.
- Unexpected API responses: If the API changes or returns unexpected data structures, the node may not handle it correctly. Review API documentation and update the node or workflow accordingly.
Links and References
- BrowserAI API Documentation (for detailed API endpoints and data formats)
- n8n Documentation on Creating Custom Nodes