Resources · Make integration

Microsoft 365 Planner Make integrationAutomate Microsoft 365 Planner with Make.

Planner can fill itself when the rest of your tools change. The Microsoft 365 Planner Make integration gives you 17 modules: 2 scheduled triggers, 12 actions and 3 searches. This page is for ops leads who already live in Planner, and it walks you from connection to a first working scenario.

Try the Microsoft 365 Planner integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft 365 Planner Make integration do?

The Microsoft 365 Planner Make integration links your Planner plans, buckets and tasks to Make, a visual tool where you chain apps without code. You build a scenario (the automation itself, a chain of bricks called modules), and Make creates, reads, updates or deletes Planner items when something happens elsewhere.

Tasks that appear on their own. A form, a CRM or a ticket tool sends data, and Create a Task drops a card into the right plan and bucket. Nobody retypes the request and the card lands where the team already looks.

A project board ready from day one. When a new client is signed elsewhere, Create a Plan opens the plan, then Create a Bucket adds the columns your team always uses. Every project starts with the same structure.

Planner news sent to the rest of your stack. Watch Tasks and Watch Plans spot what was just created, so a later module can post it in a chat tool or log it in a sheet.

What Make does not do here: both triggers only react to creation, and none of them is instant. For anything the 17 modules skip, Make an API Call reaches the rest of the Planner API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make review covers the product as a whole. Teams that want help building can turn to the Make agency page.

Connect

How do you connect Microsoft 365 Planner to Make?

  1. 01

    Add a Planner module

    Open a scenario, click the + and search for Microsoft 365 Planner. Pick any module, then click Create a connection. A connection is your Planner account linked to Make once, and every Planner module reuses it afterwards.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label helps when several people share the account. Something like the team or the tenant it belongs to makes the right one easy to pick later from the dropdown.

  3. 03

    Sign in with Microsoft

    Follow the on-screen instructions and sign in with a Microsoft work or school account that has the right permissions. If your admin prefers a custom app, paste the Client ID and Client secret from an Azure app registration instead.

First scenario

Your first scenario with Microsoft 365 Planner

GoalWhen a task is created in one Planner plan, Make copies it into a second plan used by another team.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. The canvas stays empty until you pick an app.

  2. 02

    Pick Watch Tasks

    Search for Microsoft 365 Planner, choose Watch Tasks and select your connection. Once connected, Make lists what it can read in Planner, so you choose rather than type.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and add Create a Task. Point it to the second plan, then map the task data coming from Watch Tasks into its fields.

  4. 04

    Test with Run once

    Create a test task in the source plan, then click Run once. Open the bubbles above each module to read the bundle it received, one bundle per task.

  5. 05

    Schedule and switch on

    Open Scheduling on the first module. A new scenario checks every 15 minutes by default. Keep that or change it, then flip the scenario on.

Triggers

Triggers that start a Planner scenario

2 modules start a scenario when something happens in Microsoft 365 Planner. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Microsoft 365 Planner as soon as it happens.

Microsoft 365 Planner1Watch Plans

Watch Plans

Scheduled trigger

In Make“Triggers when a plan is created.”

Watch Plans hands your scenario every plan that has just been created, one bundle per plan, so the next modules can prepare it or announce it to the team.

How it fires
scheduled. Make checks Planner on the scenario's schedule, every 15 minutes by default, and picks up the plans created since the last check.
When to use it
a new plan is the start of a project, and you want buckets added or a message posted as soon as it exists.
Watch out
it only sees new plans. A renamed or edited plan does not start the scenario.
Microsoft 365 Planner2Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when a planner task is created.”

With Watch Tasks, each new Planner task becomes a bundle your scenario can copy, log or forward to another app, without anyone opening Planner to check.

How it fires
scheduled. Make asks Planner on the scenario's schedule for tasks created since the previous run, so a task shows up at the next check, not the second it is saved.
When to use it
requests land as tasks and another team or tool needs to hear about them.
Watch out
the trigger reacts to creation only. Changes to an existing task need a different approach, such as Get a Task inside a scheduled scenario.
Modules

Every Microsoft 365 Planner module in Make

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

Microsoft 365 Planner1

Create a Bucket

Action

In Make“Creates a new planner bucket.”

Create a Bucket adds a new column to a plan, which is how Planner groups tasks by stage or by topic. Your board gets its structure without a manual click.

When to use it
right after Create a Plan, to lay out the same stages on every new project.
Watch out
the bucket needs a plan to live in, so map the plan from the previous module.
Microsoft 365 Planner2

Create a Plan

Action

In Make“Creates a new plan.”

Need a fresh board for a new client or project? Create a Plan opens it from your scenario, ready to receive buckets and tasks in the following modules.

When to use it
a deal is marked as won in your CRM and delivery needs its own space.
Watch out
run it once per project. Placed after a search that returns several bundles, it will create several plans.
Microsoft 365 Planner3

Create a Task

Action

In Make“Creates a new planner task.”

This is the module most scenarios end on: it turns data from another app into a Planner task in the plan and bucket you pick.

When to use it
a form reply, a support ticket or an email should become work someone owns, visible on the team board.
Watch out
test with Run once on a dummy plan first, since every bundle that reaches it creates a real task.
Microsoft 365 Planner4

Delete a Bucket

Action

In Make“Deletes a planner bucket.”

Delete a Bucket removes a column from a plan, which keeps boards tidy once a phase of the project is over.

When to use it
a template plan carries stages a given project does not need, and the scenario strips them after the plan is built.
Watch out
treat the deletion as final. Check the tasks still sitting in that bucket before the scenario runs.
Microsoft 365 Planner5

Delete a Task

Action

In Make“Deletes a planner task.”

Delete a Task wipes one card from Planner, useful when the source of the task disappears and the card would only confuse people.

