Exa icon

Exa

Interact with the Exa API
Join our community

Actions6

Overview

This node integrates with the Exa API to perform advanced content search and retrieval operations. Specifically, for the Search resource with the Search and Get Contents operation, it allows users to submit a search query and retrieve detailed content results including text and highlights.

Common scenarios where this node is beneficial include:

  • Content discovery workflows where you want to find relevant articles or documents based on a query.
  • Automated research pipelines that require fetching both metadata and full content of search results.
  • Enhancing knowledge bases by programmatically retrieving and processing external content.

For example, a user could input a query like "latest AI advancements" and receive a curated list of articles along with their full text and highlighted excerpts, enabling further analysis or summarization downstream.

Properties

Name Meaning
Query The search query string to find relevant content.
Additional Fields A collection of optional parameters to refine the search:
- End Published Date Filter results published on or before this date (format YYYY-MM-DD).
- Include Domains Comma-separated list of domains to restrict the search to.
- Number of Results The maximum number of search results to return (default is 10).
- Start Published Date Filter results published on or after this date (format YYYY-MM-DD).
- Use Autoprompt Boolean flag to enable autoprompt feature for the query, potentially enhancing search relevance.

Output

The node outputs an array of JSON objects representing the search results. For the Search and Get Contents operation, each result includes:

  • Full text content of the matched items.
  • Highlighted snippets showing query matches within the content.
  • Metadata such as publication dates and source information (depending on the API response).

This rich output enables users to directly consume or process the retrieved content in subsequent workflow steps.

Dependencies

  • Requires an active connection to the Exa API via an API key credential.
  • The node depends on the exa-js library to interact with the Exa API endpoints.
  • 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.
    • Incorrect date formats in the start/end published date fields may lead to API errors.
    • Providing empty or malformed queries can result in no results or errors.

  • Error Messages:

    • Authentication errors typically indicate issues with the provided API key; verify and update credentials.
    • Validation errors from the API regarding date formats or parameter values should be corrected according to the expected format (e.g., YYYY-MM-DD).
    • Network or timeout errors suggest connectivity problems; retry or check network settings.

Links and References

Discussion