Skip to main content
The official Exa node for n8n adds web search, content extraction, grounded answers, and Exa Agent runs to visual workflows. Use it as a regular workflow step or connect it to an n8n AI Agent as a tool.

​
Install the Exa node

The package name is n8n-nodes-exa-official.
1

Add the community node

Search for Exa in the n8n node picker. If it is not available on your instance, an instance owner can install n8n-nodes-exa-official by following n8n’s community node installation guide.The node requires n8n 1.60 or newer and Node.js 20.15 or newer.
2

Create an Exa API key

Get your Exa API key

Create a key in the dashboard. New accounts start with free credits.
3

Add Exa credentials

Add an Exa API credential in n8n and paste your key. Select that credential on each Exa node that should use the account.
  1. Add a trigger to a workflow.
  2. Add the Exa node.
  3. Choose Search.
  4. Enter a query and select a search type.
  5. Choose a response format:
    • Results for ranked pages
    • Text for a synthesized answer
    • Structured for JSON matching your schema
  6. Run the node and pass its output to the next workflow step.
Search can also return text, highlights, summaries, links, and images from each result. Domain filters, publication dates, categories, maxAgeHours, and subpage crawling are available in the node’s optional fields.

​
Available resources

​
Use Exa with an n8n AI Agent

Connect an Exa node to an AI Agent node through its tool input. Parameters that the model should supply can use n8n’s $fromAI() expression:
Search and Answer work well as grounding tools. Use the Agent resource when the task requires multi-step research, list building, structured enrichment, or premium Exa Connect data.

​
Wait for an Agent run

When creating an Agent run, Wait for Completion supports:
  • Stream to hold one server-sent events connection open until the run finishes
  • Poll to check the run on an interval
For long-running or asynchronous workflows, turn Wait for Completion off, save the returned run id, and use Get Run later. The run continues on Exa after the n8n step finishes.

​
Troubleshooting

Ask an instance owner to install the verified community package n8n-nodes-exa-official. Community-node availability can depend on how your n8n instance is hosted.
Confirm that the selected credential contains an active key from the Exa dashboard and that the key has available credits.
Disable Wait for Completion, persist the returned run id, and retrieve the result in a later step with Get Run.

​
Resources

Official Exa node

Review the current operations, compatibility, and source.

Exa Agent

Build multi-step research and enrichment workflows.

Search best practices

Write better queries and choose the right search mode.
Last modified on September 15, 2026