Microsoft 365 Planner is part of the Microsoft 365 suite, offering lightweight task and bucket-based planning for teams. This integration supports creating plans, buckets, tasks, fetching them, deleting them, and custom API calls.
Microsoft 365 Planner currently provides 3 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New Plan Created
Triggers when a new Plan is created in Microsoft 365 Planner.
New Task Created
Triggers when a new Task is created in Microsoft 365 Planner.
New Task Assigned to User
Triggers when a Task is assigned to the authenticated user in Microsoft 365 Planner.
Create Plan
Create a new planner plan
Create Bucket
Create a bucket (category) under a plan.
Create Task
Create a new planner task with title, assignments, due date, etc.
Delete Bucket
Delete an existing bucket.
Delete Task
Remove a specific task by ID.
Update Plan
modify metadata of a plan (e.g. title changes).
Update Bucket
Modify bucket’s name or properties.
Update Task
Modify existing task fields: title, due date, assignments, descriptions.
Find a Plan
Finds a plan by field.
Get a Bucket
Retrieve details about a specific bucket.
Find Task
Find task by fields.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Microsoft 365 Planner event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Plan Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Microsoft 365 Planner action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Plan
Combine Microsoft 365 Planner with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New Plan Created
Finishes with
Create Plan, then preserve the outcome in Coherence
The exact authentication fields depend on Microsoft 365 Planner. The workflow structure stays straightforward:
Authorize the Microsoft 365 Planner account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Microsoft 365 Planner or provide a complementary trigger or action.
Microsoft 365 Planner currently provides 3 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Microsoft 365 Planner currently lists 3 triggers and 12 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Microsoft 365 Planner triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
