Exa icon

Exa

Interact with the Exa API
Join our community

Actions6

Overview

This node integrates with the Exa API to find content similar to a given URL. It is useful for scenarios where you want to discover related articles, web pages, or documents based on an existing URL. For example, marketers can use it to find competitor content, researchers can find related studies, and content creators can identify similar topics to expand upon.

The node supports two main operations under the "Find Similar" resource:

  • Find Similar: Retrieves URLs or content similar to the provided URL.
  • Find Similar and Get Contents: Retrieves similar content along with the full text and highlights.

Properties

Name Meaning
URL The URL to find similar content for.
Additional Fields Collection of optional parameters:
- Exclude Source Domain Whether to exclude the source domain from the results (true/false).
- Number of Results The number of similar results to return (default 10).

Output

The node outputs a JSON array where each element corresponds to the result of the API call for each input item. The structure depends on the operation:

  • For Find Similar, the output contains metadata about similar content found by the API.
  • For Find Similar and Get Contents, the output includes the similar content along with the full text and highlighted sections.

If errors occur during execution and the node is configured to continue on failure, the output will include objects with an error field describing the issue.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Exa API.
  • The node uses the external exa-js library to interact with the Exa API.
  • Proper configuration of the API key in n8n credentials is necessary.

Troubleshooting

  • Common issues:
    • Invalid or missing API key: Ensure the API key credential is correctly set up.
    • Network or API downtime: Check connectivity and Exa API status.
    • Incorrect URL format: Validate that the URL provided is well-formed.
  • Error messages:
    • Errors returned from the API are caught and either cause the node to fail or are included in the output if "Continue On Fail" is enabled.
    • Typical error messages relate to authentication failures, invalid parameters, or rate limits.

Links and References

Discussion