Actions28
Overview
The node "Exa Websets" integrates with the Exa Websets API to create, manage, and query structured datasets derived from web sources. Specifically, the Monitor - Get operation allows users to retrieve details about a specific monitor by its ID. Monitors are used to track new content automatically and update websets accordingly.
This node is beneficial in scenarios where you want to automate monitoring of web content changes or updates and integrate those updates into your data workflows. For example, you could use it to fetch the status or configuration of a particular monitor that watches for new articles on a news website or product listings on an e-commerce platform.
Properties
| Name | Meaning |
|---|---|
| Monitor ID | The ID of the monitor to retrieve details for |
Output
The output JSON contains the detailed information about the requested monitor. This typically includes metadata such as the monitor's configuration, status, last run time, and any other relevant attributes provided by the Exa Websets API for monitors.
If the node encounters an error (e.g., invalid Monitor ID), the output will contain an error field describing the issue along with the resource and operation names.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Exa Websets API.
- The base URL for API requests is
https://api.exa.ai. - Proper configuration of the API key credential within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing Monitor ID: Ensure the Monitor ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
- Network or API downtime: Check connectivity and the status of the Exa Websets API service.
Error messages:
"Unknown resource: monitors": This indicates the resource parameter was not set correctly; ensure "monitors" is selected.- Errors returned from the API will be included in the output under the
errorfield if "Continue On Fail" is enabled.
Links and References
- Exa Websets API Documentation (hypothetical link for reference)
- n8n documentation on Creating Custom Nodes