Resources · Make integration

IP2Location.io IP Geolocation API Make integrationAutomate IP2Location.io IP Geolocation API with Make.

Got an IP address and need to know where it comes from, without leaving your automation? The IP2Location.io IP Geolocation API Make integration gives you 1 action module, Lookup an IP Address. This guide is for ops and growth builders: connect your API key, then build a first scenario around it.

Try the IP2Location.io IP Geolocation API integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you do with the IP2Location.io IP Geolocation API Make integration?

The IP2Location.io IP Geolocation API Make integration lets a Make scenario, the automation you build in Make as a chain of bricks called modules, send an IP address to IP2Location.io and get its geolocation back. There is a single module, an action named Lookup an IP Address, so the work is about feeding it the right address and using what comes out.

Since this app has no trigger, something else always starts the flow. Here are three typical setups, presented as examples rather than client stories.

Qualify inbound leads. A signup form in another app passes along the visitor's IP. Lookup an IP Address resolves it, and the next module writes the location into your CRM so sales sees where the lead is before calling.

Flag odd logins. For a SaaS team, a login event from your product reaches Make through a webhook, the lookup runs, and a filter sends a message to support when the address looks out of place for that account.

Enrich an order log. An e-commerce shop can push each new order with its IP into Make and store the location next to the order in a spreadsheet, which helps when a payment dispute lands later.

What Make will not do here: watch IP2Location.io for events, since the app exposes no trigger, and there is no Make an API Call module to reach other endpoints. The same service may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ. For a wider view of the platform, read our Make review, or check Make pricing before you plan volume.

Connect

How do you connect IP2Location.io IP Geolocation API to Make?

  1. 01

    Copy your API key

    You need an active IP2Location.io account and an API key. Log in, open your user dashboard, click the API Keys section in the menu and copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add the module and open the connection

    In your Make scenario, add the Lookup an IP Address module and click Create a connection. A connection is your IP2Location.io account linked to Make once, then reused by every module of this app.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you want to spot it easily later; it is optional. Paste the API key you copied, or follow the on-screen instructions, and save the connection.

First scenario

Your first scenario with IP2Location.io IP Geolocation API

GoalWhen another app hands Make a visitor's IP address, Make looks it up in IP2Location.io and passes the location to the next step.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. That first module comes from the app that already holds the IP, such as your form tool or a Make webhook.

  2. 02

    Set up the starting module

    Pick that app, choose the module that delivers the records you care about and create its connection. Each record it returns becomes a bundle, one item flowing to the next module.

  3. 03

    Add Lookup an IP Address

    Click the + on the right of the first module, search IP2Location.io IP Geolocation API and pick Lookup an IP Address. Select your connection, then map the IP value from the previous module into the module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received and check that the lookup returned data for your test IP.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, to decide how often Make checks for new records. Then switch the scenario on so each new IP gets looked up without you.

Modules

What the IP2Location.io IP Geolocation API module does

IP2Location.io IP Geolocation API gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

IP2Location.io IP Geolocation API1

Lookup an IP Address

ActionIn the docs only

Turns a raw IP address into geolocation data you can reuse further down the scenario, so a bare number in a form entry or a log line becomes a place.

When to use it
right after the module that brings in the IP, before the step that stores or routes the record, so the location travels with it.
Watch out
it is an action, so it runs once per bundle and each run counts as an operation on your plan; filter out empty IP values before this step.
Need help

Need help automating IP2Location.io IP Geolocation API with Make?

A person reads every message.

FAQ

IP2Location.io IP Geolocation API and Make: common questions

01Is the IP2Location.io IP Geolocation API Make integration free?
Yes, on the Make side. It is a standard app, so it works on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits, meaning operations, each month. Your IP2Location.io subscription is separate: check the vendor's own pricing page for what your API key allows.
02What do you need to connect IP2Location.io IP Geolocation API to Make?
An active IP2Location.io account and an API key. After logging in, open your user dashboard, go to the API Keys section and copy the key. In Make, add the Lookup an IP Address module, click Create a connection, optionally name it, then paste the key. The connection is stored once and reused by any module of this app in your other scenarios, so you only do this setup a single time.
03Can the IP2Location.io IP Geolocation API Make integration start a scenario by itself?
No. The app has no trigger module, so it never starts a scenario on its own. You start the flow another way: with a trigger from the app that holds the IP, such as a form or a CRM, with a Make webhook your product calls, or with a plain schedule on the first module, every 15 minutes by default. Lookup an IP Address then runs as the second step, once per bundle it receives from that first module.
04What if the IP2Location.io IP Geolocation API Make module does not do what you need?
It depends on the gap. The app offers only Lookup an IP Address and no Make an API Call module, so you cannot reach other endpoints of the service through this app. When the lookup itself is enough, build the rest with modules from other apps in the same scenario. When the need goes beyond it, look for another app in Make that covers it, or ask our team to scope a custom setup with you.
05Should you use Make or n8n for IP2Location.io IP Geolocation API?
It depends on the tool your team already runs. On Make, the lookup is a ready module that takes an API key and fits into a visual scenario next to your form, CRM or spreadsheet apps. The same service often has an n8n node too, so if your automations already live in n8n, stay there. The honest criterion is where the rest of your workflow sits, not the lookup, since both tools can call it from a flow.
Same platform

Other docs you might need on this stack.

Browse all integrations