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 Delete operation under the Webset resource enables users to remove a webset by its unique identifier. This is useful for cleaning up outdated or irrelevant datasets, managing storage, or maintaining an organized collection of web content.
Practical examples include:
- Automatically deleting websets that are no longer needed after processing.
- Removing test or temporary websets created during data ingestion workflows.
- Managing lifecycle of datasets in automated content curation pipelines.
Properties
| Name | Meaning |
|---|---|
| Webset ID | The unique identifier of the webset to delete |
Output
The output JSON contains the response from the Exa Websets API after attempting to delete the specified webset. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data output is produced by this operation.
Example output JSON might look like:
{
"success": true,
"message": "Webset deleted successfully",
"websetId": "12345"
}
Or in case of failure:
{
"error": "Webset not found",
"websetId": "12345"
}
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:
- Providing an invalid or non-existent Webset ID will result in an error indicating the webset could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent communication with the Exa Websets API.
Error messages and resolutions:
"Webset not found": Verify the Webset ID is correct and exists.- Authentication errors: Check that the API key credential is properly set up and has necessary permissions.
- Timeout or network errors: Ensure stable internet connection and that the API endpoint is reachable.
Links and References
- Exa Websets API Documentation (hypothetical link)
- n8n documentation on creating custom nodes