Resources · Make integration

Reoon Email Verifier Make integrationAutomate Reoon Email Verifier with Make.

Need to clean an email list before a campaign goes out? The Reoon Email Verifier Make integration gives you 7 action modules, and no trigger, to check one address or a whole batch without code. This page shows how to link your account and walks you through a first scenario.

Try the Reoon Email Verifier integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Reoon Email Verifier Make integration do for you?

The Reoon Email Verifier Make integration links your Reoon account to Make, the no-code tool where you build a scenario: the automation itself, a chain of modules. A module is one brick of that chain. Reoon brings 7 of them, all actions, to check an address, run a bulk check or read your balance.

Screen signups as they arrive. A form or another app starts the scenario, then Verify a Single Address (Quick) or Verify a Single Address (Power) checks the email it just received. You map Reoon's answer into the next module to keep, tag or drop the contact.

Check a whole list in one go. Going by the module names, Create a Bulk Verification Task sends a batch to Reoon, Get a Bulk Task Status tells you whether it is done, and Get a Bulk Task Result brings the verdicts back so a later module can update your list.

Keep an eye on your balance. Check an Account Balance, as its name suggests, reads what is left on your Reoon account, which is useful before a large batch. For anything the listed modules miss, Make an API Call reaches other endpoints of the Reoon API with the same connection.

What Make does not give you here: a trigger. Reoon has none in Make, so your scenario starts from another app or from Make's own schedule. Make also marks the Reoon documentation as limited, so test every module with Run once before relying on it. To go further, the Make training covers the basics, Make troubleshooting helps when a run fails, and n8n vs Make sets the two tools side by side.

Connect

How do you connect Reoon Email Verifier to Make?

  1. 01

    Add a Reoon module

    In your scenario, click the + and search for Reoon Email Verifier, then pick any of its modules. Make asks for a connection, meaning your Reoon account linked to Make once and reused by every Reoon module. Click Create a connection.

  2. 02

    Name the connection

    Naming the connection is optional, but it pays off as soon as you handle more than one Reoon account, say one for a client and one for tests. A clear label saves you from guessing later when you pick it inside a module.

  3. 03

    Authorize and save

    Follow what the window asks: approve Make on the Reoon page, or paste the key that Reoon gives you. Then click Save. The connection now shows up in the module, ready for every other Reoon module in your scenarios.

First scenario

Build your first scenario with Reoon Email Verifier

GoalWhen a new contact lands in another app, Make checks the email with Reoon and passes the verdict to the next module.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. Click the + to add the first module. Since Reoon has no trigger, this one comes from the app that collects your contacts, such as a form or a CRM.

  2. 02

    Add the Reoon check

    Click the + on the right of that first module, search for Reoon Email Verifier and choose Verify a Single Address (Quick). Select your connection, or click Create a connection if you have none yet.

  3. 03

    Map the address

    In the Reoon module, map the email coming from the first module. Each contact that flows in is a bundle, one item passed from a module to the next, and Reoon checks them one at a time.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received, and look at the answer Reoon sent back before you add the module that will use it.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each Reoon Email Verifier module does

Reoon Email Verifier gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Reoon Email Verifier1

Check an Account Balance

ActionIn the docs only

Going by its name, it reads what is left on your Reoon account, so a scenario can look at the balance before it spends anything on checks. The documentation does not say which figures come back, so read them during a Run once test.

When to use it
right before Create a Bulk Verification Task, to stop the scenario when the balance looks too low for the list.
Watch out
this module costs an operation too, so avoid placing it in front of every single check.
Reoon Email Verifier2

Create a Bulk Verification Task

ActionIn the docs only

Hands a whole batch of addresses to Reoon instead of checking them one by one. Going by its name, it opens a task that Reoon processes on its side, and you collect the verdicts with another module later.

When to use it
when a full list lands at once, after an event import or a trade show, rather than contact by contact.
Watch out
creating the task does not give you the answers; pair it with Get a Bulk Task Status and Get a Bulk Task Result.
Reoon Email Verifier3

