Resources · Make integration

IPQualityScore Make integrationAutomate IPQualityScore with Make.

Stop fake signups before they reach your CRM. The IPQualityScore Make integration gives you 5 action modules to check emails, phone numbers, IP addresses and transactions. This page shows how to link your API key and build a first working check, step by step.

Try the IPQualityScore integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IPQualityScore Make integration do for you?

The IPQualityScore Make integration lets a Make scenario (the automation you build, a chain of steps) send an email, a phone number, an IP address or a transaction to IPQualityScore and get its verdict back. You never touch the API yourself: each check is a ready module, and your API key is stored once.

A cleaner contact list. When a lead fills in a form, pass the address to Validate an Email and route the doubtful ones to a review list instead of your newsletter tool. Your marketing team stops mailing addresses that bounce.

Safer checkouts. For an online store, Get a Transaction Score gives an order a risk verdict before you ship it, and Validate an IP Address tells you more about where the buyer connects from, which matters when VPN abuse is a concern.

Real people on the phone. A sales team that calls back inbound requests can run Validate a Phone Number first and skip numbers that look fake.

What Make does not do here: the app has no trigger, so IPQualityScore never starts a scenario on its own. Another app or a schedule has to feed it data. The same app often has an n8n node too; the n8n vs Make comparison helps you pick. For a broader take on the tool, read our Make review, or check Make pricing before you scale up.

Connect

How do you connect IPQualityScore to Make?

  1. 01

    Copy your API key

    Log in to IPQualityScore and open your account dashboard. In the settings menu, go to the API section (or API Keys area) and copy the key shown on screen. You need an active IPQualityScore account for this.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any IPQualityScore module and click Create a connection. A connection is your IPQualityScore account linked to Make once, then reused by all five modules.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you run several accounts. Paste the API key you copied, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with IPQualityScore

GoalWhen someone submits your signup form, Make checks the email and the phone number with IPQualityScore before the lead goes any further.

  1. 01

    Start with the app that collects leads

    Create a new scenario from the Scenarios page and click the + to add the first module. Pick the trigger of the tool where signups land, such as your form app, since IPQualityScore has no trigger of its own.

  2. 02

    Add Validate an Email

    Click the + on the right of the first module, search IPQualityScore and choose Validate an Email. Create the connection with your API key, then map the email from the form into the module.

  3. 03

    Chain Validate a Phone Number

    Click the + again and add Validate a Phone Number. Map the phone field from the same form entry, so each signup gets both checks in one pass.

  4. 04

    Test with Run once

    Submit a test entry, then click Run once. Make runs the scenario one time and shows the bundles (the items passed between modules) that each module received, so you can read the verdicts.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default. Then turn the scenario on and let it screen each new lead.

Modules

What each IPQualityScore module does

IPQualityScore gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

IPQualityScore1

Get a Transaction Score

Action

In Make“Retrieves a transaction score.”

You get a risk score for a transaction, so you can decide whether an order ships, waits or goes to a human reviewer.

When to use it
right after a payment or order lands in your store and before fulfillment starts, when the cost of a fraudulent order is higher than a short hold.
Watch out
the score is a signal, not a decision; add a filter after the module so only risky orders take the review path.
IPQualityScore2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This one reaches any endpoint of the IPQualityScore API with the connection you already set up, which covers checks the four ready modules do not offer.

When to use it
when the IPQualityScore documentation describes a check you need and no module matches it.
Watch out
you build the request yourself here, so read the vendor documentation first and test with Run once before mapping the answer further.
IPQualityScore3

Validate an Email

Action

In Make“Validates an existing email.”

Hand it an email address and it returns IPQualityScore's verdict on it, which keeps doubtful addresses out of your mailing lists and CRM.

When to use it
whenever a new contact arrives from a form, an import or a webinar signup, before it is added to your newsletter tool.
Watch out
each check is one operation (one module run on one bundle), so validate at entry rather than re-checking the whole list.
IPQualityScore4

Validate an IP Address

Action

In Make“Validates an existing IP address.”

Pass an IP address and learn what IPQualityScore knows about it, a useful way to spot visitors hiding behind abusive VPNs or known threat sources.

When to use it
on account creation or login events where your app records the visitor's IP, and you want to flag suspicious signups.
Watch out
the module needs the IP from an upstream app; if your form tool does not capture it, there is nothing to validate.
IPQualityScore5

Validate a Phone Number

Action

In Make“Validates an existing phone number.”

It runs a phone number through IPQualityScore so your sales team calls real prospects instead of fake or mistyped numbers.

When to use it
when inbound leads leave a number for a callback, or before you send text messages to a fresh list.
Watch out
the module only checks what you map into it, so confirm in Run once that the phone field, not another one, reaches it.
Need help

Need help automating IPQualityScore with Make?

A person reads every message.

FAQ

IPQualityScore and Make: common questions

01Is the IPQualityScore Make integration free?
Yes on the Make side: IPQualityScore is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Each module run counts as an operation on your plan. You still need an active IPQualityScore account, whose pricing is set by IPQualityScore itself.
02What do you need to connect IPQualityScore to Make?
An active IPQualityScore account and its API key. Log in to IPQualityScore, open your dashboard, go to the API section or API Keys area in the settings, and copy the key. In Make, add any IPQualityScore module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves all five modules, including Make an API Call, so you only do this once per account.
03Does the IPQualityScore Make integration react in real time?
Not by itself, because IPQualityScore has no trigger module in Make. The scenario has to start elsewhere: either on a trigger from the app that collects your data, such as a form or a store, or on a schedule you set with the clock on the first module. A new scenario runs every 15 minutes by default. If the upstream app offers an instant trigger, the checks run as soon as that app calls Make.
04What if a module you need is missing from the IPQualityScore app?
Use Make an API Call. It calls any endpoint of the IPQualityScore API with the same connection, so a check that the four ready modules skip is still reachable. Read the IPQualityScore documentation to build the request, then test it with Run once. Note that the Make documentation for this app is AI-generated from the vendor's docs and may contain mistakes, so confirm important details with IPQualityScore directly. Keep the first test small: one record through Run once shows exactly what the endpoint sends back.
05Should you use Make or n8n for IPQualityScore?
It depends on the tool your team already runs. In Make, IPQualityScore offers five modules: three validations, a transaction score and Make an API Call, all behind one API key connection and a visual editor. The same app often has an n8n node as well, so both routes are possible. Compare the modules each side offers for the checks you need, then pick the platform where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations