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 structured datasets sourced from the web. Specifically, for the Import - Update operation, it allows users to update existing import jobs by modifying their configuration, priority, or status. This is useful in scenarios where an ongoing or scheduled import needs adjustment without creating a new import job, such as changing the import's processing priority or pausing/resuming it.

Practical examples include:

  • Updating the priority of an import to "urgent" to expedite data ingestion.
  • Pausing an import temporarily due to system maintenance.
  • Modifying the import configuration JSON to adjust parameters like source URLs or filters.

Properties

Name Meaning
Import ID The unique identifier of the import job to update.
Update Fields A collection of fields to update on the import:
  Configuration Updated import configuration in JSON format (e.g., source settings, filters).
  Priority Priority level of the import. Options: High, Low, Normal, Urgent.
  Status Status of the import. Options: Cancelled, Paused, Running.

Output

The node outputs a JSON object representing the updated import resource after applying the changes. The exact structure depends on the API response but typically includes fields such as import ID, updated configuration, current status, priority, timestamps, and other metadata related to the import job.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Exa Websets API endpoint (https://api.exa.ai).
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node uses internal service classes to handle the API calls for imports.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Import ID will likely result in an error indicating the import was not found.
    • Malformed JSON in the Configuration field can cause request failures.
    • Attempting to set unsupported values for Priority or Status will be rejected by the API.

  • Error messages:

    • "Unknown resource": Occurs if the resource parameter is incorrectly set; ensure "imports" is selected.
    • API errors related to authentication failure indicate missing or incorrect API credentials.
    • Validation errors from the API when update fields are invalid or incomplete.

  • Resolutions:

    • Double-check the Import ID exists and is correct.
    • Validate JSON syntax before submitting the Configuration update.
    • Use only allowed options for Priority and Status.
    • Ensure API credentials are properly configured and have sufficient permissions.

Links and References

Discussion