Exa Websets icon

Exa Websets

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

Actions28

Overview

The node "Exa Websets" allows users to create, manage, and query structured datasets called websets from web sources using the Exa Websets API. Specifically, the Search - Get operation enables retrieving details of a specific search within a given webset by providing the webset ID and the search ID. This is useful for scenarios where you want to programmatically access the results or metadata of a previously executed search inside a webset.

Practical examples include:

  • Fetching search results to analyze or process them further in an automation workflow.
  • Monitoring the status or details of a particular search query within a webset.
  • Integrating search data into other systems or dashboards.

Properties

Name Meaning
Webset ID The ID of the webset to search within.
Search ID The ID of the search whose details you want to retrieve.

Output

The output JSON contains the detailed information about the specified search within the given webset. This typically includes metadata and results related to that search as returned by the Exa Websets API.

If the node supports binary data output (not explicitly shown in the provided code), it would represent any associated files or media linked to the search results, but this is not indicated here.

Dependencies

  • Requires an active connection to the Exa Websets API.
  • Needs an API key credential configured in n8n for authentication with the Exa Websets service.
  • The base URL for API requests is https://api.exa.ai.

Troubleshooting

  • Common issues:

    • Invalid or missing Webset ID or Search ID will cause the API call to fail.
    • Authentication errors if the API key credential is not set up correctly.
    • Network connectivity problems preventing access to the Exa Websets API.
  • Error messages:

    • "Unknown resource" error if an unsupported resource name is used.
    • API errors returned from the Exa Websets service, such as "Not Found" if the search or webset ID does not exist.
  • Resolutions:

    • Verify that the Webset ID and Search ID are correct and exist in your Exa Websets account.
    • Ensure the API key credential is properly configured and has necessary permissions.
    • Check network connectivity and firewall settings.

Links and References

Discussion