Get a Bulk Task Result

ActionIn the docs only

Brings back the verdicts of a bulk task so you can clean your list with them. Its name points to the output of a task started earlier by Create a Bulk Verification Task.

When to use it
once Get a Bulk Task Status shows the batch is done, to send the results to your CRM or spreadsheet module.
Watch out
the documentation does not describe the output, so try it on a small batch and read the bundles before you map anything.
Reoon Email Verifier4

Get a Bulk Task Status

ActionIn the docs only

As its name suggests, this module tells you whether a bulk task is still running or finished, which keeps you from reading results too early. It works on the task created by Create a Bulk Verification Task.

When to use it
as a checkpoint between launching a batch and fetching its results.
Watch out
the documentation gives no processing time, so never assume a batch is finished just because the next module runs.
Reoon Email Verifier5

Make an API Call

ActionIn the docs only

Opens the rest of the Reoon API to your scenario: you call any endpoint of that API with the same connection as the other modules. It covers what the six ready-made modules leave out.

When to use it
when the Reoon feature you need has no module of its own in Make.
Watch out
you write the request yourself, so double-check the endpoint path and method, then validate the call with Run once.
Reoon Email Verifier6

Verify a Single Address (Power)

ActionIn the docs only

Checks one email address in Reoon's Power mode, the counterpart of the Quick module. Make's documentation does not explain how the two modes differ, so compare their answers on a few addresses of your own.

When to use it
for an address that matters, like a lead about to enter your sales pipeline, once a test has shown you what Power adds.
Watch out
each check is one operation in Make, whichever mode you pick.
Reoon Email Verifier7

Verify a Single Address (Quick)

ActionIn the docs only

Gives you a verdict on a single email address with Reoon's Quick mode, the lighter sibling of Power going by the names. It fits a scenario that fires on each new contact.

When to use it
behind a signup form or a newsletter tool, to screen addresses as they come in.
Watch out
the documentation does not list what Quick skips compared with Power, so run both on the same address before choosing.
Need help

Need help automating Reoon Email Verifier with Make?

A person reads every message.

FAQ

Reoon Email Verifier and Make: common questions

01Is the Reoon Email Verifier Make integration free?
Yes, on the Make side. Reoon Email Verifier is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits each month. What Reoon charges for its own checks is a separate question that this page does not cover, so look at your Reoon account for that.
02What do you need to connect Reoon Email Verifier to Make?
A Reoon account and a Make account. Make's documentation lists no other prerequisite and gives no app-specific steps, so the usual path applies: add a Reoon module, click Create a connection, name it if you like, then authorize Make or paste the key Reoon gives you, and click Save. The connection is created once and reused by all 7 modules. Test it right away with Run once on Check an Account Balance before building the rest of the scenario.
03Does Reoon Email Verifier have a trigger in Make?
No. All 7 modules are actions, so nothing in Reoon starts a scenario on its own. You start it another way: from a trigger of another app, such as a form or a CRM that watches for new contacts, or from Make's schedule on the first module, which runs every 15 minutes by default. Reoon then sits in the middle of the flow and checks the address that the previous module hands over.
04What if a Reoon Email Verifier module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Reoon API with the connection you already have, so a feature without its own module stays within reach. Keep in mind that Make labels its Reoon documentation as limited: it does not detail fields, output formats or limits. Before building a long scenario, test each module with Run once and read the bundles it returns. If a behavior still blocks you, a module from another verification app may fit better.
05Make or n8n for Reoon Email Verifier?
It depends on the tool your team already runs. In Make, Reoon comes with 7 ready-made action modules, Make an API Call among them, and the editor lets you test each step with Run once. This page does not cover whether n8n offers a Reoon node, so check its node list before comparing. Choose the tool where your other apps already live, since the scenario will mostly move data between them. The comparison linked earlier on this page lays out how the two tools differ.
Same platform

Other docs you might need on this stack.

Browse all integrations