Actions28
Overview
The node "Exa Websets" allows users to interact with the Exa Websets API to manage structured datasets derived from web sources. Specifically, for the Item - Get operation, it retrieves detailed information about a single item within a specified webset. This is useful when you want to fetch metadata or content of an individual item stored in a webset.
Common scenarios include:
- Fetching details of a specific article, document, or data entry identified by its unique ID within a webset.
- Integrating item-level data retrieval into workflows that process or analyze web-collected content.
- Automating updates or validations by retrieving current item states before further processing.
Example: You have a webset containing news articles and want to get the full details of one particular article by its ID to enrich it or send it downstream.
Properties
| Name | Meaning |
|---|---|
| Webset ID | The unique identifier of the webset that contains the items. |
| Item ID | The unique identifier of the specific item to retrieve from the given webset. |
Output
The output JSON contains the detailed data of the requested item as returned by the Exa Websets API. This typically includes all metadata and content fields associated with the item, such as title, description, URL, timestamps, and any custom attributes defined in the webset.
If the node supports binary data (not explicitly shown here), it would represent the item's binary content (e.g., images, documents) if available.
Dependencies
- Requires an active connection to the Exa Websets API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for API calls is
https://api.exa.ai.
Troubleshooting
Common issues:
- Invalid or missing Webset ID or Item ID will cause the API call to fail.
- Network connectivity problems can prevent successful API communication.
- Insufficient permissions or expired API credentials may result in authorization errors.
Error messages:
"Unknown resource": Indicates the resource parameter was not set correctly; ensure "items" is selected.- API error responses will be passed through; check the error message for details like "Item not found" or "Unauthorized".
Resolutions:
- Verify that the Webset ID and Item ID are correct and exist in your Exa Websets account.
- Confirm that the API key credential is valid and has necessary permissions.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch executions.
Links and References
- Exa Websets API Documentation (hypothetical link)
- n8n documentation on creating custom nodes
- General info on API authentication in n8n