When to use it
a request is cancelled in the original tool and its Planner copy should go too.
Watch out
treat the deletion as final. Make sure the module before it hands over only the task you mean to remove.
Microsoft 365 Planner6

Get a Bucket

Action

In Make“Gets a specified planner bucket.”

Get a Bucket reads the details of one bucket you already know, so later modules can reuse its name or its plan.

When to use it
a task arrives with a bucket reference and you want the readable name before posting it somewhere.
Watch out
it returns a single bucket. To scan every column of a plan, List Buckets is the better pick.
Microsoft 365 Planner7

Get a Plan

Action

In Make“Gets a specified plan.”

Get a Plan fetches one specific plan and passes its details down the scenario, handy when a trigger gives you only a reference.

When to use it
Watch Tasks hands you a task, and your message should mention the plan it belongs to by name.
Watch out
the connected account must be able to see that plan, so a board shared with someone else may stay out of reach.
Microsoft 365 Planner8

Get a Task

Action

In Make“Gets a specified planner task.”

Get a Task pulls the current state of a single task, so the scenario works with fresh data instead of what the trigger saw earlier.

When to use it
before updating or reporting on a task, to be sure you read its latest version.
Watch out
one call, one task, one operation (an operation is one module run on one bundle, what Make counts on your plan).
Microsoft 365 Planner9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any part of the Planner API the other modules leave out, while reusing the connection you already set up.

When to use it
you need an operation none of the 17 modules offer, and a developer on the team can read the Microsoft docs.
Watch out
you write the request yourself. It is the least beginner friendly module on this page, so keep it for real gaps.
Microsoft 365 Planner10

Update a Bucket

Action

In Make“Updates an existing planner bucket.”

Update a Bucket changes an existing column, so a board can follow a project as it moves forward without anyone renaming things by hand.

When to use it
a phase gets a new label in your project tool and Planner should mirror it.
Watch out
pick the bucket by its reference, usually from List Buckets or Get a Bucket earlier in the flow.
Microsoft 365 Planner11

Update a Plan

Action

In Make“Updates an existing plan.”

With Update a Plan, the plan itself follows changes made elsewhere, for instance a project renamed in your CRM once the contract is signed.

When to use it
the plan was created by a scenario and some of its details only become known later.
Watch out
it edits one plan at a time. Pair it with List Plans if several plans need the same change.
Microsoft 365 Planner12

Update a Task

Action

In Make“Updates an existing planner task.”

Update a Task edits a card that already exists, so Planner reflects progress logged in another tool and nobody keeps two boards in sync.

When to use it
a ticket is closed in your helpdesk and the matching Planner task should move along with it.
Watch out
you must know which task to touch. Store its reference when you create it, or find it with List Tasks.
Microsoft 365 Planner13

List Buckets

Search

In Make“Retrieves a list of planner buckets.”

List Buckets returns every bucket of a plan as separate bundles (a bundle is one item passed to the next module), ready to loop over.

When to use it
you want to find the bucket called "Done" before moving a task, without hardcoding its reference.
Watch out
each bucket found counts as its own bundle, so the modules after it run once per bucket.
Microsoft 365 Planner14

List Plans

Search

In Make“Retrieve a list of authenticated user's plans.”

List Plans returns the plans the connected user can see, which gives your scenario a starting point for audits or bulk changes.

When to use it
you need to find a plan by name, or apply the same update to several of them.
Watch out
it reads the plans of the authenticated account only. A plan that account cannot open will not show up.
Microsoft 365 Planner15

List Tasks

Search

In Make“Retrieves a list of planner tasks”

List Tasks gives back the tasks of Planner as one bundle each, the raw material for a report, an export to a sheet or a cleanup pass.

When to use it
a manager wants open tasks copied into a spreadsheet when a project review is prepared.
Watch out
the search can return zero, one or many tasks, and each of them costs operations in the modules that follow.
Need help

Need help automating Microsoft 365 Planner with Make?

A person reads every message.

FAQ

Microsoft 365 Planner and Make: common questions

01Is the Microsoft 365 Planner Make integration free?
Yes, on the Make side. Microsoft 365 Planner is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations per month, one per module run. You still need your own Microsoft subscription that includes Planner.
02What do you need to connect Microsoft 365 Planner to Make?
You need an active Microsoft work or school account with the right permissions, plus an access token that Make gets for you when you sign in. In the editor, add any Planner module, click Create a connection, optionally name it, then follow the Microsoft sign-in. For a custom setup, an admin registers an app in the Azure portal, copies the Client ID and Client secret, and pastes both into the connection. A personal Microsoft account is not enough.
03Does the Microsoft 365 Planner trigger fire in real time?
No. Watch Plans and Watch Tasks are both scheduled triggers, shown with a clock badge in the editor. Make checks Planner on the schedule you set on the first module, every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest gap between two runs, while paid plans go down to 1 minute. If you need a faster reaction, lower the interval on a paid plan; Planner has no instant trigger in Make.
04What if a Microsoft 365 Planner module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Planner API with the connection you already have, so you are not limited to the 17 listed modules. It asks you to write the request yourself from the Microsoft documentation, which suits someone comfortable reading an API reference. Keep in mind that the Make docs for this app are AI generated from Microsoft material and can contain mistakes, so double check important details with Microsoft.
05Should you use Make or n8n for Microsoft 365 Planner?
It depends on the tool your team already uses. Planner often has an equivalent node in n8n, so the app itself rarely decides. On Make, you get 17 ready modules, including 2 triggers and a generic API module, a visual editor and a Free plan to test with. Compare how each tool handles your other apps, how your team likes to build, and which one it will maintain, rather than the Planner connector alone.
Same platform

Other docs you might need on this stack.

Browse all integrations