Lee este artículo en español.

How to validate an email in Make (HTTP module)

Q: What if the email has a good format but the domain doesn't exist?

format_valid comes back true but valid comes back false, because mx_found is false.

If you automate lead intake with Make (formerly Integromat), sooner or later you'll get a badly typed or made-up email. Before that contact lands in your CRM or triggers a welcome email, it's worth checking it. With the HTTP module and the Cofferdock API, you check it in one step, nothing extra to install.

An honest heads-up: Make has no dedicated "validate email" module. You do it with the generic HTTP module calling an API that runs two checks: that the format is correct, and that the domain actually has a mail server behind it (MX record). A good-looking email on a domain that doesn't exist gets caught too.

What you'll get

You send the email and it tells you whether it's valid, whether the format is correct, and whether the domain has a real MX record (mail server). No "looks like an email" guesswork: a real check against DNS.

Common uses in Make:

Filtering leads from a form before creating them in your CRM.
Rejecting made-up emails at sign-up.
Cleaning a list before importing it into your email marketing tool.
Checking an order's email before sending the confirmation.

What you need

A Cofferdock account. The free tier gives you 50 uses/month with no card.
Your API key, from your dashboard with "+ Create key". It's shown only once.
The HTTP → Make a request module in your scenario.

Step by step in the HTTP module

Add the HTTP → Make a request module and set it up like this:

URL: https://api.cofferdock.com/validate-email
Method: POST
Headers: add two → x-api-key with your key, and Content-Type with the value application/json.
Body type: Raw
Content type: JSON (application/json)
Request content:

{ "email": "{{1.email}}" }

Turn on Parse response: this time the response is JSON, not an image.

The response includes valid (true/false), format_valid, mx_found and domain. With a Router or a Filter right after, you decide what to do based on valid.

A quick example

Say you filter form leads before creating them in your CRM:

A module that catches the lead (a webhook from the form, or Google Sheets → Watch Rows).
The HTTP module above, which validates the email.
A Router with two routes: one with a Filter valid = true that continues to the CRM, and another with valid = false that flags it for manual review.

Leads with fake emails no longer clutter your CRM.

Options you can tweak

Add it in the same JSON body:

Option	Default	What it does
`check_mx`	`true`	Set it to `false` to check only the format (faster, no DNS lookup).

Prefer to see it in code?

The same call with curl:

curl -X POST "https://api.cofferdock.com/validate-email" \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "hello@example.com"}'

How much does it cost?

Each check uses 1 credit from your plan, whether the email comes back valid or not. Every Cofferdock tool draws from the same pool of credits.

FAQ

Does Make have a native module to validate emails? No. You do it with the generic HTTP module calling the Cofferdock API.

Do I need to turn on "Parse response"? Yes, this time you do: the response is JSON, so turn it on to map valid, format_valid and mx_found in later modules.

What if the email has a good format but the domain doesn't exist? format_valid comes back true but valid comes back false, because mx_found is false.

Can I validate several emails at once? Yes. If the previous module returns several items, Make runs the HTTP module once per item.

Related guides

Try it yourself

You'll find the full instructions, with copy-paste examples, on the email validation page. And if you don't have an account yet, you can create one for free and build your first scenario today.