ActionipstackUpdated September 2026
How do I geolocate an IP with ipstack?
Short answer: You can ipstack ip lookup in ipstack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ipstack ipstack IP Lookup 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 | string | Required | IP Address |
Sample request
{"ip": "{{trigger.ip}}"}
Returns
{"ip": "8.8.8.8","city": "Mountain View","latitude": 37.38,"longitude": -122.08,"country_name": "United States"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for ipstack IP Lookup.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about ipstack IP Lookup.
What does the ipstack IP Lookup action do in ipstack?
Commercial-licensed IP geolocation with country, city, timezone, currency, languages spoken. Higher tiers add proxy/VPN/threat detection. For production workflows that need commercial use rights.
What inputs does ipstack IP Lookup 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 ipstack returns an error?
The run history shows the failed step with its input and the error message ipstack 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 ipstack IP Lookup support batch operations?
Run ipstack IP Lookup 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 ipstack's rate limits.