Short answer: Drop the "Tavily → Web Search" 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 |
|---|---|---|---|
Query query | string | Required | Search query |
Depth search_depth | options | Optional | Depth. Options: Basic (fast), Advanced (thorough) |
Max Results max_results | string | Optional | 5 |
Topic topic | options | Optional | Topic. Options: General, News, Finance |
Include Answer Summary include_answer | options | Optional | Include Answer Summary. Options: Yes, No |
{"query": "e.g. latest news on quantum computing","search_depth": "{{trigger.search_depth}}","max_results": "5","topic": "{{trigger.topic}}","include_answer": "{{trigger.include_answer}}"}
{"query": "quantum computing","answer": "Recent advances in quantum computing include...","results": [{"url": "https://example.com","score": 0.95,"title": "Title","content": "..."}]}
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.