How to map site in Tavily

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
Starting URL url	string	Required	Starting URL (required)
Max Depth max_depth	string	Optional	Max Depth
URL Limit limit	string	Optional	URL Limit

Sample request

{
  "url": "e.g. https://example.com/path",
  "max_depth": "{{trigger.max_depth}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "results": [
    "https://example.com/p1",
    "https://example.com/p2"
  ],
  "base_url": "https://example.com"
}

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

FAQ

Questions about Map Site.

What does the Map Site action do in Tavily?

Discovers URLs on a site without downloading or parsing page content. Much faster than Crawl when you only need the URL graph (sitemaps, audits, route inventories).

What inputs does Map Site require?

Required: Starting URL. 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 Map Site support batch operations?

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

More actions