IP2Location.io IP Geolocation
Analytics & DataResolve IPv4 and IPv6 addresses to geolocation and network intelligence with IP2Location.io, returning country, region, city, ZIP, and carrier data. Agents localize experiences and flag traffic that does not fit the account.
What This Integration Enables
IP2Location.io is the breadth play in IP geolocation. Every plan returns country, region, city, ZIP, coordinates, time zone, ASN and AS name with a proxy flag. Higher plans progressively add:
- ISP, domain, net speed, usage type and address type
- Mobile carrier down to MCC, MNC and brand
- Translated place objects, currency and language, IDD and area codes, elevation
- A detailed proxy object covering VPN, Tor, data center and residential detection
- A fraud score and IAB advertising categories
That is a lot of attributes to hang segmentation, localization and risk logic on without wiring up several vendors.
FlowRunner agents use that breadth two ways. Inline, an agent resolves one address at the moment a person signs up or a ticket opens and adapts what happens next. In bulk, an agent resolves up to a thousand addresses per request against the bulk endpoint, which is how you enrich a quarter of firewall logs or a stale signup table without a loop. Either way the connector returns a network profile, not a verdict. The verdict is a decision your flow makes, and FlowRunner's position is that some of those decisions belong to a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Currency and locale set from the connection, not the dropdown
A self-serve product collects a billing country from a dropdown that most people leave at the default. An agent resolves each new signup's address with Lookup IP Address and compares the returned country, currency and language against what the account says. Most agree, and the agent sets the display currency and locale so the pricing page speaks the right money on the first visit. The ones that disagree do not get quietly overwritten. A customer connecting from Singapore with a US billing country might be travelling, might be a US employee of an APAC subsidiary, or might be sitting behind a corporate proxy, and the usage type field tells you which is plausible.
Backfilling a quarter of logs without a loop
A security review asks where a quarter of blocked requests actually came from. An agent pulls the distinct addresses out of the log export, batches them into Lookup IP Addresses In Bulk a thousand at a time with the Fields parameter trimmed to country, ASN, usage type and the proxy object, and writes the enriched rows into Snowflake. What was a multi-hour enrichment loop becomes a handful of requests, and the analyst gets a table they can group by network rather than by raw address.
Carrier and connection segmentation for a mobile campaign
A campaign targets mobile users on a specific carrier in a specific region. An agent enriches the audience list with Lookup IP Addresses In Bulk, reads the mobile carrier brand, MCC and MNC alongside net speed and usage type, and builds the segment in Klaviyo from connection attributes the CRM never captured. Records where the address resolves to a data center rather than a mobile carrier are held out, because a data center address on a mobile campaign is usually a scraper.
Human-in-Loop Highlight
The gate sits on repricing. When the resolved country disagrees with the billing country on an existing paying account, changing the account's region is not a display tweak: it changes the currency, the tax treatment and the amount on the next invoice, and the customer sees it. The agent will not make that change on the strength of one address. It gathers the evidence from Lookup IP Address, then posts to the revenue operations channel: "Account 8841 bills in GBP with a UK address on file. Last four logins resolved to Ireland, usage type COM, no proxy flag. Re-region to EUR, keep GBP, or ask the customer?" The operator picks. Accounts where the signals agree never reach a human, which is the point. The automation exceptions are the only thing on the queue.
Agent Capabilities
2 actionsIP Lookup
2- Lookup IP Address Resolves a single IPv4 or IPv6 address to its geolocation and network profile. Country, region, city, ZIP, coordinates, time zone, ASN, AS name and a proxy flag come back on every plan, with ISP, domain, net speed, usage type, mobile carrier, currency and language, the detailed proxy object, fraud score and IAB categories layered in as the plan allows. Leave the address empty to look up the calling server's own address. Used at the moment of a signup, a login or a ticket to adapt what happens next.
- Lookup IP Addresses In Bulk Resolves up to 1,000 IPv4 and IPv6 addresses in a single request, returning one record per address keyed by the IP. This is the action to reach for whenever the alternative is a loop: enriching logs after the fact, backfilling a signup table, or profiling an imported audience list. The Fields parameter trims the payload to the attributes the flow actually reads, and the available attributes follow your subscription plan.
Frequently Asked Questions
What can FlowRunner do with IP2Location.io IP Geolocation?
FlowRunner agents can run Lookup IP Address and Lookup IP Addresses In Bulk in IP2Location.io IP Geolocation.
Does connecting IP2Location.io IP Geolocation to FlowRunner require OAuth?
No. IP2Location.io IP Geolocation connects to FlowRunner with an API key, no OAuth flow required.
Can IP2Location.io IP Geolocation trigger a FlowRunner workflow automatically?
IP2Location.io IP Geolocation doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with IP2Location.io IP Geolocation
$100 in credits. No card required. Connect in minutes.