Exa Websets icon

Exa Websets

Create, manage, and query structured datasets from web sources using Exa Websets API

Actions28

Overview

The node interacts with the "Monitor" resource of the Exa Websets API, specifically supporting the "List" operation. It retrieves a list of monitors that track new content and automatically update websets based on specified criteria.

This node is useful when you want to programmatically fetch and review monitoring configurations or statuses from your Exa Websets account. For example, you might use it to:

  • Get all active monitors to audit which content sources are currently being tracked.
  • Filter monitors created after a certain date to analyze recent monitoring setups.
  • Limit the number of returned monitors for pagination or performance reasons.

Properties

Name Meaning
Return All Whether to return all monitor results or only up to a given limit.
Limit Maximum number of monitor results to return (only applicable if "Return All" is false).
Filters Collection of filters to narrow down the list of monitors:
   Created After Filter monitors created after this ISO 8601 date/time string.
   Frequency Filter by monitoring frequency. Options: Daily, Hourly, Monthly, Weekly.
   Status Filter by monitor status. Options: Active, Paused, Stopped. Default is Active.

Output

The output is a JSON array where each item represents a monitor object retrieved from the API. Each monitor object typically contains details such as its ID, creation date, frequency, status, and other metadata related to the monitoring configuration.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to monitors, but in this case, the output is purely JSON data describing monitors.

Dependencies

  • Requires an API key credential for authenticating with the Exa Websets API.
  • The node makes HTTP requests to https://api.exa.ai.
  • No additional environment variables or external services are explicitly required beyond the API key.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key credential will cause authentication failures.
    • Providing invalid filter values (e.g., malformed dates) may result in API errors.
    • Requesting too many items without enabling "Return All" could lead to truncated results.

  • Error Messages:

    • "Unknown resource": Indicates the resource parameter is not set to "monitors".
    • API errors related to authentication or invalid parameters will be returned in the error field of the output if "Continue On Fail" is enabled.

  • Resolutions:

    • Ensure the API key credential is correctly configured and valid.
    • Validate filter inputs, especially date formats.
    • Use "Return All" carefully to avoid large payloads or timeouts.

Links and References

Discussion