Actions28
Overview
The node "Exa Websets" allows users to interact with the Exa Websets API to create, manage, and query structured datasets derived from web sources. Specifically, the Search - Cancel operation enables users to cancel an ongoing search within a specified webset. This is useful in scenarios where a search query was initiated but needs to be stopped before completion, for example, if the search criteria were incorrect or if the user wants to free up resources.
Practical examples:
- Canceling a long-running search that is no longer needed.
- Stopping a search to modify parameters and restart it with updated criteria.
- Managing multiple searches by programmatically cancelling outdated or irrelevant ones.
Properties
| Name | Meaning |
|---|---|
| Webset ID | The ID of the webset to search within. |
| Search ID | The ID of the search to cancel. |
Output
The output JSON will typically contain confirmation details about the cancellation of the specified search. It may include status information indicating whether the cancellation was successful or if there were any issues.
If the node supports binary data output (not indicated here), it would represent related content such as search results or logs, but for the cancel operation, the output is expected to be purely JSON-based confirmation.
Dependencies
- Requires an API key credential for authenticating with the Exa Websets API.
- The node communicates with the Exa Websets REST API at
https://api.exa.ai. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
Common Issues:
- Providing invalid or non-existent Webset ID or Search ID will likely result in errors.
- Network connectivity problems can prevent communication with the Exa Websets API.
- Insufficient permissions or expired API keys may cause authentication failures.
Error Messages:
- Errors indicating unknown resource or operation suggest misconfiguration of the node parameters.
- API error messages returned from the Exa Websets service should be checked for details on why cancellation failed.
Resolutions:
- Verify that the Webset ID and Search ID are correct and exist in your Exa Websets account.
- Ensure the API key credential is valid and has appropriate permissions.
- Check network connectivity and retry the operation.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch executions.
Links and References
- Exa Websets API Documentation (Assumed official docs URL)
- n8n Documentation on Creating Custom Nodes
- General info on managing API credentials in n8n: Credentials