> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/connectors/connect-microsoft-planner-for-auto-updates.md).

# Connect Microsoft Planner for auto-updates

The Microsoft Planner connector lets a Key Result or Initiative update itself from a Planner plan — task completion, tasks by bucket, assignee or label, overdue counts. The setup flow (Update mode › Set up auto update, then a short chat) is the same for every connector and is described in [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md). This article covers only what is specific to Planner.

## Before you connect Planner

* A Rhythms Admin has enabled **Planner** under **Settings › Workspace › Connectors**.
* **Your Microsoft 365 administrator has granted consent** (one-time for the whole organization). Send them this link: [Grant admin consent for Microsoft Planner](https://api.rhythms.ai/connections/planner/admin_consent_init). The same link is shown on the Planner connector in Rhythms. The admin signs in, reviews the permissions (read Planner plans, tasks and user profiles) and clicks **Accept**. Until consent is granted, individual sign-ins fail.
* You have a Microsoft 365 account that can see the plans you want to track.

## How Planner authentication works

You sign in with your Microsoft 365 account (OAuth) from **My connectors › Planner › Connect** or when the setup chat prompts you. Rhythms requests these Microsoft Graph permissions: `Group.Read.All` (find the groups that own plans), `Tasks.ReadWrite` (Microsoft's only Planner task permission; auto-updates only read), `User.ReadBasic.All` (show assignee names) and `offline_access` (stay connected). Each person connects their own account.

## What you can track from Planner

* Task completion percentage for a plan
* Completed, open or overdue task counts
* Tasks filtered by bucket, by assignee or by label
* Tasks by priority, or checklist detail for individual tasks

Give Rhythms the plan name (or paste its URL). It finds the plan, reads its buckets, labels and members, and asks which subset counts. A task counts as complete when Planner marks it 100 percent done.

## Limits

* One plan per connection. To combine plans, track each on its own Key Result and roll them up.
* Planner's partial progress (a task set to 50 percent) is not treated as complete.
* Rhythms never creates, changes or completes tasks.

## Example prompts

* "Track the percentage of tasks completed in the Q3 Marketing Campaign plan."
* "Count open tasks in the Design Phase bucket assigned to Priya."

## Related articles

* [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)
* [Enable Connectors for Your Workspace](/connectivity/manage-connectors-for-your-workspace.md)
* [Connect Azure DevOps for auto-updates](/connectivity/connectors/connect-azure-devops-for-auto-updates.md)
* [Effective Check-ins to Track OKR Progress in Rhythms](/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/connectivity/connectors/connect-microsoft-planner-for-auto-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.