Extract URLs: Tavily action

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	List of URLs to extract
Depth extract_depth	options	Optional	Depth. Options: Basic, Advanced

Sample request

{
  "urls": "{{trigger.urls}}",
  "extract_depth": "{{trigger.extract_depth}}"
}

Returns

{
  "results": [
    {
      "url": "https://example.com",
      "raw_content": "..."
    }
  ],
  "failed_results": []
}

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

FAQ

Questions about Extract URLs.

What does the Extract URLs action do in Tavily?

Fetches a list of URLs and returns clean, structured Markdown for each, stripping nav, ads, and boilerplate. Use this in RAG pipelines or when you need to feed pages into an LLM context.

What inputs does Extract URLs 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 Tavily 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 Extract URLs support batch operations?

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

More actions