Planner Task from Flagged Emails
When you flag an email in Outlook, automatically creates a corresponding task in Microsoft Planner with the email subject as the title and email body as the description. Links back to the original email.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
When an email is flagged in Outlook, this flow automatically creates a corresponding task in Microsoft Planner. The task title is set from the email subject, the description is populated from the email body preview, and a web link back to the original message is attached so you can jump from Planner straight back to the email. An optional Teams step posts a confirmation message in a chat with yourself so you have a visible audit trail of created tasks.
The pattern is intentionally lightweight: it turns the familiar "flag for follow-up" gesture in Outlook into a real, trackable task without having to switch apps or copy-paste subject lines and links.
Use Case
Many people use the Outlook flag as a lightweight "come back to this later" marker, but flags get lost in the inbox and don't surface in any task list. This flow promotes a flagged email into a first-class Planner task in a designated bucket, with a sensible default due date and a link back to the source email. It's a good starter automation for anyone who already lives in Outlook and Planner and wants their follow-ups to stop hiding in the inbox.
The flow is ideal for teams that:
- Individuals who triage email by flagging items for follow-up
- Teams that track action items in a shared Planner plan
- Power Automate beginners learning the Outlook + Planner connector pair
Flow Architecture
When an email is flagged
Office 365 Outlook — When an email is flagged (V3)Fires whenever a message in the Inbox folder is flagged for follow-up.
Create Planner task
Planner — Create a taskCreates a task in the configured plan and bucket. Title is set from the email subject, due date defaults to addDays(utcNow(), 3), and the task is assigned to the configured user.
Update task details
Planner — Update task detailsPopulates the task description with the email body preview and adds a web-link reference back to the original Outlook message.
Post confirmation message (optional)
Microsoft Teams — Post message in a chat or channelPosts a confirmation message in a chat with yourself so you have a visible record that the task was created. Optional — can be removed without affecting the rest of the flow.
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Office 365 Outlook | shared_office365 | OnFlaggedEmailV3 (trigger) |
| Microsoft Planner | shared_planner | CreateTaskV3 UpdateTaskDetailsV2 |
| Microsoft Teams | shared_teams | PostMessageToChannelV3 (optional) |
Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.
Customization Guide
Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.
- Change the default due date offset
- Replace addDays(utcNow(), 3) in the Create a task action with a different offset (1, 5, 7 days) to match your team's typical follow-up SLA.
- Promote plan, bucket, and assignee to env vars
- Replace the hard-coded Plan Id, Bucket Id, and Assigned to user with environment variables so the same flow can be redeployed against different plans/users without editing the action.
- Map Outlook importance to Planner priority
- Add a switch on triggerOutputs()?['body/importance'] (Low/Normal/High) and set the Planner priority field accordingly when creating the task.
- Drop the Teams confirmation step
- The Post message action is purely a confirmation. Remove it if you don't want the extra notifications, or redirect it to a shared channel for team-wide visibility.
Key Expressions
The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.
EXPR.01Task title from email subject
Pulls the subject line of the flagged email and uses it as the Planner task title.
EXPR.02Task description from email body preview
Uses Outlook's body preview (first ~255 characters of the email) for the task description, keeping the task readable.
EXPR.03Default due date 3 days out
Sets the task due date to three days from when the flow runs. Adjust the offset to change the default SLA.
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.