Resources · Make integration

IP2WHOIS Make integrationAutomate IP2WHOIS with Make.

Need the WHOIS record of a domain without opening a lookup tool each time? The IP2WHOIS Make integration gives you 1 action module that fetches it inside a scenario. This page shows how to link your API key, then walks you through a first working scenario.

Try the IP2WHOIS integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IP2WHOIS Make integration do for you?

The IP2WHOIS Make integration lets a Make scenario ask IP2WHOIS for the WHOIS record of a domain and pass the answer to the next step. A scenario is the automation you build in Make, a chain of modules, and a module is one brick of that chain. IP2WHOIS brings exactly one brick: an action you feed a domain name.

Because the app has no trigger, the lookup always sits behind something else. Picture a sales team whose inbound form collects a company website: the form app starts the scenario, Lookup a WHOIS Record for a Domain pulls the record for that domain, and the result lands next to the lead, so nobody pastes domains into a browser tab by hand.

A second use: a list of domains kept in a spreadsheet. A scheduled scenario reads the rows, runs the same lookup on each one, and writes the record back beside it. Each domain is a bundle, one item flowing from module to module, and each lookup counts as one operation on your Make plan.

A third one, for a security or IT desk: when a suspicious domain gets reported in a ticket, the scenario queries IP2WHOIS and adds the WHOIS record to the ticket before anyone opens it.

What Make will not do here: IP2WHOIS offers no trigger and no Make an API Call module, so anything beyond this single lookup needs another app. The official documentation also warns that it is AI-generated from the vendor docs, so double-check important details with IP2WHOIS. If you are weighing tools, the n8n vs Make comparison helps, and the Make training covers the editor from zero.

Connect

How do you connect IP2WHOIS to Make?

  1. 01

    Copy your API key

    Log in to your IP2Location.io account, open the dashboard, then go to the API section or Settings, where credentials live. Copy the API key shown on screen. You need an active IP2WHOIS account first; the subscription details sit on the IP2WHOIS pricing page.

  2. 02

    Open the connection window

    In your scenario, add the IP2WHOIS module and click Create a connection. A connection is your IP2WHOIS account linked to Make once, then reused by every IP2WHOIS module you add later. The Connection name field is optional but handy.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, then confirm. The connection now appears in the module, ready to use in this scenario and in any other one you build.

First scenario

Your first scenario with IP2WHOIS

GoalWhen a new domain shows up in another app, Make looks up its WHOIS record with IP2WHOIS and passes it on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot belongs to the app where your domains appear, such as a form or a sheet.

  2. 02

    Set the starting module

    Search that app by name, pick the module that returns new entries, and click Create a connection for it. Fill its fields; Make lists what it can read once the account is linked.

  3. 03

    Add the IP2WHOIS lookup

    Click the + on the right of the first module, search IP2WHOIS and choose Lookup a WHOIS Record for a Domain. Link your API key, then map the domain coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time, and you can open each module to read the bundles it received, including the WHOIS record IP2WHOIS sent back.

  5. 05

    Schedule and switch on

    On the first module, open the clock and set the schedule, every 15 minutes by default, then switch the scenario on. From now on, each new domain gets looked up without you.

Modules

What the IP2WHOIS module does

IP2WHOIS gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

IP2WHOIS1

Lookup a WHOIS Record for a Domain

ActionIn the docs only

Hand this action a domain name and you get its WHOIS record back as data the next module can use, without leaving Make.

When to use it
right after the module that collects domains, for instance a lead form asking for a company website or a ticket reporting a strange link.
Watch out
every domain processed is one operation, and the official documentation is AI-generated, so check important details with IP2WHOIS.
Need help

Need help automating IP2WHOIS with Make?

A person reads every message.

FAQ

IP2WHOIS and Make: common questions

01Is the IP2WHOIS Make integration free?
Yes, on the Make side. IP2WHOIS is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, and at most 5 minutes per execution. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Make counts each module run as an operation, so every domain you look up uses one. On the IP2WHOIS side you need an active account and an API key; check the IP2WHOIS pricing page for subscription terms.
02What do you need to connect IP2WHOIS to Make?
An active IP2WHOIS account and its API key. You find the key in your IP2Location.io dashboard, under the API section or Settings. In Make, add the IP2WHOIS module to a scenario, click Create a connection, optionally give the connection a name, then paste the key. That connection is stored once and reused by every IP2WHOIS module you add afterwards, in this scenario or another. No developer access or code is involved at any point.
03Does the IP2WHOIS Make integration run in real time?
It depends on what starts your scenario, because IP2WHOIS has no trigger of its own. The lookup always follows another module. If that first module is a scheduled trigger, Make checks for new data on the schedule you set, every 15 minutes by default and never more often than every 15 minutes on the Free plan. If the first module is an instant trigger from another app, which calls Make through a webhook as soon as something happens, the lookup runs right after that event.
04What if the IP2WHOIS module you need is missing in Make?
Then you have to work around it, because IP2WHOIS offers only one module, Lookup a WHOIS Record for a Domain, and no Make an API Call module to reach other IP2WHOIS features. You can pair the lookup with modules from other apps to store, filter or forward the result. For anything the app does not cover, look for another app in Make's catalog of 3000+ standard apps, or ask the team to scope a custom setup with you.
05Make or n8n for IP2WHOIS?
It depends on the tool your team already uses. On Make, IP2WHOIS gives you a single lookup action that you chain behind a form, a sheet or any other starting module, all in a visual editor with a Free plan to test on. The same app often has an n8n node as well, so the choice comes down to where the rest of your workflows live rather than to this app. Compare both editors on a small scenario before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations