Exa Websets icon

Exa Websets

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

Actions28

Overview

The node "Exa Websets" integrates with the Exa Websets API to manage and query structured datasets derived from web sources. Specifically, the Import - List operation allows users to retrieve a list of import jobs that have been performed on websets. This is useful for tracking data ingestion activities, auditing import statuses, or filtering imports based on criteria such as date ranges, type, or status.

Practical examples include:

  • Fetching all recent CSV imports completed in the last week.
  • Listing only failed imports to troubleshoot issues.
  • Retrieving a limited number of pending imports for monitoring purposes.

Properties

Name Meaning
Return All Whether to return all import results or limit the output to a specified maximum number.
Limit The maximum number of import results to return when not returning all. Must be at least 1.
Filters A collection of filters to narrow down the list of imports:
   Created After Filter imports created after this ISO 8601 date/time (e.g., "2024-01-01T00:00:00Z").
   Created Before Filter imports created before this ISO 8601 date/time (e.g., "2024-12-31T23:59:59Z").
   Import Type Filter by import type. Options: CSV, JSON, Sitemap, URL List.
   Status Filter by import status. Options: Cancelled, Completed, Failed, Paused, Pending (default), Running.

Output

The node outputs a JSON array where each element represents an import job matching the filter criteria. Each import object typically contains metadata about the import such as its creation date, type, status, and possibly other details returned by the Exa Websets API.

If binary data were involved (not indicated here), it would represent files or content imported, but this operation focuses on listing import metadata only.

Dependencies

  • Requires an API key credential for authenticating with the Exa Websets API.
  • The node communicates with the base URL https://api.exa.ai.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid date formats in filters (non-ISO 8601) may result in errors or no results.
    • Requesting too many results without enabling "Return All" might truncate data unexpectedly.

  • Error Messages:

    • "Unknown resource": Occurs if the resource parameter is set incorrectly; ensure "imports" is selected.
    • API errors related to rate limits or invalid parameters will be surfaced as error messages in the node output.

  • Resolutions:

    • Verify API key validity and permissions.
    • Use correct ISO 8601 date strings for date filters.
    • Adjust "Return All" and "Limit" settings according to expected data volume.

Links and References

Discussion