Resources · Make integration

MailboxValidator Make integrationAutomate MailboxValidator with Make.

Can Make check an email address before it pollutes your list? The MailboxValidator Make integration gives you 4 action modules and no trigger. This guide is for anyone who collects addresses from forms or imports, and it walks you from the connection to a first working scenario.

Try the MailboxValidator integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MailboxValidator Make integration do?

The integration lets a Make scenario, the automation you build as a chain of modules, send an email address to MailboxValidator and get a verdict back. A module is one brick of that chain. MailboxValidator offers four of them, all actions, so something else has to start the scenario: another app, or the Make schedule.

Screen signups before they reach sales. A lead arrives from a form app, Single Email Validator checks the address, and only then does the contact move on to your CRM. Your reps stop chasing inboxes that do not exist.

Keep throwaway addresses out of trials. A SaaS team can pass each new account through Disposable Email and flag the ones that look temporary, instead of discovering them when the first invoice bounces.

Separate personal and business contacts. A B2B marketer can run Free Email on inbound requests and route free webmail addresses to a nurture list while company domains go to a sales rep.

What the page cannot promise: the Make documentation lists these modules without describing their fields or outputs, and it warns that its own text is AI-generated and may contain mistakes. Run each module once and read what comes back before you build logic on it. If you need an endpoint the four modules skip, Make an API Call reaches the rest of the API. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick a tool, Make pricing covers the plans, and Make training covers the editor in depth.

Connect

How do you connect MailboxValidator to Make?

  1. 01

    Copy your API key

    Log in to MailboxValidator and open your account dashboard. Find the section labeled API key or API credentials and copy the key shown there. You need an active MailboxValidator account for this; the subscription is handled on their side.

  2. 02

    Add a module and click Create a connection

    In your Make scenario, add any MailboxValidator module and click Create a connection. A connection is your account linked to Make once, then reused by every MailboxValidator module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the on-screen instructions Make shows, then save. The module is now ready to fill, and the next MailboxValidator module you add will offer the same connection in its list.

First scenario

Your first scenario with MailboxValidator

GoalWhen a new email address arrives in another app, Make checks it with MailboxValidator and flags throwaway inboxes.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since MailboxValidator has no trigger, pick the app where your new addresses show up, such as a form tool.

  2. 02

    Add Single Email Validator

    Click the + on the right of that first module, search for MailboxValidator and pick Single Email Validator. Choose your connection, then map the email address coming from the previous module.

  3. 03

    Add Disposable Email

    Add one more module the same way and pick Disposable Email. Map the same address. Each module run on one bundle, meaning one item such as one contact, counts as one operation on your plan.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each MailboxValidator module received: that is where you learn which values you can use in the next step.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval you can pick.

Modules

What each MailboxValidator module is for

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

MailboxValidator1

Disposable Email

ActionIn the docs only

Judging by its name, it asks MailboxValidator whether an address belongs to a throwaway inbox, the kind people create to grab a download and then abandon. You get an answer you can filter on before the contact goes further.

When to use it
on trial signups or coupon requests, where a temporary inbox usually means the person never planned to come back.
Watch out
the documentation does not describe the output, so run it once and check which value you filter on.
MailboxValidator2

Free Email

ActionIn the docs only

As its name suggests, it tells you whether an address comes from a free webmail provider rather than a company domain. That single answer lets a scenario split personal contacts from business ones without anyone reading the list by hand.

When to use it
on demo requests in a B2B funnel, to send company domains to a sales rep and the rest to a nurture list.
Watch out
a free address is not a bad address, so route it instead of deleting it.
MailboxValidator3

Make an API Call

ActionIn the docs only

Opens the whole MailboxValidator API from your scenario, using the connection you already created. Reach for it when the three ready-made checks fall short.

When to use it
when the MailboxValidator documentation shows an endpoint that none of the other modules offer.
Watch out
you build the request yourself, so keep the MailboxValidator API reference open while you fill it in.
MailboxValidator4

Single Email Validator

ActionIn the docs only

Its name points to a check of one address with MailboxValidator's verdict, the result most scenarios want first. Each contact passing through costs one operation, so one lead equals one check.

When to use it
right after a form submission or a CRM import, before the address receives any email from you.
Watch out
it handles one address per bundle; for a whole file, the scenario processes each row as its own bundle, and each one counts.
Need help

Need help automating MailboxValidator with Make?

A person reads every message.

FAQ

MailboxValidator and Make: common questions

01Is the MailboxValidator Make integration free?
Yes on the Make side. MailboxValidator is a standard app, so it works on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits per month. The MailboxValidator side is separate: you need an active account with them, and their own pricing page covers the subscription.
02What do you need to connect MailboxValidator to Make?
An active MailboxValidator account and its API key. Log in, open the account dashboard, find the section labeled API key or API credentials and copy the key. In Make, add any MailboxValidator module, click Create a connection, give it a name if you like, and paste the key. That single connection is then reused by all four MailboxValidator modules, so you only do this once per account. If the key is refused later, go back to the same dashboard section, copy the key shown there and paste it into a new connection.
03Does MailboxValidator trigger a Make scenario in real time?
No, because MailboxValidator has no trigger module at all. All four modules are actions, so the scenario has to start elsewhere. The usual choice is a trigger from the app where addresses come in, like a form or a CRM, with MailboxValidator placed right after it. You can also start the scenario on the Make schedule, which runs every 15 minutes by default, if you want to check a batch of contacts stored somewhere else.
04What if a MailboxValidator module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the MailboxValidator API with the connection you already have, so anything the three ready-made modules skip stays within reach. Keep in mind that the Make documentation for this app is AI-generated and flagged as possibly inaccurate, so confirm each endpoint in the MailboxValidator API reference and test with Run once before you switch the scenario on. For anything that needs a trigger, pair it with the module of another app that can start the scenario.
05Should you use Make or n8n for MailboxValidator?
It depends on the tool your team already works in. Make offers four MailboxValidator modules, Make an API Call included, all usable from the Free plan. The same app often has an n8n node as well. There is no reason to switch tools for this app alone: if your other automations already live in Make, keep the email checks next to them, and if they live in n8n, look at the node there first.
Same platform

Other docs you might need on this stack.

Browse all integrations