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.
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 |
{"ip": "{{trigger.ip}}"}
{"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.
Any of these apps can fire this action as part of a workflow.