Exa Answer: Exa action · Tiny Command

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
Question query	string	Required	What is the latest research on quantum error correction?
Stream stream	options	Optional	Stream. Options: No, Yes (SSE)
Model model	options	Optional	Model. Options: Exa, Exa Pro

Sample request

{
  "query": "What is the latest research on quantum error correction?",
  "stream": "{{trigger.stream}}",
  "model": "{{trigger.model}}"
}

Returns

{
  "answer": "Quantum error correction has...",
  "citations": [
    {
      "id": "abc",
      "url": "https://x.com",
      "title": "T"
    }
  ]
}

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

FAQ

Questions about Exa Answer.

What does the Exa Answer action do in Exa?

Exa's RAG-as-a-service — pass a question, get back a synthesised answer with source citations. Saves the search + retrieve + LLM-summarise chain by bundling all three server-side. For "agent needs to look something up" workflows.

What inputs does Exa Answer require?

Required: Question. 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 Answer support batch operations?

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

More actions