Short answer: Drop the "Tavily → Crawl Site" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
Max Breadth max_breadth | string | Optional | Max Breadth |
Page Limit limit | string | Optional | Page Limit |
{"url": "e.g. https://example.com/path","max_depth": "{{trigger.max_depth}}","max_breadth": "{{trigger.max_breadth}}","limit": "{{trigger.limit}}"}
{"results": [{"url": "https://example.com/p","raw_content": "..."}],"base_url": "https://example.com","response_time": 2.5}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.