How to exa neural search in Exa

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Query query	string	Required	Query (required)
Type type	options	Optional	Type. Options: Auto, Neural, Keyword
Num Results num_results	string	Optional	Num Results
Include Page Text include_text	options	Optional	Include Page Text. Options: Yes, No

Sample request

{
  "query": "{{trigger.query}}",
  "type": "{{trigger.type}}",
  "num_results": "{{trigger.num_results}}",
  "include_text": "{{trigger.include_text}}"
}

Returns

{
  "results": [
    {
      "url": "https://example.com",
      "text": "...",
      "score": 0.95,
      "title": "Title",
      "publishedDate": "2026-01-01"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Exa Neural Search.

What does the Exa Neural Search action do in Exa?

Semantic web search — favours content depth and topical relevance over keyword exactness. Returns URLs with titles and summaries. Use include_answer to bundle LLM synthesis, include_raw_content to fetch the cleaned text inline.

What inputs does Exa Neural Search require?

Required: Query. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Exa returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Exa Neural Search support batch operations?

Yes. Run Exa Neural Search inside a Loop node to process arrays. TinyCommand handles Exa's rate limits automatically so you don't have to throttle manually.

More actions