Resources · Make integration

IPLocate IP Geolocation API Make integrationAutomate IPLocate IP Geolocation API with Make.

Got IP addresses piling up in forms, logs or sign-ups and no idea where they come from? The IPLocate IP Geolocation API Make integration gives you 4 action modules to look them up without code. This guide covers the API key, a first scenario and each module.

Try the IPLocate IP Geolocation API integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IPLocate IP Geolocation API Make integration do?

The IPLocate IP Geolocation API Make integration lets a Make scenario, the automation you build step by step, send an IP address to IPLocate and get back what the service knows about it. You pick the lookup you need, and the answer flows on to the next app of your scenario.

Know where a lead signs up from. A form app starts the scenario, Look Up an IP Address Location checks the visitor's IP, and the result lands next to the contact in your CRM or sheet. Sales knows where the request comes from before the first call.

Flag risky traffic before it costs you. An online shop can pass each checkout IP to Look Up an IP Address Privacy & Threat Data and route suspicious orders to a manual review channel instead of shipping blind.

Get the full picture in one call. When one module should return everything IPLocate has on an address, Look Up an IP Address is the general lookup, and Make an API Call reaches any endpoint the listed modules leave out.

What the app does not have: triggers. IPLocate never starts a scenario on its own, so another app or Make's own clock opens the flow. Before you rely on a field, check it with a test run, since the official documentation is thin. The same service is often available as an n8n node too; the n8n vs Make comparison helps you choose, and the Make training covers the editor basics.

Connect

How do you connect IPLocate IP Geolocation API to Make?

  1. 01

    Copy your API key

    You need an active IPLocate account and an API key. Open your account dashboard, click the API section and copy the key shown on the screen. Keep that tab open, you will paste it in a moment.

  2. 02

    Add a module and create the connection

    In your scenario, add any IPLocate IP Geolocation API module and click Create a connection. A connection is your IPLocate account linked to Make once, then reused by all four modules. Give it a clear Connection name if you like, this field is optional.

  3. 03

    Paste the key and save

    Paste the API key in the credentials field and follow the on-screen instructions to save. The module now shows your connection, and you can move on to filling its fields with the IP you want to check.

First scenario

Build your first scenario with IPLocate IP Geolocation API

GoalWhen another app hands Make a new IP address, Make asks IPLocate for its privacy and threat data so you can act on it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Here it comes from the app that collects the IP, such as your form or shop tool.

  2. 02

    Set up the starting app

    Pick that app's module, connect your account and fill its fields. Each new entry it sends becomes a bundle, one item passed from module to module, and it should carry the visitor's IP.

  3. 03

    Add the IPLocate lookup

    Click the + on the right, search IPLocate IP Geolocation API and choose Look Up an IP Address Privacy & Threat Data. Select your connection, then map the IP from the first module into the lookup.

  4. 04

    Test with Run once

    Click Run once and send one real entry through the starting app. Read the bundles it received and check what IPLocate returned for that IP.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each lookup counts as one operation, the unit Make bills on your plan.

Modules

What each IPLocate IP Geolocation API module does

IPLocate IP Geolocation API gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

IPLocate IP Geolocation API1

Look Up an IP Address

ActionIn the docs only

Hand this module one IP address and you get back the general record IPLocate keeps on it, in a single bundle your next modules can map. It is the broad lookup of the app.

When to use it
you want everything at once on a visitor or a server address and do not yet know which details you will keep.
Watch out
run it once on a real IP and read the output before mapping, because the documentation does not list the returned fields.
IPLocate IP Geolocation API2

Look Up an IP Address Location

ActionIn the docs only

This lookup answers the question most teams ask first: where is this address located? You receive the location data for the IP you pass, ready to write into a CRM, a sheet or a message.

When to use it
a lead fills in a form and sales wants to know where the lead is located before calling back.
Watch out
keep it for location needs; if you also care about risk, the privacy and threat module is the one to add.
IPLocate IP Geolocation API3

Look Up an IP Address Privacy & Threat Data

ActionIn the docs only

With this module you learn what IPLocate knows about the privacy and threat side of an address, so your scenario can decide whether an order, a login or a sign-up deserves a second look.

When to use it
an online shop wants to hold suspicious checkouts for review instead of shipping them straight away.
Watch out
the documentation does not describe the returned fields, so run it once on a known address and read the result before building any rule on it.
IPLocate IP Geolocation API4

Make an API Call

ActionIn the docs only

Your escape hatch: this module calls any endpoint of the IPLocate API with the connection you already set up, so nothing the three ready-made lookups leave out is off limits.

When to use it
the IPLocate API documentation describes a request none of the listed modules covers.
Watch out
you build the request yourself, so read the IPLocate API reference first and test the call with Run once before mapping anything.
Need help

Need help automating IPLocate IP Geolocation API with Make?

A person reads every message.

FAQ

IPLocate IP Geolocation API and Make: common questions

01Is the IPLocate IP Geolocation API Make integration free?
Yes on the Make side: it is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops each run after 5 minutes and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the active scenario cap. Your IPLocate account and its own subscription are separate: check the IPLocate pricing page for what your API key includes.
02What is needed to connect IPLocate IP Geolocation API to Make?
Two things: an active IPLocate IP Geolocation API account and its API key. You find the key in your account dashboard, under the API section. In Make, add any IPLocate module, click Create a connection, optionally name it, then paste the key and save. That one connection is reused by all four modules, so you only do this once per IPLocate account. If saving fails, copy the key again and make sure your IPLocate account is active.
03Can IPLocate IP Geolocation API start a scenario in real time?
No, the app has no trigger, so it never starts a scenario by itself. You open the flow with another app: a form, a shop or a database module that sends a new IP, and the IPLocate lookup comes right after. If that first module is an instant trigger, called by its app through a webhook, the lookup runs as soon as the entry arrives. If it is scheduled, Make checks it on the scenario schedule, every 15 minutes by default.
04What if an IPLocate IP Geolocation API module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the IPLocate API with the connection you already have, which covers what the three ready-made lookups do not. You write the request from the IPLocate API reference, then test it with Run once and read the returned bundle before mapping it. The Make documentation for this app is marked as AI-generated from the vendor's own docs, so confirm important details with IPLocate directly.
05Make or n8n for IPLocate IP Geolocation API: which fits better?
It depends on the tool your team already builds in. In Make, IPLocate gives you 4 modules, including three ready-made lookups and a generic API call, with no trigger. The same service often exists as an n8n node too. Compare what each tool offers for your exact lookup, check which one your other apps already live in, and pick the editor your team will actually maintain. The n8n vs Make comparison on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations