How to create a flow that creates tasks in Planner in Power Automate
This tutorial shows how to create a flow in Power Automate that automatically generates tasks in Planner when an email arrives with a specific tag or when a form is submitted. It is useful to turn requests into actions, ensure assignments and deadlines without manual work.
Prerequisites
- Microsoft account with access to Power Automate and Planner.
- A plan and a bucket created in Planner (Board/Plan configured).
- Basic knowledge of Power Automate: creating automated flows and using connectors.
Step 1: Choose the right trigger
Decide whether you want to trigger the flow by email or by form. For email use the Outlook connector (When a new email arrives). For Microsoft Forms use (When a new response is submitted). This example uses the email trigger with a condition on the Subject or with a specific tag.
Step 2: Create the automated flow
In the Power Automate portal create a new "Automated cloud flow". Choose the trigger "When a new email arrives (V3)" from the Outlook connector. Configure the mailbox, the folder and, if you want, filter by From or Subject to avoid creating unnecessary tasks.
// Example trigger settings (not executable code, this is configuration) // Trigger: When a new email arrives (V3) // Folder: Inbox // Include Attachments: No // Only with Attachments: No // Importance: Any
Step 3: Add a condition to filter emails
Add a "Condition" action to check if the email matches what you want (for example, Subject contains "Pedido" or Body contains "Criar tarefa"). This prevents creating tasks for all email traffic.
// Simple logical condition (visual example in Power Automate) // Condition: subject contains 'Pedido' OR body contains 'Criar tarefa'
Step 4: Configure the Create a task action in Planner
In the Yes branch of the Condition add the "Create a task" action from the Planner connector. Select the corresponding Group Id and Plan Id for the Plan where you want to create the task. Fill Title with something meaningful (e.g.: Subject of the email) and, if desired, set Assigned User Ids and Due Date.
// Essential fields for Create a task (mapping example) // Title: @{triggerOutputs()?['body/subject']} // Plan Id: (select from dropdown) // Bucket Id: (optional) // Assigned User Ids: [ 'user@exemplo.com' ] (optional) // Start Date Time / Due Date Time: use expressions or fields from the email/forms
Step 5: Add description and attachments (optional)
To add more context to the task use the "Update task details" action from Planner immediately after Create a task. You can copy the body of the email to the Description and attach links or files. If the email has attachments, use the Get attachment and Create file actions to save them and then reference them in the task.
// Mapping example for Update task details // Task Id: output of the Create a task action (use dynamic content) // Description: @{triggerOutputs()?['body/bodyPreview']} // References: add links or URLs to files stored in SharePoint/OneDrive
Step 6: Assign task dynamically
If you want to assign the task based on the content of the email (for example, a name or email in the body), extract that value with expressions or with Parse JSON and place it in Assigned User Ids. If the user does not exist, handle it with an action to notify the administrator.
// Simple example to assign to the email sender // Assigned User Ids: [ @{triggerOutputs()?['body/from/emailAddress/address']} ] // Note: you may need to use the Get user action (Office 365 Users) to obtain the actual ID.
Verify the result
Send a test email with the Subject and content that match the rules and see if the flow runs successfully. In Power Automate open the flow Run history to confirm that the Create a task and Update task details actions executed without errors. Check Planner to see if the task was created, with the correct title, description, date and assignees.
Conclusion
Automating task creation in Planner with Power Automate reduces manual work and ensures request tracking. Next steps: add error handling (configure Run after), integrate with Microsoft Forms or SharePoint for other sources, and use Compose/Parse JSON to extract more complex information. Tip: test with multiple scenarios (no valid sender, no subject) to avoid creating invalid tasks.