Short answer: Drop the "SerpAPI → SerpAPI 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 q | string | Required | Query (required) |
Engine engine | options | Optional | Engine. Options: Google, Bing, DuckDuckGo … |
Country gl | string | Optional | Country |
Num Results num | string | Optional | Num Results |
{"q": "{{trigger.q}}","engine": "{{trigger.engine}}","gl": "{{trigger.gl}}","num": "{{trigger.num}}"}
{"organic_results": [{"link": "https://x.com","title": "T","snippet": "..."}]}
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.