Resources · Make integration

Numverify Make integrationAutomate Numverify with Make.

Need to know whether a phone number is worth calling before it lands in your tools? The Numverify Make integration gives you one action, Verify Phone Number, that you drop into any flow. This guide links your account and builds a first working scenario with you.

Try the Numverify integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Numverify Make integration do for you?

The Numverify Make integration lets a Make scenario, the automation you build in Make as a chain of bricks, send a phone number to Numverify and get its details back. There is a single brick, called a module, and it is an action: it does not start anything by itself, it checks the number another app hands over.

Screen form sign-ups before sales calls. A contact form or a lead tool starts the scenario, Verify Phone Number checks the number, and only the records you trust move on to your sales team. Fewer wasted dials, less guessing.

Tidy a contact list as it grows. When a spreadsheet row or a CRM contact is added, the scenario sends its phone field to Numverify and writes the details it returns next to the contact. A support desk gets the same benefit on incoming tickets.

Guard an SMS or calling tool. Place the check right before a messaging app such as the one covered in the 2Chat Make integration, so your scenario only messages numbers whose returned details you are happy with.

What the app does not do: it has no trigger, so something else always starts the scenario, and it has no Make an API Call module for requests the action does not cover. Numverify also often has an n8n node; if you are weighing both tools, read n8n vs Make. To learn the editor properly, the Make training starts from zero.

Connect

How do you connect Numverify to Make?

  1. 01

    Copy your API key from Numverify

    You need an active Numverify account with an API Access Key. Log in to Numverify, open the dashboard, and copy the API key shown there. Keep that tab open, you will paste the key into Make a moment later.

  2. 02

    Add the module and open the connection window

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when a team shares several accounts. Paste the API key you copied from the dashboard, confirm, and Make saves the connection.

First scenario

Build your first scenario with Numverify

GoalWhen a new contact arrives from another app, Make checks the phone number with Numverify and passes the details along.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Numverify has no trigger, this first module comes from the app that holds your contacts, such as a form or a sheet.

  2. 02

    Pick the starting app

    Search the app that receives new contacts, choose its module and link its account. Each new contact becomes a bundle, one item that flows from a module to the next one.

  3. 03

    Add Verify Phone Number

    Click the + on the right of the first module, search Numverify and pick Verify Phone Number. Choose your connection, then map the phone value from the previous module into the number to check.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and confirm Numverify sent details back for your test number.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each check counts as one operation, meaning one run of one module on one bundle, on your Make plan.

Modules

What the Numverify module does

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

Numverify1

Verify Phone Number

Action

In Make“Verifies the phone number and gets all details.”

You hand it a phone number and get back the details Numverify holds on it, as a bundle the following modules can read. Your scenario can then sort, store or act on it.

When to use it
right after the module that brings in a new contact, and before the one that saves it or sends it a message.
Watch out
the Make doc for this app is flagged as AI-generated, so run a few test numbers with Run once and read the returned bundle before trusting any single detail.
Need help

Need help automating Numverify with Make?

A person reads every message.

FAQ

Numverify and Make: common questions

01Is the Numverify Make integration free?
Yes on the Make side: Numverify is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans drop the interval to 1 minute and allow 40 minutes of execution. Your Numverify account and its API key are separate, and their subscription is set on the Numverify side, so check the Numverify pricing page for that part.
02What do you need to connect Numverify to Make?
An active Numverify account and its API Access Key. After logging in to Numverify, the key sits on the dashboard: copy it. In Make, add the Numverify module, click Create a connection, give the connection a name if you like, and paste the key. The connection is then reused by every Numverify module in your scenarios, so you only do this once per account. If the connection is refused, recopy the key without spaces.
03Can Numverify start a Make scenario in real time?
No, because Numverify has no trigger in Make: its only module is an action. The scenario has to start from something else. Most often that is the trigger of the app where contacts arrive, such as a form, a sheet or a CRM, which is either scheduled, polled every 15 minutes by default, or instant when that app calls Make through a webhook. Verify Phone Number then runs as the next step for each bundle it receives.
04What if the Numverify module you need is missing in Make?
It depends on what you need. Numverify in Make offers one action, Verify Phone Number, and no Make an API Call module, so there is no generic way to reach other Numverify requests from this app. If the check covers your need, build around it. If not, look for another app in Make that does the job, or ask the team for help reviewing the case and suggest a workable setup.
05Should you use Make or n8n for Numverify?
It depends on where the rest of your automations live. Numverify often has an n8n node too, so the phone check itself is rarely the deciding factor. If your contact sources, CRM and messaging apps already run in Make scenarios, adding Verify Phone Number there keeps everything in one editor. If your team already works in n8n, stay there. Compare the two on the tools you already use and on how your team prefers to build.
Same platform

Other docs you might need on this stack.

Browse all integrations