Resources · Make integration

IPGeolocation.io Make integrationAutomate IPGeolocation.io with Make.

Got an IP address and no idea where it comes from or whether it looks risky? The IPGeolocation.io Make integration gives you 13 action modules to answer that inside an automation. This guide connects your API key and builds a first scenario with you.

Try the IPGeolocation.io integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IPGeolocation.io Make integration do for you?

The IPGeolocation.io Make integration links your IPGeolocation.io account to Make, so a scenario (the automation you build, a chain of modules) can look up an IP address, a time zone or a browser string and pass the answer to your other tools. You fill in fields instead of writing API requests.

Know where a signup comes from. A form tool sends a new lead with its IP address, Get IP Geolocation looks it up, and your CRM receives the location next to the contact. Sales can route the lead without asking.

Flag a suspicious visitor before it costs you. An online shop can pass each order IP to IP Security Lookup and hold the order for review when the check raises a concern. When a whole export of IPs needs checking at once, Bulk IP Security Lookup takes the list.

Read the device behind a visit. Parse User Agent turns the raw browser string a website logs into something a person can read, which helps a support team reproduce a bug on the right browser.

What the app does not have: any trigger. IPGeolocation.io never starts a scenario by itself, so the flow opens on another app or on a schedule. The Make documentation also lists these modules by name only, without describing their fields, so open each module to see what it asks for. The Make review covers the editor in depth, and if you are weighing tools, read n8n vs Make.

Connect

How do you connect IPGeolocation.io to Make?

  1. 01

    Copy your API key

    You need an active IPGeolocation.io account and an API key. Log in, open the Dashboard, and copy the API key shown on screen. Keep that tab open, you will paste it in the next step.

  2. 02

    Add a module and create the connection

    In Make, add any IPGeolocation.io module to your scenario and click Create a connection. A connection is your account linked to Make once, then reused by every IPGeolocation.io module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied and save. The module is then ready for its fields.

First scenario

Your first scenario: check every new signup IP

GoalWhen another app hands Make a new IP address, Make locates it with IPGeolocation.io and runs a security check on it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that receives your signups, such as your form tool, and its trigger.

  2. 02

    Add Get IP Geolocation

    Click the + on the right of the first module, search for IPGeolocation.io and choose Get IP Geolocation. Create the connection with your API key if you have not done it yet.

  3. 03

    Map the IP address

    In the module fields, map the IP address that the first module received. Each signup travels as one bundle, meaning one item passed from a module to the next, so each one gets its own lookup.

  4. 04

    Chain IP Security Lookup

    Add IP Security Lookup after the geolocation module and map the same IP. You now hold both answers and can send them on to a sheet or your CRM with a further module.

  5. 05

    Test with Run once

    Click Run once and submit a test signup. Make runs the scenario one time and shows the bundles each module received, so you can read what IPGeolocation.io returned before going live.

  6. 06

    Schedule and switch on

    Open the clock on the first module to set the schedule (every 15 minutes by default on a new scenario), then switch the scenario on. From there it runs without you.

Modules

What can each IPGeolocation.io module do?

IPGeolocation.io gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

IPGeolocation.io1

Bulk IP Security Lookup

ActionIn the docs only

Runs a security check on a whole list of IP addresses in a single step, so a batch of visitors is screened together rather than one by one.

When to use it
you exported the IPs behind a wave of failed logins or a campaign's clicks and want the risky ones picked out of the lot.
Watch out
the answers come back for many IPs at once, so plan how the next module splits or filters them before you send anything on.
IPGeolocation.io2

Get Bulk IP Geolocation

ActionIn the docs only

Locates many IP addresses in one go, which saves you from building a loop around the single lookup when your data already arrives as a list.

When to use it
a spreadsheet of visitor IPs needs a location column before a regional report goes out.
Watch out
run it with Run once on a short list first and read the bundles, so you see how the results are shaped before mapping them into a sheet.
IPGeolocation.io3

Get IP Geolocation

ActionIn the docs only

Gives you the location behind one IP address, the classic lookup and the module most scenarios start with on this app.

When to use it
each new lead, order or support ticket carries an IP, and you want the place attached to that record as it arrives.
Watch out
the module expects an IP, so map the IP field from the previous module, not the whole bundle or an email address.
IPGeolocation.io4

IP Security Lookup

ActionIn the docs only

Tells you whether a single IP address looks risky according to IPGeolocation.io, which lets a scenario decide what to do before a person even looks.

When to use it
a checkout or signup should pause for manual review when the IP behind it raises a flag.
Watch out
a flag is a signal, not a verdict. Route flagged cases to a person or a review list rather than deleting anything automatically.
IPGeolocation.io5

Lookup ASN

ActionIn the docs only

Returns the ASN details IPGeolocation.io holds, the autonomous system number that identifies the network an IP belongs to. It answers which network owns this address, a question the location lookup does not.

When to use it
an IT team sees odd traffic and wants to know which provider or company operates the network behind it.
Watch out
open the module to check what input it asks for, since the documentation does not list its fields.
IPGeolocation.io6

Lookup Abuse Contact

ActionIn the docs only

Finds who to contact about abuse coming from an IP address. Your report then reaches the network owner, not a generic inbox.

When to use it
after IP Security Lookup flags repeated attacks, you want the address to send a complaint to, prepared for a person to review.
Watch out
keep a human step before any message goes out. One wrong result is enough for an unattended scenario to send a complaint to the wrong people.
IPGeolocation.io7

Lookup Astronomy

ActionIn the docs only

Brings astronomy data for a place into your scenario. Judging by its name, it is the kind of sun and moon information outdoor or event planning depends on.

When to use it
a booking for a shoot or an outdoor event needs the day's light conditions written into the confirmation.
Watch out
the documentation does not list the module's fields, so check in the module which location and date inputs it expects.
IPGeolocation.io8

Lookup Astronomy Time Series

ActionIn the docs only

Judging by its name, it covers a span of dates rather than one day, which is the difference with Lookup Astronomy: you get a series you can drop into a sheet or a calendar.

When to use it
a photography studio plans a series of outdoor sessions and wants the data for every date in one table.
Watch out
a series brings back many values at once, so read the bundle in Run once before mapping it row by row.
IPGeolocation.io9

Lookup Timezone Information

ActionIn the docs only

Gives the time zone that applies to a place, which keeps meetings and reminders from landing in the middle of the night for the other person.

When to use it
a new customer books a call and you want the invite and the reminder set in their local time, not yours.
Watch out
pair it with Time Conversion when you need a specific time shifted, since knowing the zone alone does not move a date.
IPGeolocation.io10

Make an API Call

ActionIn the docs only

Calls any endpoint of the IPGeolocation.io API from your scenario, with the same connection, for the cases the other twelve modules do not cover.

When to use it
the IPGeolocation.io documentation describes a request you need and no ready-made module offers it.
Watch out
here you write the request yourself, so keep the vendor documentation open and test with Run once before relying on it.
IPGeolocation.io11

Parse Bulk User Agents

ActionIn the docs only

Decodes a list of user agent strings at once, the long text a browser sends with each visit, into readable device and browser information.

When to use it
a log export holds a large batch of visits and you want a clean breakdown of browsers for a product review.
Watch out
the list comes back as one block of results, so add a step that splits or aggregates it before writing it to a sheet.
IPGeolocation.io12

Parse User Agent

ActionIn the docs only

Turns one raw user agent string into something a human can read, so a support agent sees the browser and device instead of a line of code.

When to use it
a bug report form captures the visitor's user agent and the ticket should state the browser plainly.
Watch out
map the user agent field itself. Pass the IP or the whole form bundle instead, and the module has nothing to decode.
IPGeolocation.io13

Time Conversion

ActionIn the docs only

Shifts a time from one zone to another, the step that turns your office hours into the hour your customer will actually see.

When to use it
an appointment is stored in your own zone and the confirmation email must show the client's local hour.
Watch out
check in Run once which date format comes out before mapping it into an email, so the hour reads correctly.
Need help

Need help automating IPGeolocation.io with Make?

A person reads every message.

FAQ

IPGeolocation.io and Make: common questions

01Is the IPGeolocation.io Make integration free?
Yes on the Make side: IPGeolocation.io is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Every module execution counts as an operation on your plan. Paid Make plans lower the interval to 1 minute and allow runs of 40 minutes. IPGeolocation.io has its own subscription for the API key, described on its pricing page; this page quotes no price for it.
02What do you need to connect IPGeolocation.io to Make?
An active IPGeolocation.io account and its API key. Log in to IPGeolocation.io, open the Dashboard and copy the key shown there. In Make, add any IPGeolocation.io module, click Create a connection, optionally give it a name, and paste the key. That single connection then serves all 13 modules, so you only do this once per account. If the key is refused, copy it again from the Dashboard and check that the account is active.
03Can an IPGeolocation.io scenario start on its own in Make?
No. IPGeolocation.io has no trigger module in Make, only 13 actions, so it never starts a scenario by itself. You start the flow in one of two ways. Either another app's trigger opens the scenario, for example a form tool reporting a new signup with its IP, or you set a schedule on the first module, every 15 minutes by default and never under 15 minutes on the Free plan. The IPGeolocation.io modules then do the lookups in the middle of the flow.
04What if the IPGeolocation.io module you need is missing in Make?
Use Make an API Call. It is part of the 13 modules and lets you call any endpoint of the IPGeolocation.io API from your scenario, with the same connection, so a request the ready-made modules skip is still within reach. You write the request yourself, using the vendor documentation. Note that the Make documentation for this app warns that it was generated with AI from the vendor docs and may contain mistakes, so verify key details with IPGeolocation.io directly.
05Should you use Make or n8n for IPGeolocation.io?
It depends on the tool your team already builds in. In Make, IPGeolocation.io comes with 13 action modules, including Make an API Call for anything they leave out, and a visual editor where each lookup is a module you click together. The same app often has an n8n node too, so check what exists there before you choose. Pick the platform where your other automations already live, since the lookups only matter once they feed the rest of your process.
Same platform

Other docs you might need on this stack.

Browse all integrations