Exa icon

Exa

Interact with the Exa API
Join our community

Actions6

Overview

This node interacts with the Exa API to retrieve content from specified URLs. Specifically, the "Get Contents" operation allows users to input one or more URLs and fetch their associated content. This is useful in scenarios where you want to programmatically extract and process the textual content of web pages or documents referenced by URLs.

Practical examples include:

  • Aggregating content from multiple news articles for sentiment analysis.
  • Extracting product descriptions from e-commerce URLs for comparison.
  • Collecting blog post contents for summarization or keyword extraction.

Properties

Name Meaning
URLs A comma-separated list of URLs for which the node will retrieve content. Each URL should be a valid web address pointing to the desired resource.

Output

The node outputs a JSON array where each element corresponds to the content retrieved from the provided URLs. The content includes textual data extracted from those URLs. The output field json contains this structured content data.

If the node supports binary data (not explicitly shown here), it would typically represent media or file content fetched from the URLs, but in this case, the focus is on textual content retrieval.

Dependencies

  • Requires an API key credential for authenticating with the Exa API service.
  • The node depends on the external exa-js library to interact with the Exa API.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or malformed URLs in the "URLs" property can cause failures in content retrieval.
    • Missing or incorrect API key credentials will result in authentication errors.
    • Network connectivity problems may prevent access to the URLs or the Exa API.

  • Error messages:

    • Errors related to invalid URLs usually indicate that the input URLs need correction or validation.
    • Authentication errors suggest checking the API key credential setup.
    • If the node throws errors about exceeding rate limits or quota, verify your API usage limits with the Exa service.

  • To handle errors gracefully, the node supports continuing on failure, allowing partial results to be returned even if some URLs fail.

Links and References

Discussion