Exa Websets icon

Exa Websets

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

Actions28

Overview

The "Exa Websets" node allows users to create, manage, and query structured datasets called websets, which are collections of web content organized for easy access and analysis. Specifically, the Cancel operation under the Webset resource enables users to cancel an ongoing process or action related to a particular webset by specifying its ID.

This node is beneficial in scenarios where automated data collection or processing tasks need to be stopped before completion, such as halting a web scraping job, import, or enrichment process associated with a webset. For example, if a user starts importing large amounts of data into a webset but realizes the parameters were incorrect, they can use this Cancel operation to stop the import promptly.

Properties

Name Meaning
Webset ID The unique identifier of the webset to cancel. This is required to specify which webset's ongoing operation should be halted.

Output

The node outputs JSON data representing the result of the cancel operation. Typically, this will include confirmation that the cancellation was successful or details about the cancellation status. The exact structure depends on the API response but generally includes fields indicating success or failure.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Exa Websets API.
  • The node communicates with the Exa Websets service at https://api.exa.ai.
  • Proper configuration of the API authentication within n8n is necessary to perform operations.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Webset ID will likely cause errors.
    • Network connectivity problems may prevent communication with the Exa Websets API.
    • Insufficient permissions or expired API credentials can lead to authorization failures.

  • Error messages:

    • Errors indicating "Unknown resource" suggest the resource parameter is incorrectly set.
    • API error responses may include messages about invalid IDs or inability to cancel due to the current state of the webset.

  • Resolutions:

    • Verify the Webset ID is correct and corresponds to an active webset.
    • Ensure the API key credential is valid and has appropriate permissions.
    • Check network connectivity and retry the operation.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion