Resources · Make integration

MillionVerifier Make integrationAutomate MillionVerifier with Make.

Clean email lists without leaving your usual tools. The MillionVerifier Make integration gives you 9 modules: 8 actions and 1 search. This page is for anyone who collects addresses, and it walks you from connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MillionVerifier Make integration do for you?

The MillionVerifier Make integration links your MillionVerifier account to Make so an address can be checked the moment another tool hands it over. You build a scenario, the automation you design in Make, out of modules, the bricks that each do one job, and MillionVerifier supplies 9 of those bricks. Make's doc gives no description for them, so the roles below are read from the module names: test each one with Run once.

A form that only lets real addresses through. A lead lands in your form tool or your CRM. The next module, Verify an email, checks that single address, and the scenario writes the answer back next to the contact so sales never chases a dead inbox.

A whole list checked in one pass. When a marketing export is ready, Upload a file sends the list to MillionVerifier. Get file info tells you where the job stands, and Download a report brings the results back into the scenario once it is done.

Housekeeping on the account. Check API credits reads your balance before a big job, List files shows what is stored, and Delete a file removes lists you no longer need.

One limit to know upfront: the app has no trigger, so a MillionVerifier event cannot start a scenario. The flow starts from another app, such as the Airtable Make integration, or from a schedule. MillionVerifier may also have an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make training covers the editor from zero.

Connect

How do you connect MillionVerifier to Make?

  1. 01

    Copy your API key

    In MillionVerifier, click your profile icon at the top right, open Account settings, then API KEYS in the menu bar. Copy the key from the list. An active MillionVerifier account is required.

  2. 02

    Add a module and open the connection

    In your scenario, add any MillionVerifier module and click Create a connection. A connection is your MillionVerifier account linked to Make once, then reused by every module of the app.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the API key, follow any on-screen instructions, and save.

First scenario

Your first scenario with MillionVerifier

GoalWhen a new lead arrives in your form or CRM, Make checks the address with MillionVerifier and passes the answer to the next step.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your leads land, since MillionVerifier has no trigger of its own.

  2. 02

    Add Verify an email

    Click the + on the right of that first module, search MillionVerifier and pick Verify an email. Select the connection you created, or click Create a connection.

  3. 03

    Map the address

    In Verify an email, map the address that came from the first module. Each lead travels as a bundle, one item passed from module to module, so the check runs once per lead.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and confirm the address arrived where you expected.

  5. 05

    Schedule and switch on

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

Modules

What each MillionVerifier module does

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

MillionVerifier1

Check API credits

ActionIn the docs only

Reads the credit balance of your MillionVerifier account, so the scenario knows what is left before it spends anything.

When to use it
place it ahead of Upload a file when a large marketing list is about to go through, and add a filter so the run stops if the balance looks too thin.
MillionVerifier2

Delete a file

ActionIn the docs only

Removes a list you uploaded earlier from your MillionVerifier account, which keeps the file area tidy once the results are safely stored elsewhere.

When to use it
at the very end of a bulk flow, after Download a report has saved the results.
Watch out
keep it last in the chain, never before the report is stored.
MillionVerifier3

Download a report

ActionIn the docs only

Brings the verification results of an uploaded list back into Make, where the next module can save them to a sheet, a drive or your CRM.

When to use it
once Get file info shows the job is finished.
Watch out
on the Free plan Make handles files up to 5 MB, so large reports may need a paid plan.
MillionVerifier4

Get file info

ActionIn the docs only

Returns the details of one uploaded list, which is how the scenario learns where a bulk verification stands before it moves on to the results.

When to use it
between Upload a file and Download a report, to confirm the list is ready instead of grabbing a report too early.
MillionVerifier5

List files

SearchIn the docs only

Searches the lists stored in your account and hands them over one by one, which is handy when you need an overview rather than a single file.

When to use it
to review old uploads before a cleanup with Delete a file.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
MillionVerifier6

Make an API call

ActionIn the docs only

Lets you call any endpoint of the MillionVerifier API from your scenario, reusing the same connection, so you are not limited to the eight ready-made actions.

When to use it
when the task you need has no module of its own.
Watch out
you describe the request yourself, so keep the MillionVerifier API documentation open.
MillionVerifier7

Stop a file

ActionIn the docs only

Halts the processing of a list you already sent, which spares you results you no longer want when the wrong export went out.

When to use it
as the emergency branch of a bulk flow, for example when a filter spots that the uploaded file was not the one intended.
Watch out
check the file with Get file info afterwards.
MillionVerifier8

Upload a file

ActionIn the docs only

Sends a whole list of addresses to MillionVerifier in one go, so a marketing export is checked as a batch rather than contact by contact.

When to use it
when a file lands in your drive or a sheet export is ready and you want the full list cleaned.
Watch out
the Free plan caps files at 5 MB in Make.
MillionVerifier9

Verify an email

ActionIn the docs only

Checks a single address and gives its answer straight back to the scenario, the quickest way to screen each new contact as it comes in.

When to use it
right after a form submission or a new CRM record, before a welcome sequence starts.
Watch out
every address is one operation, so a large backlog is better handled with Upload a file.
Need help

Need help automating MillionVerifier with Make?

A person reads every message.

FAQ

Questions about MillionVerifier and Make

01Is the MillionVerifier Make integration free?
Yes, on the Make side. MillionVerifier is a standard app, so it works on the Free plan, which allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the active scenario cap. You still need your own MillionVerifier account and subscription, which is billed by MillionVerifier.
02What does the MillionVerifier Make connection require?
You need an active MillionVerifier account and its API key. In MillionVerifier, click the profile icon at the top right, then Account settings, then API KEYS, and copy the key. In Make, add a MillionVerifier module, click Create a connection, optionally give it a name, and paste the key. The same connection then serves all 9 modules, so you only do this once per account. If Make rejects the key, copy it again in full from API KEYS.
03Can MillionVerifier start a Make scenario in real time?
No. MillionVerifier has no trigger module in Make, so nothing happening in your MillionVerifier account can start a scenario. Put another app first instead: a form, a CRM or a spreadsheet that receives new contacts, then add Verify an email behind it. If you only want periodic checks, a schedule on the first module works too, every 15 minutes by default and down to 1 minute on paid plans. Either way, each module run counts as one operation.
04What if a MillionVerifier module is missing in Make?
Use the Make an API call module. It reaches any endpoint of the MillionVerifier API through the connection you already have, so anything outside the eight ready-made actions stays within reach. Keep the MillionVerifier API documentation at hand, since you write the request yourself. Also note that the Make doc for this app is AI-generated and may contain mistakes, so confirm important details with MillionVerifier. Every call still counts as one operation.
05Is Make or n8n better for MillionVerifier?
It depends on the tool your team already runs. On Make, MillionVerifier offers 9 modules, including Verify an email, Upload a file and a generic API call, and it is available from the Free plan. The same app often has an n8n node too. Compare the modules each side exposes for your use case, check who on your team will maintain the scenario, and pick the tool they are comfortable with.