Resources · Make integration

Microsoft 365 Email (Outlook) Make integrationAutomate Microsoft 365 Email (Outlook) with Make.

What if your inbox sorted itself? The Microsoft 365 Email (Outlook) Make integration gives you 15 modules: one trigger, 12 actions and 2 searches. This guide connects your account and walks you through a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft 365 Email (Outlook) Make integration do?

It links your Outlook mailbox to Make so emails can start an automation or be handled by one. You build a scenario, the automation itself, from modules: small blocks that each watch, create, send, move or search emails, with no code to write.

A cleaner inbox. Watch Emails spots each new message, and Move an Email to a Folder files it where it belongs, so the support request lands in the support folder instead of piling up in the inbox.

Attachments that go where they are needed. List Attachments tells you what files an email carries, and Download an Attachment (legacy) hands them to the next module, for instance a storage app or a spreadsheet you already use in Make.

Replies prepared, a human decides. Create a Draft Email writes an answer in your Drafts folder, Update an Email adjusts it, and Send a Draft Email ships it once someone has checked it. For a direct message, Send an Email does all three at once.

The official documentation was unavailable when this page was written, so no limit is quoted here. If a scenario stops, the Make troubleshooting guide is a good place to start. Want a structured path? Try the Make training. Still weighing tools? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect Microsoft 365 Email (Outlook) to Make?

  1. 01

    Add an Outlook module

    In your scenario, add any Microsoft 365 Email (Outlook) module and click Create a connection. A connection is your mailbox linked to Make once, then reused by every Outlook module you add later.

  2. 02

    Name the connection

    This step is optional but handy: give the connection a clear name, such as the address of the mailbox. When a team shares several mailboxes, the right one is easy to pick from the list.

  3. 03

    Authorize and save

    Sign in on the Microsoft page that opens and allow Make to access the mailbox. Back in Make, click Save. The connection now appears in the module, ready to use.

First scenario

Your first scenario: a draft reply for every new email

GoalWhen a new email reaches your Outlook mailbox, Make writes a draft reply that waits for you in Drafts.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add its first module. Search for Microsoft 365 Email (Outlook) and pick Watch Emails.

  2. 02

    Connect and set up the trigger

    Click Create a connection and authorize your mailbox. Once connected, Make can list the folders it reads, so choose the one you want to watch and fill in the remaining fields.

  3. 03

    Add the draft

    Click the + to the right of Watch Emails and add Create a Draft Email. Map data from the email received into the draft, so the answer goes back to the right person.

  4. 04

    Test with Run once

    Click Run once, then send yourself a test email. Open each module to read the bundles it received: a bundle is one item passed along, here one email.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default, then switch the scenario on. Each new email now leaves a draft in Outlook for you to review.

Triggers

What starts the scenario

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

Microsoft 365 Email (Outlook)1Watch Emails

Watch Emails

Scheduled trigger

In MakeTriggers when a new email is sent or received.

Watch Emails picks up each new message in the mailbox and starts your scenario with it, one bundle per email. It reacts to messages you receive and to the ones you send.

How it fires
it is a scheduled trigger, so Make checks the mailbox on the scenario's schedule, every 15 minutes by default, with no push from Outlook.
When to use it
as the first module of any flow that should react to incoming mail, such as sorting requests or saving invoices.
Watch out
because sent emails count too, a scenario that sends mail from the same mailbox can wake itself up again.
Modules

What the Outlook modules can do

Microsoft 365 Email (Outlook) gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft 365 Email (Outlook)1

Add an Attachment

Action

In MakeAdds a large attachment to an email.

Add an Attachment puts a large file onto an email that already exists, typically a draft you are still preparing, so the message leaves with its document.

When to use it
after Create a Draft Email, when a quote or report produced earlier in the scenario must travel with the message.
Watch out
it adds to an existing email; to write a brand new message with its file, pair it with a draft first.
Microsoft 365 Email (Outlook)2

Create a Draft Email

Action

In MakeCreates a new draft email.

Create a Draft Email writes a message and leaves it in your Drafts folder instead of sending it. Nothing reaches the recipient until someone decides.

When to use it
for replies that deserve a human glance, like an answer to a new customer or a message with prices in it.
Watch out
drafts pile up quietly, so plan who reviews them and when they get sent with Send a Draft Email.
Microsoft 365 Email (Outlook)3

Delete an Email

Action

In MakeDeletes an email.

Delete an Email removes a message from the mailbox. It keeps the inbox free of noise you never read, such as automatic alerts already handled elsewhere.

When to use it
at the end of a flow, once the useful content of an email has been copied to another tool.
Watch out
test it on a dummy email first with Run once; pointed at the wrong message, it removes mail you wanted to keep.
Microsoft 365 Email (Outlook)4

Download an Attachment (legacy)

Action

In MakeDownloads an attachment from an email.

Download an Attachment (legacy) fetches a file attached to an email so the next module can store it, read it or send it on.

When to use it
when invoices or signed forms arrive by email and must end up in a storage app or be parsed by another module.
Watch out
Make labels this module legacy. Keep that tag in mind when you build a new scenario around it, and check the module list for a newer option.
Microsoft 365 Email (Outlook)5

Forward an Email

Action

In MakeForwards an email.

Forward an Email passes a message you received on to someone else, with its original content, the same way you would from Outlook by hand.

