IP2WHOIS Zapier integrationAutomate IP2WHOIS with Zapier.
The IP2WHOIS Zapier integration counts 0 triggers, 0 actions and 1 search. That single search, Query WHOIS, fetches the WHOIS record of a domain name halfway through a Zap. Another app has to start the Zap, and the search step puts it on a paid plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the IP2WHOIS Zapier integration actually does
In plain terms: whenever another app hands a Zap a domain name, IP2WHOIS looks up the WHOIS record of that domain. Nothing starts on the IP2WHOIS side: a form, a spreadsheet or a help desk fires first, then the Query WHOIS step fetches the record so the next steps can store it, route it or send it to a person.
Three results people build with it, all on Query WHOIS. A lead sheet where each new company website arrives with its domain record already pulled, so sales stops copying domains into a lookup tool by hand. A review queue for a security or compliance team, where a filter keeps only the entries that carry a domain before the lookup runs. A support thread that gets the record of a suspicious domain posted next to the ticket, so whoever triages it reads one place instead of three.
Now the limits, because they shape every Zap. IP2WHOIS has no trigger on Zapier, so it cannot watch a domain and react when its record changes. It has no action either, so nothing gets written back into IP2WHOIS. The only input the search takes is a domain name (the Domain field is required), and there is no find-or-create variant. In short: a lookup tool you call from the middle of a Zap, nothing more.
The same app also exists on Make: see the IP2WHOIS Make integration page. If n8n is on your shortlist too, start with n8n vs Zapier.
The Zapier words, in one minute
Eight words come back on every line of this page. Here is what each one means, in plain terms.
- Zap
- The automation you build on Zapier: one event starts it, then one or more steps run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. IP2WHOIS offers none.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer, at an interval set by your plan. An instant one is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it everywhere else.
- Search step
- A step that looks up something that already exists, so later steps can use what it found. Query WHOIS is one.
- Connection
- Your account of an app linked to Zapier once, then reused by every step that calls that app in any Zap.
What it really costs
IP2WHOIS is not a premium app, so the connection itself works on the free plan. The catch sits in the Zap shape.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo
- Zap with Query WHOISMulti-step, paid plan
The free plan only builds two-step Zaps: one trigger, one action. Query WHOIS is a search step, and a Zap carrying a search (or a filter, or a second action) becomes a multi-step Zap that needs a paid plan. The trigger never costs a task, every action that succeeds costs one, and an action that fails costs nothing. The interval grid below applies to the app that starts the Zap: a polling trigger waits for its next check, while an instant one fires straight away on any plan.
Connect IP2WHOIS to Zapier in three steps
- 01
Open your Apps page
You need an IP2WHOIS account first. In Zapier, open Apps from your account, then click + Add connection. A dialog opens with a search box for the app.
- 02
Pick IP2WHOIS
Type IP2WHOIS in the dialog, select it in the results, then click Add connection. A new browser tab opens on the IP2WHOIS side. Keep the Zapier tab open behind it, you will come back to it.
- 03
Sign in and grant access
Sign in to IP2WHOIS in that tab and grant Zapier access to the account. The connection now shows up on your Apps page, and every Zap that uses Query WHOIS reuses it without asking again.
Your first Zap: look up every domain that comes in
GoalEach new form entry that contains a website gets its WHOIS record, and the result lands in a spreadsheet row.
- 01
Build: start on another app
Create a Zap and pick the app that receives domain names, here your form tool, plus the event that starts it. IP2WHOIS cannot start a Zap, so the first card always belongs to someone else.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent entries of the connected account, so pick one that really contains a website before mapping anything.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field to watch (the website), the rule and the value. Entries with no domain stop here and never reach the lookup.
- 04
Add Query WHOIS
Add a step, pick IP2WHOIS, and look under the SEARCH heading of the Action event list for Query WHOIS. Map the website field into Domain, then test the step and read the record that came back.
- 05
Write the result, then publish
Add the spreadsheet step, map the fields from the lookup into the columns, test it once, then click Publish. The Zap is on, and only entries that arrive from now on go through it.
The IP2WHOIS search, explained
1 search step looks for data that already exists in IP2WHOIS, so a later step can use it.
A search step does not change anything: it fetches a record and hands it to the steps that follow. Three settings decide what happens when the result is not what you expected.
Query WHOIS
SearchIn Zapier“Query WHOIS record”
Give it a domain name and it returns the WHOIS record of that domain, ready to be mapped into a sheet, a CRM field or a message. Domain is the one field it insists on.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a lookup that comes back empty stops the Zap and skips every step that relied on it. Switched on, the Zap carries on with nothing in hand.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. IP2WHOIS offers no such variant, so you will not see it on Query WHOIS.
- If multiple search results are found?Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks
Zapier attaches no help article to IP2WHOIS, so the failures below are the general ones, read through a lookup-only app.
Most broken IP2WHOIS Zaps come from the step before the lookup or from Zapier's own rules, not from IP2WHOIS. If you are stuck, our Zapier troubleshooting page walks through the usual fixes.
No backlog, ever
A Zap only reacts to what happens after you switch it on. Domains already sitting in your sheet or form history are never looked up, and moving them is a separate job.An empty lookup stops the Zap
With the default setting, a Query WHOIS that finds nothing halts the run and every step after it is skipped. Turn the setting on if the rest should run anyway.A loop that eats tasks
If the last step writes into the very sheet or list your trigger watches, each new row starts the Zap again, and your task count drains fast.A bulk import gets held back
Paste a big batch of domains at once and the trigger returns a flood of items. Zapier's flood protection can hold them back instead of running them all.
Need help automating IP2WHOIS with Zapier?
A person reads every message.
