Resources · Make integration

emailvalidation Make integrationAutomate emailvalidation with Make.

Stop guessing whether an address is worth keeping. The emailvalidation Make integration gives you 2 action modules that check an address from inside a scenario. This guide is for marketers and ops leads: link your account, build a first check, then decide what to automate next.

Try the emailvalidation integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the emailvalidation Make integration do for you?

The emailvalidation Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) send an email address to emailvalidation and get the verification back, without code. It has no trigger of its own, so another app or a schedule starts the flow.

A cleaner signup list. A form tool hands over a new contact, Verify an Email Address checks the address, and the rest of the scenario only continues for the contacts you decide to keep. Each item passing between modules is called a bundle: here, one contact.

A check before a CRM record. Sales teams can place the same module right before the step that creates a lead, so you can set doubtful addresses aside instead of filing them.

Calls the listed modules do not cover. Make an API Call reaches any endpoint of the emailvalidation API with the connection you already set up, which is handy once you know the API documentation.

What Make does not give you here: a trigger. Nothing fires when something happens inside emailvalidation, so plan your starting point elsewhere. Every module run on one bundle counts as one operation on your plan; the Make pricing page explains how plans count them. The same app often has an n8n node too, and n8n vs Make lays out the differences. If a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect emailvalidation to Make?

  1. 01

    Copy your API key

    Log in to your emailvalidation account, open the dashboard, go to the Settings section, then the API or API key tab. Copy the key shown on screen. You need an active emailvalidation account before any of this works.

  2. 02

    Add a module and open the connection

    In your Make scenario, add an emailvalidation module and click Create a connection. A connection is your emailvalidation account linked to Make once, then reused by both modules of the app.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key you copied and save. Make now lets the module talk to your account.

First scenario

Build your first scenario with emailvalidation

GoalWhen a new contact reaches the app that collects your signups, Make sends the address to emailvalidation and lets you read the answer.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module comes from the app that holds your new addresses, such as your form tool.

  2. 02

    Add the verification

    Click the + on the right of that first module, search for emailvalidation and pick Verify an Email Address. Choose the connection you created, or click Create a connection now.

  3. 03

    Map the address

    In the module fields, map the email address coming from the previous module instead of typing one. Make shows the data it received, so you click the right item rather than guessing its name.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and what emailvalidation sent back for your test contact.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Then switch the scenario on so it keeps working without you.

Modules

What the emailvalidation modules do

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

emailvalidation1

Make an API Call

ActionIn the docs only

This one gives you access to the rest of the emailvalidation API, using the connection you already set up, so you are not stuck with the single ready-made module. You pick the endpoint and send the request yourself.

When to use it
the emailvalidation documentation describes a call that Verify an Email Address does not offer and you need it inside the same scenario.
Watch out
you write the request by hand here, so keep the API documentation open and test with Run once before switching anything on.
emailvalidation2

Verify an Email Address

ActionIn the docs only

Here is the module that gives you an answer about one address at a time: it sends the email to emailvalidation and passes the result along to the next module of your scenario, with no code involved.

When to use it
right after a form, a spreadsheet row or a CRM step hands over a contact, before you add that person to a list.
Watch out
each address checked uses one operation, so place it after any filter that already drops contacts you would never keep.
Need help

Need help automating emailvalidation with Make?

A person reads every message.

FAQ

emailvalidation and Make: common questions

01Is the emailvalidation Make integration free?
Yes, on the Make side. emailvalidation is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a scheduled run at most every 15 minutes, up to 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. You still need an active emailvalidation account with its own subscription, which is handled on the emailvalidation side, not in Make.
02What does the emailvalidation Make integration need to connect?
Two things: an active emailvalidation account and its API key. Log in to emailvalidation, open the Settings section of your dashboard, then the API or API key tab, and copy the key. In Make, add an emailvalidation module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves both modules of the app, so you only do this once per account.
03Does the emailvalidation Make integration react in real time?
No, because emailvalidation has no trigger module in Make. Nothing inside emailvalidation can start a scenario. Instead, begin the scenario with a trigger from the app that receives your contacts, such as a form or CRM module, or let the Make schedule start it. A new scenario runs every 15 minutes by default, and paid plans allow intervals down to 1 minute. The verification then happens as a step in the middle of the flow.
04What if an emailvalidation module is missing in Make?
Use Make an API Call. It reaches any endpoint of the emailvalidation API with the connection you already created, so a call that Verify an Email Address does not offer can still sit inside your scenario. You write the request yourself, so keep the emailvalidation API documentation next to you and test with Run once. The Make documentation page for this app also notes that its content is generated from vendor documentation, so confirm details with emailvalidation when something looks off.
05Is Make or n8n better for emailvalidation?
It depends on where the rest of your automations live. This page covers the Make side: 2 modules, a connection built on your API key, and Make an API Call for anything else. The same app often has an n8n node as well, so check what it offers before choosing. If your forms, CRM and lists are already wired in one of the two tools, keeping the email check in that same tool means one connection to maintain and one place to debug.
Same platform

Other docs you might need on this stack.

Browse all integrations