Why does so much manual work start in Outlook?
In many SMEs the mailbox is where work comes in. A request via info@, a purchase invoice via invoices@, an order confirmation from a supplier, a customer who wants to move an appointment. Someone reads the email, retypes the details into another system and then files the email in a folder.
That work is not difficult, but it never stops. And it depends on one colleague: when they are on holiday, info@ piles up.
Make.com is well suited to taking this over, because Make has ready-made apps for the Microsoft 365 tools you use every day. This article is about Outlook: your email and your calendar. How to connect two systems with Make in general is covered in building a Make.com integration.
What can Make.com do with your Outlook email and calendar?
For email you use the Microsoft 365 Email (Outlook) app in Make. According to Make's documentation (checked on 13 November 2026), it lets you, among other things:
- watch for new messages in your own mailbox, or in a folder of a shared mailbox;
- search, retrieve, reply to, forward, move and delete messages;
- create and send a new message, or prepare a draft first;
- list, download and add attachments.
For your calendar there is the Microsoft 365 Calendar app, which lets you watch, search, create and update events. And for files there are separate apps for OneDrive and SharePoint. If a module lacks the exact function you need, each app also has a module to make your own API call to Microsoft.
Good to know: a trigger such as Watch Messages checks for new email at the interval you set for the scenario. That means the scenario also runs when nothing has arrived. How to work that out in credits is covered in what Make.com automation costs.
Which 5 Outlook workflows deliver the most?
We see these five come back often. They are deliberately small: one mailbox or calendar, a few steps and a clear outcome.
1. Requests from info@ into your CRM, with a task attached
Trigger: a new email in the Inbox of the shared mailbox info@.
Steps: filter on emails that are requests (for example by the subject your web form uses), check in your CRM whether the sender is already known, otherwise create a contact, set up a follow-up task and move the email to a "Processed" folder.
Watch out: moving the email is not just tidy. It also stops the same email from being picked up twice later.
2. Preparing a draft reply for standard questions
Trigger: a new email in a shared mailbox for customer questions.
Steps: recognise the type of question (delivery time, opening hours, a copy of an invoice), fetch the data needed and put a draft reply in the mailbox. A colleague reads it and clicks send.
Watch out: Make can also send the reply straight away, but for customer email we recommend a draft. If you want to use AI to recognise the question or prepare the text, read agentic AI for SMEs first.
3. Appointments from a form or CRM into the calendar
Trigger: a submitted appointment form or a new appointment in your CRM.
Steps: create the event in the right Outlook calendar, with the customer details in the description, and send the customer a confirmation from the general address.
Watch out: decide which system leads. If an appointment is moved in Outlook, your CRM does not know that by itself.
4. Recording order confirmations from suppliers
Trigger: a new email from a fixed set of suppliers with a recognisable subject.
Steps: download the PDF attachment, store it with the purchase order (in SharePoint or your ERP) and set the order status to "confirmed".
Watch out: every supplier emails differently. Start with the two or three suppliers with the most volume.
5. Flagging email that is left waiting
Trigger: scheduled, every working day at nine.
Steps: search the shared mailbox for email that has been sitting unanswered in the Inbox for more than a working day and send one summary to the team or the person responsible.
Watch out: this only works if processed email really leaves the Inbox. Agree on that with the team.
Automatically saving attachments such as purchase invoices to SharePoint or OneDrive is another strong Outlook workflow. It is worked out in Make.com workflows for SMEs.
How do you connect Outlook to Make.com?
The connection itself is quick: you add an Outlook module, choose "Create a connection" and sign in with a Microsoft account. Three choices do need some thought.
- Which account do you sign in with? The account you connect with determines what Make can see and do. Preferably use a dedicated account for integrations, not a colleague's personal account. If that colleague leaves or changes their password, your scenario keeps working.
- Shared mailbox or your own? For a shared mailbox such as info@ you use Make's module for messages in a shared folder. The account behind the connection must actually have access to that mailbox. Set that up in Microsoft 365 first, or you will run into a permissions error while testing.
- Does an administrator need to be involved? When you sign in, Make asks for permissions such as reading and sending email. Depending on how your Microsoft 365 environment is configured, an administrator may need to approve that first. So involve whoever manages Microsoft for you upfront.
If you work with strict IT requirements, you can also use your own app registration from your Microsoft environment under Make's advanced settings. That gives your administrator more visibility into exactly which permissions have been granted.
An example: info@ at a consultancy
A fictional but recognisable example. A consultancy with fifteen employees receives requests through a form on its website, which sends an email to info@. One colleague reads that mailbox, adds new customers to the CRM, creates a task for the right consultant and files the email. On busy days things are left waiting, and when that colleague is ill it stops altogether.
The scenario in Make:
- Trigger: new messages in the Inbox of the shared mailbox info@, every fifteen minutes.
- Filter: only emails with the fixed subject of the web form. Other email stays put for the colleague.
- Extract the data: the form always sends the same fields, so name, email address, phone number and question can be reliably taken from the text.
- CRM: search by email address whether the contact exists, otherwise create it, and set up a follow-up task.
- Wrap up: move the email to "Processed" and send the requester a short acknowledgement.
- Error handling: if a step fails, the email stays in the Inbox and the colleague gets an alert. Nothing gets lost.
The colleague keeps the emails that really need attention and is no longer the only one who knows how requests are handled. How to set up that error handling properly in Make is covered in Make.com error handling.
Where does automating Outlook usually go wrong?
- Processing twice. If a scenario runs again, it may pick up the same email a second time. Move processed email to a folder of its own, or keep track in a data store of which messages have been handled.
- Attachments that are not attachments. Logos and signatures arrive as attachments too. Filter on file type and size.
- Free text as a source. Data from an email a person typed is unreliable. Where possible, work with emails sent by a system, such as a web form, or have a person check the result.
- An expired or revoked connection. A changed password or a disabled account and the scenario fails. Make sure someone gets an alert and knows how to renew the connection.
- Sending automatically without a check. A mistake in a scenario that sends email itself is seen by your customers before you see it. Start with drafts and only switch to automatic sending once it has run without errors for a while.
- Personal data. Emails with names, addresses and sometimes sensitive questions pass through the scenario. Only include the fields you need and record which data goes where.
Make.com or Power Automate for Outlook?
A fair question: doesn't Microsoft have Power Automate for this? It does, and for flows that stay entirely within Microsoft 365 it can be a perfectly good choice. Think of saving an Outlook attachment to SharePoint or an approval via Teams.
Make becomes more interesting as soon as your mailbox needs to talk to systems outside Microsoft: your CRM, your accounting package, a webshop or a planning tool. Then you want all those integrations in one place, with the same error handling and the same owner. If you already run scenarios in Make, it makes sense to add Outlook there rather than manage a second platform.
Two questions help you choose:
- Where are the other systems? Almost everything in Microsoft 365, then Power Automate is a logical candidate. Many systems outside it, then Make often has the better ready-made apps.
- Who will maintain it? Choose the platform the person who maintains it already knows. A scenario nobody dares to touch is a risk after a year.
Still weighing Make against another platform? Also read Make vs n8n. And if the same data is being fetched in more and more scenarios, a central data foundation is often the next step.
Need help automating Outlook with Make.com?
Want to know which mailbox costs you the most time, or already running a scenario that sometimes misses email? We are happy to look at your processes and build Make scenarios with error handling, a fixed owner and a short description of what happens. See what we do in workflow automation, where AI does and does not fit in agentic AI, or read how we work.
