Short answer: Drop the "Serper → Serper Google Maps 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 | coffee shops near Times Square |
Lat,Lng ll | string | Optional | @40.7,-74.0,15z |
Country gl | string | Optional | Country |
{"q": "coffee shops near Times Square","ll": "@40.7,-74.0,15z","gl": "{{trigger.gl}}"}
{"places": [{"cid": "abc","title": "Cafe","rating": 4.5,"address": "123 Main","ratingCount": 200}]}
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.