Actions28
Overview
The "Exa Websets" node allows users to create, manage, and query structured datasets called websets, which are collections of web content organized via the Exa Websets API. This node is useful for automating workflows that involve aggregating, updating, or retrieving structured web data for analysis, reporting, or integration with other systems.
Specifically, the Get operation on the Webset resource retrieves detailed information about a particular webset by its unique identifier. This can be used in scenarios such as fetching metadata or content summaries of a webset before further processing or enrichment.
Practical examples:
- Retrieve a webset's details to display in a dashboard.
- Fetch a webset's content to feed into another system for analysis.
- Use the webset ID to verify existence or status before performing updates or deletions.
Properties
| Name | Meaning |
|---|---|
| Webset ID | The unique identifier of the webset to retrieve. This is a required string input. |
Output
The output of the Get operation on the Webset resource is a JSON object containing the details of the requested webset. This typically includes metadata and structured content associated with the webset as returned by the Exa Websets API.
If the node supports binary data (not indicated here), it would represent any files or media related to the webset, but this node primarily outputs JSON data describing the webset.
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 authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Webset ID will cause the API call to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems may prevent reaching the Exa Websets API endpoint.
Error messages:
"Unknown resource": Occurs if the resource parameter is set incorrectly; ensure "websets" is selected.- API errors returned from the Exa Websets service will be passed through; check the error message for details like invalid ID or permission issues.
Resolution tips:
- Verify the Webset ID is correct and exists in your Exa Websets account.
- Confirm that the API key credential is valid and has appropriate permissions.
- Check network settings and firewall rules to allow outbound requests to
api.exa.ai.
Links and References
- Exa Websets API Documentation (hypothetical link)
- n8n documentation on creating custom nodes
- General REST API usage best practices