ActionIP GeolocationUpdated September 2026
How do I geolocate an IP address (free)?
Short answer: You can lookup ip address (ip-api) in IP Geolocation by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the IP Geolocation Lookup IP Address (ip-api) action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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" |
Sample request
{"ip": "8.8.8.8"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Lookup IP Address (ip-api).
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Lookup IP Address (ip-api).
What does the Lookup IP Address (ip-api) action do in IP Geolocation?
Returns country, region, city, lat/lon, ISP, ASN, timezone for an IPv4 or IPv6 address. Free tier no-auth (non-commercial). For localisation, security workflows, basic analytics.
What inputs does Lookup IP Address (ip-api) require?
Required: IP Address. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if IP Geolocation returns an error?
The run history shows the failed step with its input and the error message IP Geolocation returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Lookup IP Address (ip-api) support batch operations?
Run Lookup IP Address (ip-api) inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within IP Geolocation's rate limits.