Resources · Make integration

Email Make integrationAutomate Email with Make.

Your inbox can sort, flag and forward mail while nobody looks at it. The Email Make integration gives you 11 modules: one trigger that spots new messages and ten that copy, move, mark, draft or send. This guide connects your mailbox and walks you through a first working scenario.

Try the Email integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Email Make integration do for you?

The Email Make integration links a mailbox to Make, a no-code automation tool, so incoming messages can start a scenario (the automation you build, a chain of steps) and other steps can act on your mail. Each step is a module: a trigger that watches, an action that does something, or an iterator that splits a list.

A support inbox that routes itself. Watch Emails catches each new message matching your criteria, Send an Email to a Team Member alerts the right person, and Move an Email files the original away so the shared inbox stays readable.

Invoices pulled out of the mail. When a supplier sends a PDF, Iterate Attachments splits the attached files into separate bundles (one item per file), so the next module, a cloud drive or an accounting app, receives them one at a time.

Replies prepared, not sent. Create a Draft writes an answer into your drafts folder for a human to review, which suits sales teams that want speed without losing control over tone.

What to know before you start: the directory lists no limit specific to this app, so the constraints are those of your Make plan, such as files up to 5 MB and 2 active scenarios on the Free plan. The Make pricing page compares plans. The same mailbox can also be automated with n8n: see the Email n8n integration and the n8n vs Make comparison.

Connect

How do you connect your mailbox to Make?

  1. 01

    Add an Email module

    Open your scenario, click the + and search for Email. Pick any module, for example Watch Emails, then click Create a connection. A connection is your mailbox linked to Make once and reused by every Email module.

  2. 02

    Name the connection

    This step is optional but pays off later. Give the connection the name of the mailbox it opens, such as the support address, so you pick the right one later when a scenario uses several inboxes.

  3. 03

    Authorize and save

    Follow the window Make opens: either approve access on your provider's page or paste the key your provider gives you. Click Save. Make can now read the mailbox and list what it finds in the module fields.

First scenario

Your first scenario: alert a teammate about important mail

GoalWhen a new email matching your criteria lands in the mailbox, Make alerts a team member and marks the message as read.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for Email and choose Watch Emails as the first module.

  2. 02

    Set up Watch Emails

    Pick your connection, then fill in the criteria that define which messages count, for instance mail from a key client. Make lists the options it can read from your mailbox once connected.

  3. 03

    Alert the right person

    Click the + on the right of Watch Emails and add Send an Email to a Team Member. Choose the colleague, then map details of the incoming email from the previous module into the alert.

  4. 04

    Mark the original as read

    Add Mark an Email as Read after the alert and map the email from Watch Emails. The shared inbox then shows at a glance which messages someone already knows about.

  5. 05

    Test, schedule and switch on

    Click Run once and check the bundles each module received. If all looks right, set the schedule on Watch Emails (every 15 minutes by default) and switch the scenario on.

Triggers

What starts an Email scenario

1 module starts a scenario when something happens in Email. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Email as soon as it happens.

Email1Watch Emails

Watch Emails

Scheduled trigger

In Make“Triggers when a new email is received for processing according to specified criteria.”

Watch Emails gives your scenario a starting point: every new message that matches the criteria you set becomes a bundle, one item that the next modules can read, reply to or file away. It is the only trigger of the Email app, so most scenarios begin here.

How it fires
scheduled. Make checks the mailbox on the scenario's schedule, every 15 minutes by default, 15 minutes at the shortest on the Free plan and down to 1 minute on paid plans.
When to use it
a shared address such as sales or support where each incoming request should reach a person or a tool.
Watch out
narrow the criteria before switching on, since every matching email costs operations in the modules that follow.
Modules

What the Email modules can do

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

Email1

Copy an Email

Action

In Make“Copies an email or a draft into a selected folder.”

Copy an Email leaves the message where it is and puts a duplicate, or a copy of a draft, into another folder of your choice. You keep the original in place for whoever reads the inbox.

When to use it
an archive folder for contracts or orders that should exist even if someone later tidies the main inbox.
Watch out
to take a message out of the inbox, pick Move an Email instead, otherwise it appears twice.
Email2

Create a Draft

Action

In Make“Creates and adds a new draft to a selected folder.”

Create a Draft saves a ready-to-edit message in the folder you select without sending anything. Someone opens it, adjusts a word or two and sends it from their usual mail client.

When to use it
quote requests where the scenario prepares a reply from the incoming data but a salesperson still checks prices and tone.
Watch out
drafts pile up quietly, so tell the team where to find them.
Email3

Delete an Email

Action

In Make“Removes an email or a draft from a selected folder.”

Delete an Email clears a message or a draft out of a chosen folder, which keeps automated notifications and newsletters from crowding the inbox once they have been processed.

