Actions28
Overview
The "Exa Websets" node integrates with the Exa Websets API to manage and manipulate structured datasets derived from web sources. Specifically, the Enrichment - Delete operation allows users to remove an existing enrichment record associated with a particular webset. This is useful when an enrichment (an AI-powered analysis or metadata attached to web content) is no longer relevant or needs to be cleared.
Common scenarios include:
- Cleaning up outdated or incorrect enrichments linked to websets.
- Managing data lifecycle by removing enrichments that are no longer needed.
- Automating maintenance of enriched datasets in workflows.
Example: A user has enriched a webset with sentiment analysis data but later decides to delete this enrichment to replace it with updated analysis.
Properties
| Name | Meaning |
|---|---|
| Webset ID | The unique identifier of the webset from which the enrichment will be deleted. |
| Enrichment ID | The unique identifier of the specific enrichment to delete within the selected webset. |
Output
The output JSON contains the result of the deletion operation. Typically, this would confirm whether the enrichment was successfully deleted or provide error information if the deletion failed.
Since the node interacts with a REST API, the output JSON structure depends on the API response for the delete request. It usually includes status or confirmation fields.
No binary data output is expected for this operation.
Dependencies
- Requires an active connection to the Exa Websets API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://api.exa.ai.
Troubleshooting
Common issues:
- Invalid or missing Webset ID or Enrichment ID parameters will cause the operation to fail.
- Authentication errors if the API key credential is not set or expired.
- Network connectivity problems preventing access to the Exa Websets API.
Error messages:
"Unknown resource": Occurs if the resource parameter is incorrectly set; ensure "enrichments" is selected.- API errors returned from the server (e.g., 404 Not Found if the enrichment does not exist) should be checked and handled accordingly.
Resolutions:
- Verify that both Webset ID and Enrichment ID are correctly provided and correspond to existing records.
- Confirm that the API key credential is valid and has necessary permissions.
- Check network settings and API endpoint accessibility.
Links and References
- Exa Websets API Documentation (hypothetical link for reference)
- n8n Documentation on Creating Custom Nodes