Exa icon

Exa

Interact with the Exa API
Join our community

Actions6

Overview

This node integrates with the Exa API to provide an answer to a user-supplied question. It is designed to generate answers based on the question input, optionally including source text and selecting different models for answer generation.

Common scenarios where this node is beneficial include:

  • Automating customer support by generating answers to frequently asked questions.
  • Enhancing chatbots or virtual assistants with dynamic, model-generated responses.
  • Research assistance by quickly retrieving concise answers from large datasets.

For example, a user can input a question like "What are the benefits of renewable energy?" and receive a generated answer. Optionally, they can include the source text that supports the answer or choose a more advanced model for potentially improved results.

Properties

Name Meaning
Question The question to get an answer for.
Additional Fields A collection of optional settings:
- Include Text Whether to include the source text in the response (true/false).
- Model The model to use for generating the answer. Options: "Default", "Exa Pro".

Output

The node outputs a JSON array where each element corresponds to the answer result for each input item.

  • The json output contains the answer data returned by the Exa API.
  • If "Include Text" is enabled, the output will also contain the source text used to generate the answer.
  • The structure of the answer depends on the API response but generally includes the generated answer text and optionally supporting content.
  • No binary data output is produced by this node.

Dependencies

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

Troubleshooting

  • Common issues:

    • Missing or invalid API key credential will cause authentication failures.
    • Providing an empty or invalid question string may result in errors or empty responses.
    • Network connectivity problems can prevent communication with the Exa API.

  • Error messages:

    • Errors from the API (e.g., rate limits, invalid parameters) will be thrown and can be caught if "Continue On Fail" is enabled.
    • Typical error message: "error": "<message>" indicating the reason for failure.

  • Resolutions:

    • Ensure the API key credential is correctly set up and valid.
    • Validate the question input before execution.
    • Check network connectivity and API service status.

Links and References

Discussion