When to use it
after a system alert has been logged elsewhere and the mail itself has no further use.
Watch out
test it with Run once on a test message before pointing it at real mail, and prefer Move an Email when in doubt.
Email4

Get Emails

Action

In Make“Returns emails that match the specified criteria.”

Get Emails fetches the messages that meet the criteria you give it, in the middle of a scenario rather than at its start. Each message comes out as its own bundle for the next modules.

When to use it
a scenario started by another app, say a form, that needs to look up earlier mail from the same customer.
Watch out
it can return several messages, and each one runs through the modules that follow.
Email5

Mark an Email as Read

Action

In Make“Marks an email or a draft in a selected folder as read by setting the "Read" flag.”

Mark an Email as Read sets the read flag on a message or a draft in a selected folder, so your mail client stops showing it as new once the scenario has dealt with it.

When to use it
at the end of a flow that already forwarded or logged the message, so the team does not open it again for nothing.
Watch out
the message stays where it is; add Move an Email if you also want it out of sight.
Email6

Mark an Email as Unread

Action

In Make“Marks an email or a draft in a selected folder as unread by setting the "Unread" flag.”

Mark an Email as Unread puts the unread flag back on a message or a draft, so it shows up in bold again and catches the eye of whoever checks the folder.

When to use it
when a scenario spots something that needs a human decision, like a complaint, and wants it to stand out after an automatic first pass.
Watch out
place it after any module that marks mail as read, or the two cancel out.
Email7

Move an Email

Action

In Make“Moves a chosen email or a draft to a selected folder.”

Move an Email takes a message or a draft out of its current folder and puts it in the one you pick. Your inbox shrinks to what still needs attention.

When to use it
sorting incoming mail by type, with invoices going to an accounting folder and job applications to a hiring folder.
Watch out
map the email from the trigger or from Get Emails, since the module needs to know which message to move.
Email8

Send an Email

Action

In Make“Sends a new email.”

Send an Email writes and sends a new message from the connected mailbox, built from data that earlier modules of the scenario picked up.

When to use it
an automatic acknowledgment to a customer whose request just arrived, or a confirmation after a record was created in another app.
Watch out
test with your own address first, because once the scenario is on, every bundle sends a real email.
Email9

Send an Email to a Team Member

Action

In Make“Sends an email to a specific member of your team.”

Send an Email to a Team Member notifies a specific colleague you pick from your team. It is the quick way to turn an incoming message into an internal alert.

When to use it
a key account writes in and the account manager should know right away, while the rest of the team keeps working.
Watch out
for customers or partners outside your team, use Send an Email.
Email10

Iterate Attachments

Iterator

In Make“Iterates received attachments one by one.”

Iterate Attachments takes the files attached to a message and hands them over one by one, each as its own bundle. That way a storage or document module can process every file separately.

When to use it
a supplier sends three PDFs in one email and each should land as a separate file in your drive.
Watch out
every module after it runs once per attachment, and each run counts as an operation on your plan.
Need help

Need help automating Email with Make?

A person reads every message.

FAQ

Questions about the Email Make integration

01Is the Email Make integration free?
Yes. Email is a standard app, available from the Free plan of Make. The Free plan has limits that matter for mail automation: 2 active scenarios, 15 minutes minimum 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, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in operations, one per module run on one bundle.
02What do you need to connect Email to Make?
A mailbox you can sign in to and a Make account. The documentation lists no other prerequisite. In the editor, add any Email module, click Create a connection, optionally name it, then either approve access on your provider's page or paste the key it gives you, and click Save. The connection is stored once and every Email module in every scenario can reuse it, so you only go through these steps for each mailbox you add.
03Does the Email Make trigger react the moment a message arrives?
No. Watch Emails is a scheduled trigger: Make checks the mailbox on the scenario's schedule and picks up whatever new mail matches your criteria. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. For mail this is usually enough, but if a request truly cannot wait, choose a paid plan and a short interval.
04What if the Email Make module you need is missing?
It depends on what you are after. The Email app has 11 modules and no Make an API Call module, so you cannot send a custom request to the mail server from it. Often another module covers the need: Get Emails to look up earlier mail, Iterate Attachments to handle files. If your provider has its own app in Make, that app may offer more. For a case that none of these covers, the team can look at your setup.
05Should you use Make or n8n to automate Email?
It depends mostly on where your other automations live. Both tools can work with a mailbox, and this site has a page for each. On the Make side you get 11 modules, a visual editor with a Run once test, and a Free plan with 2 active scenarios. If your team already builds scenarios in Make, keeping mail there saves learning a second tool; the n8n vs Make comparison covers the broader choice.
Same platform

Other docs you might need on this stack.

Browse all integrations