Resources · Make integration

Email List Verify Make integrationAutomate Email List Verify with Make.

Catch a bad email address before it lands in your CRM. The Email List Verify Make integration gives you 3 action modules: check one address, check a file of addresses, or call the API directly. This page shows you how to connect your key and build a first scenario.

Try the Email List Verify integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Email List Verify Make integration do for you?

With it, Make sends email addresses to Email List Verify and gets the verification result back inside a scenario, the automation you build in Make as a chain of modules. You pick the addresses, Make asks Email List Verify, and the next module of your scenario decides what to do with the answer.

A signup form that filters itself. When a new lead arrives from your form tool, Verify an Email checks the address first, and only then does the contact go on to your CRM or mailing tool. An address that fails the check never reaches your database.

A purchased or exported list, checked in one pass. Before a sales team imports an old list, Verify Emails in a File takes the whole file instead of one address at a time, which keeps the scenario short.

Anything the two modules skip. Make an API Call reaches any endpoint of the Email List Verify API with the same connection, so you are not limited to the two ready-made actions.

What Make does not do here: the app has no trigger, so Email List Verify never starts a scenario on its own. Something else starts it, another app or the schedule. The official documentation also warns that it was written with AI help and asks you to confirm important details with Email List Verify. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, and Make pricing explains how operations are counted on each plan.

Connect

How do you connect Email List Verify to Make?

  1. 01

    Copy your API key

    Log in to Email List Verify and open the dashboard. Click the API section in the menu and copy the key shown on that page. You need an active Email List Verify account for this: the key is what Make uses to speak for you.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any Email List Verify module and click Create a connection. A connection is your Email List Verify 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 once you have several accounts. Paste the API key you copied, follow the instructions on screen, and save. The module can now talk to Email List Verify.

First scenario

Your first scenario: check every new signup

GoalWhen a new contact arrives from another app, Make checks the address with Email List Verify before passing it on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Email List Verify has no trigger, this first module comes from the app that collects your contacts.

  2. 02

    Pick the app that brings the contacts

    Search your form or CRM app by name, choose its module and link the account. Each new contact it returns becomes a bundle: one item that flows from this module to the next one.

  3. 03

    Add Verify an Email

    Click the + on the right of the first module, search Email List Verify and pick Verify an Email. Use the connection you created, then map the email field coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received and check that Email List Verify returned a result for your test address.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From then on, each new contact gets checked without anyone opening Make.

Modules

What each Email List Verify module does

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

Email List Verify1

Make an API Call

ActionIn the docs only

This module opens the full Email List Verify API to your scenario, reusing the connection you already set up, so you can reach an endpoint that has no ready-made module.

When to use it
when neither Verify an Email nor Verify Emails in a File covers what you need and the API documentation of Email List Verify lists the request you want.
Watch out
you write the request yourself, so read the vendor documentation first and test the call with Run once before switching the scenario on.
Email List Verify2

Verify Emails in a File

ActionIn the docs only

Hand this module a file of addresses and it sends the whole batch to Email List Verify, which saves you from building a loop around the single-address module.

When to use it
a list exported from an old tool or collected at an event, which you want checked before it goes into your mailing platform.
Watch out
the Make Free plan caps files at 5 MB. Big export? Split it, or move to a paid plan first.
Email List Verify3

Verify an Email

ActionIn the docs only

You get a verdict on one address at the moment it enters your process, so an address that fails the check can be stopped before it reaches your CRM.

When to use it
right after a form submission, a new lead or a new customer record, in a scenario that handles contacts one by one.
Watch out
each address is one bundle, and every run of the module on a bundle is one operation, the unit Make counts on your plan, so a long list costs one operation per contact.
Need help

Need help automating Email List Verify with Make?

A person reads every message.

FAQ

Email List Verify and Make: frequent questions

01Is the Email List Verify Make integration free?
Yes, on the Make side. Email List Verify is a standard app, available from the Free plan. That plan lets you keep 2 active scenarios, waits at least 15 minutes between two scheduled runs, stops a run after 5 minutes, and handles files up to 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. Email List Verify itself needs an active account and an API key; its own pricing is on the vendor's site and is not covered here.
02What does connecting Email List Verify to Make require?
Two things: an active Email List Verify account and its API key. Once logged in, open the dashboard, click the API section in the menu and copy the key displayed there. In Make, add any Email List Verify module, click Create a connection, optionally give it a name, and paste the key. The same connection then serves the three modules of the app, including Make an API Call, so you only do this once per account.
03Can an Email List Verify scenario start on its own in real time?
No. Email List Verify has no trigger module in Make, so it cannot start a scenario by itself. You start the scenario another way: with a trigger from the app that collects your contacts, such as a form or a CRM, or with the schedule set on the first module, every 15 minutes by default on a new scenario. The Email List Verify modules then run as steps in the middle of the flow, on the addresses that arrive.
04What if an Email List Verify module is missing in Make?
Use Make an API Call. With the connection you already have, it can call any endpoint of the Email List Verify API, so an action that has no dedicated module is still within reach. Check the request in the vendor documentation first. The Make documentation for this app states that it was produced with AI help and may contain mistakes, and it asks you to confirm important information directly with Email List Verify. When in doubt, test with Run once before switching the scenario on.
05Is Make or n8n better for Email List Verify?
It depends on the tool your team already runs. In Make, Email List Verify offers 3 modules: one address, one file, and a direct API call, all usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Email List Verify before you choose, and compare what each tool exposes for this app rather than general promises. The comparison page linked higher on this page sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations