Short answer: Drop the "IP Geolocation → Lookup IP Address (ip-api)" 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 |
|---|---|---|---|
IP Address ip | ip | Required | IP Address. e.g. "8.8.8.8" |
{"ip": "8.8.8.8"}
{"isp": "Google LLC","lat": 37.4223,"lon": -122.0848,"org": "Google Public DNS","zip": "94043","city": "Mountain View","query": "8.8.8.8","status": "success","country": "United States","timezone": "America/Los_Angeles","regionName": "California"}
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.