Resources · Make integration

mails.so Make integrationAutomate mails.so with Make.

Want every new email address checked before it reaches your list? The mails.so Make integration gives you 2 action modules, one to validate a single address and one to call the mails.so API directly. This page shows how to connect your account and build a first scenario.

Try the mails.so integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the mails.so Make integration do for you?

The mails.so Make integration lets a Make scenario, the automation you build as a chain of modules, send an email address to mails.so and get the validation result back. Each module is one brick of that chain. mails.so has no trigger of its own, so another app or a schedule starts the flow, and mails.so does the checking in the middle.

Cleaner sign-up lists. A form tool sends each new lead to Make, Validate a Single Email checks the address, and the result travels to the next module as a bundle, one item passed along the chain. You then decide what happens to that lead.

A safer CRM import. Before a sales rep's contact lands in your CRM, the same module checks it, so the contact arrives with its validation answer attached.

Anything the listed modules skip. Make an API Call reaches any endpoint of the mails.so API with the connection you already set up.

Be aware of one limit: Make's own documentation for mails.so is short, because little public information exists about the app. Expect to read the returned bundles in Run once to learn what mails.so sends back. If something breaks, Make troubleshooting walks through the usual fixes, and Make pricing explains how operations are counted.

Weighing tools? The same app often has an n8n node too, and n8n vs Make lays out the differences between the two platforms.

Connect

How do you connect mails.so to Make?

  1. 01

    Add a mails.so module

    In your scenario, search for mails.so, pick a module, then click Create a connection. A connection is your mails.so account linked to Make once and reused by both modules.

  2. 02

    Name the connection

    Giving it a name is optional, but a clear label helps later when a teammate opens the scenario and wonders which mails.so account it uses.

  3. 03

    Authorize and save

    Authorize Make on the mails.so page, or paste the key mails.so gives you, depending on what the window asks for. Click Save and the connection appears in the module.

First scenario

Your first scenario with mails.so

GoalWhen a new contact shows up in another app, Make asks mails.so to validate that address.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Because mails.so has no trigger, this first module comes from the app that holds your contacts.

  2. 02

    Set the starting module

    Pick the module of that other app that returns your new contacts, connect its account and fill its fields. Make lists what it can read once the connection exists.

  3. 03

    Add Validate a Single Email

    Click the + on the right, search mails.so and choose Validate a Single Email. Create the connection, then map the email address coming from the first module.

  4. 04

    Test with Run once

    Click Run once. The scenario runs one time, and you can open each module to read the bundles it received, including the answer mails.so returned.

  5. 05

    Schedule and switch 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 you lifting a finger.

Modules

What the mails.so modules do

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

mails.so1

Make an API Call

ActionIn the docs only

Gives you access to the whole mails.so API from inside a scenario, with the connection you already created, so nothing is out of reach when the other module does not cover your need.

When to use it
you need a mails.so feature that Validate a Single Email does not offer, and you know which endpoint handles it.
Watch out
Make's documentation for mails.so is limited, so check the mails.so API reference for the endpoint before you build around it.
mails.so2

Validate a Single Email

ActionIn the docs only

Judging by its name, since Make gives no description, it checks one email address at a time and passes the result to the rest of your scenario so doubtful contacts don't slip into your tools unnoticed.

When to use it
right after a form, a shop or a CRM hands Make a fresh address, before that address is stored anywhere else.
Watch out
each address checked is one operation on your Make plan, so place the module where it only sees addresses you actually need to validate.
Need help

Need help automating mails.so with Make?

A person reads every message.

FAQ

Questions about the mails.so Make integration

01Is the mails.so Make integration free?
Yes, on the Make side. mails.so is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your mails.so account is a separate matter.
02What do you need to connect mails.so to Make?
A mails.so account and a Make account. Make's documentation gives no specific prerequisite for this app, so the generic steps apply: add a mails.so module, click Create a connection, optionally name it, then authorize Make on the mails.so page or paste the key mails.so provides, and click Save. The connection is stored once and reused by both modules, Validate a Single Email and Make an API Call. If the window asks for something you cannot find, look in your mails.so account settings first.
03Can mails.so start a Make scenario by itself?
No. mails.so has no trigger module in Make, neither scheduled nor instant, so it cannot launch a scenario on its own. The scenario starts from another app, such as your form tool or your CRM, or from the schedule set on the first module, which runs every 15 minutes by default on a new scenario. mails.so then sits in the middle of the flow and validates the addresses that the first module passes along. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.
04What if the mails.so module you need is missing in Make?
Use Make an API Call. With this module, any endpoint of the mails.so API can be called from your scenario, using the same connection as Validate a Single Email. That covers whatever the 2 listed modules do not. Keep in mind that Make's documentation for mails.so is limited because little public information exists about the app, so the mails.so API reference is where you confirm which endpoint to call. Test the call with Run once and read the returned bundle before you switch the scenario on.
05Should you use Make or n8n for mails.so?
It depends on the platform your team already runs. On Make, mails.so offers 2 modules: Validate a Single Email for everyday checks and Make an API Call for the rest of the API, all without code. The same app often has an n8n node as well, so look at what each side offers for mails.so before choosing. Neither tool is ranked here: compare the modules available, how your other apps connect, and where your existing scenarios or workflows already live. The comparison page linked above goes through the broader differences.
Same platform

Other docs you might need on this stack.

Browse all integrations