Resources · Make integration

Veriphone Make integrationAutomate Veriphone with Make.

Can a phone number be checked the moment it lands in another tool? The Veriphone Make integration gives you 3 action modules for that job. This page is for ops and sales teams who keep contact lists clean, and it walks you from connection to a first working scenario.

Try the Veriphone integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Veriphone Make integration do?

The Veriphone Make integration links your Veriphone account to Make so a scenario, the automation you build as a chain of modules, can send phone numbers to Veriphone without code. A module is one brick of that chain. Veriphone brings 3 action modules and no trigger, so another app or a schedule starts the flow.

Screen signups before they reach sales. A form tool or a CRM starts the scenario, and Verify a Phone checks the number it received, so your team only calls leads worth calling. The 123FormBuilder Make integration is one possible starting point.

Build a safe test case. Get a Phone Example fetches a sample number from Veriphone, which is handy when you want to try a scenario without touching real customer data.

Reach what the menu does not show. Make an API Call uses the same connection to call any endpoint of the Veriphone API, for the day the two other modules fall short.

Keep in mind that the Make documentation for this app is AI-generated from Veriphone's own docs and may contain mistakes, so check anything critical with Veriphone. The same app often exists as an n8n node too; the n8n vs Make comparison lays out the differences, and Make pricing explains the plans.

Connect

How do you connect Veriphone to Make?

  1. 01

    Copy your Veriphone API key

    Log in to Veriphone, open the control panel, go to the Account section and copy the API key shown there. You need an active Veriphone account for this; the plan side is on Veriphone's pricing page.

  2. 02

    Open the connection window

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

  3. 03

    Paste the key and save

    The Connection name field is optional, though a clear label helps once you juggle several accounts. Paste the API key you copied or follow the on-screen instructions. Save, and you are done.

First scenario

Your first scenario with Veriphone

GoalWhen a new contact arrives in another app, Make sends the number to Veriphone and passes the result to the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add a first module. Pick the app that holds your new contacts, such as your form tool.

  2. 02

    Add Verify a Phone

    Click the + to the right of that first module, search for Veriphone and choose Verify a Phone. Click Create a connection and paste your API key.

  3. 03

    Map the phone number

    Fill the module by mapping the phone number that the first module received. Each item passing between modules is a bundle: here, one bundle is one contact.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and confirm the number went through.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on, and each run of each module counts as one operation on your plan.

Modules

What can the Veriphone modules do?

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

Veriphone1

Get a Phone Example

ActionIn the docs only

This module gives you a sample phone number from Veriphone, so you can build and test a flow with harmless data instead of a real customer record.

When to use it
you are setting up a new scenario and want the later modules to receive a number before any real contact arrives.
Watch out
the Make documentation does not describe what the sample contains, so read its bundle after Run once before mapping anything.
Veriphone2

Make an API Call

ActionIn the docs only

With Make an API Call you reach any endpoint of the Veriphone API from your scenario, reusing the connection you already created, without a second key.

When to use it
the task you need is not covered by Verify a Phone or Get a Phone Example.
Watch out
you write the request yourself, so keep Veriphone's API documentation open and remember that the Make docs for this app may contain mistakes.
Veriphone3

Verify a Phone

ActionIn the docs only

Verify a Phone is the heart of this app: as its name says, it sends a phone number to Veriphone for checking. The Make docs do not detail the answer, so read its bundle after Run once.

When to use it
a lead, an order or a signup arrives in another app and you want the number checked before it reaches your CRM or your call list.
Watch out
every number checked costs one operation, so filter out empty entries earlier in the flow.
Need help

Need help automating Veriphone with Make?

A person reads every message.

FAQ

Veriphone and Make: common questions

01Is the Veriphone Make integration free?
Yes, on the Make side. Veriphone is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB 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. You still need your own active Veriphone account, whose pricing is set by Veriphone.
02What is needed to connect Veriphone to Make?
You need an active Veriphone account and its API key. Log in to Veriphone, open the control panel, go to the Account section and copy the key. Then, in Make, add a Veriphone module, click Create a connection, optionally name it, and paste the key. That single connection serves all three Veriphone modules, including Make an API Call, so you only set it up once. If you later add a second Veriphone account, create a separate connection and pick it in each module.
03Does the Veriphone Make integration have a trigger?
No. Veriphone offers no trigger module in Make, only 3 actions. The scenario therefore starts elsewhere: a trigger from another app, such as a form or a CRM that receives new contacts, or the schedule on the first module, which runs a new scenario every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. Verify a Phone then runs as the next step for each contact received.
04What if a Veriphone module is missing in Make?
It depends on what you need. The list has only three modules, but Make an API Call calls any endpoint of the Veriphone API with the connection you already have, so it covers most gaps. Since the Make documentation for Veriphone is AI-generated and may contain mistakes, compare it with Veriphone's own API docs before relying on an endpoint, and contact Veriphone directly when something does not match. The Make troubleshooting guide on this site also helps with failed runs.
05Make or n8n for Veriphone: which one fits?
It depends on your team and your existing tools. Veriphone often exists as an n8n node as well, so both routes can work. In Make you get 3 ready modules, a visual editor with Run once for testing, and Make an API Call for anything else. If your other automations already live in one of the two tools, keeping Veriphone there is the simplest choice. The comparison page on this site sets out the criteria side by side, without ranking one above the other.
Same platform

Other docs you might need on this stack.

Browse all integrations