When to use it
to route a request to the colleague in charge, for example every email from a key account going straight to its account manager.
Watch out
the forward is itself a sent email, so a Watch Emails trigger on the same mailbox will see it too.
Microsoft 365 Email (Outlook)6

Get an Email

Action

In MakeGets the metadata of a specified email.

Get an Email reads the metadata of one precise email you point it to, so later modules can work with its details without searching the whole mailbox again.

When to use it
when an earlier step gives you the identifier of an email, and you need its information before replying or moving it.
Watch out
it targets a single email; to find messages by criteria, Search Emails is the module you want.
Microsoft 365 Email (Outlook)7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you reach any endpoint of the Microsoft API from your scenario, using the same connection as the other Outlook modules.

When to use it
when none of the listed modules covers what you need, such as an action on the mailbox that has no dedicated module.
Watch out
you write the request yourself, so read the Microsoft API reference first and test the call with Run once before you rely on it.
Microsoft 365 Email (Outlook)8

Move an Email to a Folder

Action

In MakeMoves an email to a selected folder in the mailbox.

Move an Email to a Folder files a message into the folder you pick in the mailbox, which is the core of any automatic sorting.

When to use it
right after Watch Emails, to send supplier invoices to one folder and support requests to another, based on a filter you set between the two.
Watch out
pick the destination from the folder list Make reads once connected, rather than typing a name, and test the move with Run once.
Microsoft 365 Email (Outlook)9

Reply to an Email

Action

In MakeReplies to the sender of an email.

Reply to an Email answers the sender of a message you received, straight from the connected mailbox.

When to use it
for a standard acknowledgment, like confirming that a request was received and logged in your tracking tool.
Watch out
the reply goes out at once, so write a text that works for every sender, and keep a filter so newsletters and alerts get no answer.
Microsoft 365 Email (Outlook)10

Send a Draft Email

Action

In MakeSends a draft email.

Send a Draft Email takes a draft that already sits in the mailbox and sends it as it stands, with its recipients, text and files.

When to use it
in two-step flows where Create a Draft Email prepares the message and a person approves it before the scenario ships it.
Watch out
it sends the draft exactly as stored, so any correction must happen before, with Update an Email.
Microsoft 365 Email (Outlook)11

Send an Email

Action

In MakeCreates and sends a new email immediately.

Send an Email writes a new message and sends it right away, in one module, from the connected mailbox.

When to use it
for plain notifications, like telling the team a form was filled.
Watch out
there is no draft to catch a mistake, so run it once toward your own address before pointing it at real recipients.
Microsoft 365 Email (Outlook)12

Update an Email

Action

In MakeUpdates an existing email.

Update an Email changes an existing message, most usefully a draft that still needs its final wording, a new recipient or a corrected subject.

When to use it
between Create a Draft Email and Send a Draft Email, when data coming later in the scenario must complete the message.
Watch out
pass it the right email identifier from an earlier module, or it edits nothing you expected.
Microsoft 365 Email (Outlook)13

List Attachments

Search

In MakeRetrieves a list of attachment from an email.

List Attachments returns the files carried by one email, each as a separate bundle, so you know what arrived before doing anything with it.

When to use it
when an email may hold several files, for instance a delivery note plus its invoice, and each deserves its own treatment.
Watch out
as a search, it can return zero, one or several items, and the modules after it run once per attachment.
Microsoft 365 Email (Outlook)14

Search Emails

Search

In MakeSearches for emails.

Search Emails finds the messages in the mailbox that match your criteria and hands them over one by one to the rest of the scenario.

When to use it
to handle mail on demand, like pulling every message from one client when a deal closes in your CRM.
Watch out
it may return nothing or many emails; each result counts as an operation for the modules that follow, so narrow the search.
Need help

Need help automating Microsoft 365 Email (Outlook) with Make?

A person reads every message.

FAQ

Common questions

01Is the Microsoft 365 Email (Outlook) Make integration free?
Yes, it is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module and per bundle, so a busy mailbox uses more of your monthly credits.
02What do you need to connect Outlook to Make?
A Microsoft 365 mailbox you can sign into, and a Make account. The documentation lists no other prerequisite. Add any Outlook module, click Create a connection, name it if you like, sign in on the Microsoft page to authorize Make, then click Save. The connection is shared by every Outlook module in your scenarios, so you only go through this once per mailbox. If several accounts are open in the browser, check which one is active before you authorize.
03Does the Outlook trigger react in real time?
No. Watch Emails is a scheduled trigger, marked with a clock badge in the editor: Make checks the mailbox on the scenario's schedule instead of being called by Outlook. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. For most sorting or archiving flows that delay is fine. The integration offers no instant trigger.
04What if the Outlook module you need is missing?
Use Make an API Call. It lets the scenario reach any endpoint of the Microsoft API with the connection you already set up, which covers actions the listed modules do not offer. You write the request yourself, so keep the Microsoft API reference at hand and test with Run once. The official documentation was unavailable when this page was written, so no limit of the app is listed here; if a run fails, read the error shown on the module.
05Make or n8n for Outlook automation?
It depends on the tool your team already uses and on how you like to build. On Make, this app brings 15 modules, one scheduled trigger, 12 actions and 2 searches, usable from the Free plan with a visual editor. The same app often has an n8n node too, so both routes can work. There is no ranking to give here: compare the criteria that matter to you, like the modules you need and the plans, in the dedicated n8n vs Make comparison.