How to exa get contents 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
URLs urls	array	Required	URLs (array)
Include Text text	options	Optional	Include Text. Options: Yes, No
Include Highlights highlights	options	Optional	Include Highlights. Options: Yes, No

Sample request

{
  "urls": "{{trigger.urls}}",
  "text": "{{trigger.text}}",
  "highlights": "{{trigger.highlights}}"
}

Returns

{
  "results": [
    {
      "url": "https://example.com",
      "text": "...",
      "highlights": [
        "..."
      ]
    }
  ]
}

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

FAQ

Questions about Exa Get Contents.

What does the Exa Get Contents action do in Exa?

Fetches and cleans the full text of one or more specific URLs. The right path when you already have the URLs (from elsewhere or from Search) and want Exa's text extraction for downstream LLM consumption.

What inputs does Exa Get Contents require?

Required: URLs. 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 Get Contents support batch operations?

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

More actions