Resources · Make integration

Microsoft 365 Calendar Make integrationAutomate Microsoft 365 Calendar with Make.

Can Make keep your Microsoft calendar in step with the rest of your tools? The Microsoft 365 Calendar Make integration gives you 12 modules: one trigger, nine actions and two searches. This guide shows how to connect your account and build a first working scenario.

Try the Microsoft 365 Calendar integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft 365 Calendar Make integration do?

It links your Microsoft 365 Calendar account to Make so a scenario, the automation you build in Make, can read, create, change and remove calendars and events for you. Each step of that scenario is a module, and this app brings 12 of them, from a trigger that notices new or edited events to a free-form API call.

Bookings that land on the calendar by themselves. When a request arrives in another tool, such as a form or a CRM, Create an Event puts it on the right calendar with the details you map. Nobody has to retype a date.

Changes that spread to other tools. Watch Events notices when an event is created or edited, so a scenario can pass that news to a spreadsheet, a chat channel or a project board. Pair it with Get an Event when the next step needs the full details.

Tidy calendars for a team or a project. Create a Calendar opens a dedicated calendar when a new project starts, and Delete a Calendar removes it once the work is closed. List Calendars shows what already exists before you add anything.

A few limits to keep in mind. The only trigger is scheduled: Make checks for news on the scenario's clock rather than hearing from Microsoft right away. And the documentation lists no specific quota for this app, so if something odd happens, the Make troubleshooting guide is the place to start.

The same app often has an n8n node too. If you are weighing both tools, read n8n vs Make; to learn Make itself step by step, see the Make training.

Connect

How do you connect Microsoft 365 Calendar to Make?

  1. 01

    Add a module and start the connection

    In your scenario, add any Microsoft 365 Calendar module, then click Create a connection. A connection is your account linked to Make once; every module of this app reuses it afterward.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when a colleague's account sits next to yours. Then approve access on the Microsoft page that opens, or paste the key if Make asks for one instead.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make can now read your account and offer your calendars in the fields, so you pick from a list instead of typing names by hand.

First scenario

Your first scenario: turn incoming requests into events

GoalWhen a request arrives in another app, Make adds a matching event to your Microsoft 365 Calendar.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Start with the app that receives requests

    Search for the tool where requests come in, a form app or your CRM for example, and pick its trigger. Connect that account the same way you would connect Microsoft.

  3. 03

    Add Create an Event

    Click the + on the right of the first module, search for Microsoft 365 Calendar and choose Create an Event. Select your connection, or create it now.

  4. 04

    Map the request into the event

    Pick the calendar from the list Make shows, then map the data of the previous module: the date, the subject and the person behind the request go where they belong.

  5. 05

    Test with Run once

    Send a test request in the first app, then click Run once. Open each module's bubble to read the bundles it received, then check that the event shows up in your calendar.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. From now on, each new request becomes an event without anyone touching the calendar.

Triggers

What can start a Microsoft 365 Calendar scenario?

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

Microsoft 365 Calendar1Watch Events

Watch Events

Scheduled trigger

In Make“Triggers when an event is created or updated.”

Watch Events gives your scenario a fresh bundle, one item passed to the next module, every time an event is created or edited in your calendar. That lets the rest of the scenario react to calendar news without anyone copying it over.

How it fires
this is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default, rather than being called by Microsoft.
When to use it
a new client meeting should appear in your CRM or in a team channel as soon as the next check runs.
Watch out
an edit also counts, so a scenario that updates the same events it watches will keep waking itself up.
Modules

What else can Make do with Microsoft 365 Calendar?

Microsoft 365 Calendar gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft 365 Calendar1

Create a Calendar

Action

In Make“Creates a new calendar.”

With Create a Calendar you get a brand new, empty calendar in the account, ready to hold a project's or a team's events apart from your own schedule.

When to use it
a deal is signed or a project opens in another tool, and its milestones deserve their own calendar rather than crowding the main one.
Watch out
run it once per project, not on every bundle, or you will end up with duplicate calendars.
Microsoft 365 Calendar2

Create an Event

Action

In Make“Creates a new event.”

This is the module that writes to your agenda: it adds a new event to the calendar you choose, filled with data mapped from earlier modules.

When to use it
a booking form is submitted, a demo is requested or a task gets a due date, and the slot should appear in the calendar without anyone retyping it.
Watch out
if Watch Events on the same calendar starts another scenario, the new event will trigger it as well.
Microsoft 365 Calendar3

Delete a Calendar

Action

In Make“Deletes a calendar.”

Delete a Calendar removes a whole calendar from the account, which keeps the list short once a project or a temporary team is over.

When to use it
the project is marked closed in your project tool and its dedicated calendar has no reason to stay.
Watch out
treat a delete as final: test it with Run once on a throwaway calendar and double-check which calendar you mapped.
Microsoft 365 Calendar4

Delete an Event

Action

In Make“Deletes an event.”

Use it to wipe a single event off the calendar, for example when the meeting behind it no longer exists anywhere else.

When to use it
a customer cancels a booking in your form or CRM, and the matching slot should free up for someone else.
Watch out
treat the delete as final. Check that the previous module points to the right event, usually one found with Search Events, and test on a dummy event first.
Microsoft 365 Calendar5

Get a Calendar

Action

In Make“Gets the metadata of a specified calendar.”

Get a Calendar reads the details of one calendar you name, so the following modules can reuse what it returns without you typing anything in.

When to use it
a scenario receives a calendar reference from an earlier step and needs its information before writing a report or a message.
Watch out
it reads one calendar only; to see them all at once, List Calendars is the better fit.
Microsoft 365 Calendar6

Get an Event

Action

In Make“Gets the metadata of a specified event.”

Once you know which event matters, Get an Event fetches its details so the next module has the complete picture instead of a partial one.

When to use it
right after Watch Events, when a later step, such as a summary sent to a chat channel, needs more than the trigger passed along.
Watch out
it needs to be told which event to read, so map that reference from a previous module rather than typing it by hand.
Microsoft 365 Calendar7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Here you reach any endpoint of the Microsoft API from your scenario, reusing the same connection, when the eleven other modules do not cover what you need.

When to use it
you need an operation that has no dedicated module on this page, and you are comfortable reading the API documentation to build the request.
Watch out
it is the most technical module of the app, so start with a read-only request and test it with Run once.
Microsoft 365 Calendar8

Update a Calendar

Action

In Make“Updates an existing calendar.”

Update a Calendar changes an existing calendar in place, so its settings follow what happens elsewhere without anyone editing them by hand.

When to use it
a project gets renamed in your project tool and its dedicated calendar should carry the new name too.
Watch out
point it at the right calendar, ideally mapped from List Calendars or Get a Calendar, rather than a guessed name.
Microsoft 365 Calendar9

Update an Event

Action

In Make“Updates an existing event.”

When a plan shifts, Update an Event edits an event that already exists instead of creating a second copy, so attendees keep one clean entry.

When to use it
a client moves an appointment in your booking tool, and the calendar should show the new slot on the same event.
Watch out
an update wakes up any scenario running Watch Events on that calendar, so avoid updating events inside the scenario that watches them.
Microsoft 365 Calendar10

List Calendars

Search

In Make“Retrieves a list of the authenticated user's all calendars.”

List Calendars returns every calendar of the connected account, one bundle per calendar, which is handy for knowing what exists before acting.

When to use it
you want to check whether a project calendar is already there before running Create a Calendar, or to process each calendar in turn.
Watch out
each calendar becomes its own bundle, so the modules after it run once per calendar and use operations each time.
Microsoft 365 Calendar11

Search Events

Search

In Make“Searches for the events.”

Search Events looks through your calendar and hands back the matching events, so a scenario can find the one to update or delete.

When to use it
a cancellation arrives by email or form, and you need to locate the related meeting before Delete an Event removes it.
Watch out
a search can return zero, one or several events; plan for the empty case and for more than one match before acting.
Need help

Need help automating Microsoft 365 Calendar with Make?

A person reads every message.

FAQ

Microsoft 365 Calendar and Make: common questions

01Is the Microsoft 365 Calendar Make integration free?
Yes, it is a standard app, so it works from the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run counts as an operation, the unit Make uses to measure usage on your plan. Paid plans such as Core, Pro, Teams and Enterprise lift those limits, with unlimited active scenarios and a 1 minute minimum interval.
02What do you need to connect Microsoft 365 Calendar to Make?
The documentation lists no special prerequisite, so a Microsoft 365 Calendar account you can sign in to is the starting point. In any module of the app, click Create a connection, name it if you wish, approve access on the Microsoft page that opens, then click Save. That connection is then shared by all 12 modules, so you only do it once per account. If you work with several accounts, give each connection a clear name to avoid writing to the wrong calendar.
03Does Watch Events react in real time?
No. Watch Events is a scheduled trigger: Make checks your calendar on the scenario's schedule instead of being notified by Microsoft the moment something changes. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap allowed, while paid plans go down to 1 minute. When the check runs, every event created or edited since the previous one comes in as its own bundle and moves through the scenario.
04What if a Microsoft 365 Calendar module is missing in Make?
It depends on what is missing, but there is a way out. The app includes Make an API Call, which lets a scenario reach any endpoint of the Microsoft API with the connection you already set up. It asks you to read the API documentation to build the request, so it suits someone at ease with that. The official documentation gives no specific limit for this app, so if a scenario stalls, look at the error on the module that failed before changing your setup.
05Should you use Make or n8n for Microsoft 365 Calendar?
It depends on your criteria rather than on the app. On the Make side, you get 12 ready-made modules, a scheduled Watch Events trigger and Make an API Call for anything they leave out, all usable from the Free plan. The same app often has an n8n node as well, so check that it covers the actions you need. This page does not rank the two tools; the n8n vs Make comparison linked above lays out the differences in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations