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 and optionally retrieve the full contents of those similar items. It is useful for scenarios such as content discovery, competitive analysis, or research where you want to identify related articles, documents, or web pages based on a source URL.

For example, you can input a news article URL and get a list of similar news stories from other sources, optionally excluding the original domain. You can also fetch the full text and highlights of these similar contents in one step.

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 (the domain of the input URL) from the results.
- Number of Results The number of similar content results to return (default is 10).

Output

The node outputs an array of JSON objects representing the similar content found by the Exa API. Each object typically contains metadata about each similar item, such as URLs, titles, snippets, and possibly highlighted text excerpts if the "Get Contents" option is used.

If the operation includes retrieving contents, the output will include the full text content and highlights of the similar items.

No binary data output is produced by this node.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Providing an invalid or unreachable URL may result in no results or errors.
    • Requesting too many results might lead to rate limiting or performance delays.

  • Error messages:

    • Errors returned from the Exa API are propagated; typical messages include network errors, invalid parameters, or quota exceeded.
    • If the node is set to continue on fail, errors for individual items will be included in the output as { error: "message" }.

  • Resolutions:

    • Verify that the API key credential is correctly configured and active.
    • Ensure the input URL is valid and accessible.
    • Adjust the number of results requested to stay within API limits.

Links and References

Discussion