How to use Power Automate tasks in Outlook for productivity?

Power Automate can create a personal Microsoft To Do task when a matching email arrives in your work mailbox. Start with one narrow filter and one destination list. This is different from creating a shared Planner task or configuring Outlook rules and automatic replies.

Create a personal To Do task from a filtered Outlook email

You need an eligible work or school account with access to Power Automate, an Office 365 Outlook mailbox connection, and a Microsoft To-Do (Business) connection. Open To Do first and identify the personal list that should receive the tasks.

  1. Create the cloud flow

    Open make.powerautomate.com, confirm the environment, and choose Create > Automated cloud flow. Name it Email follow-up test and select Office 365 Outlook > When a new email arrives (V3).

  2. Limit the trigger

    Select Inbox as the Folder. In the trigger’s additional parameters, set Subject Filter to [Followup-Test] and From to your own work email for the initial test. Set Include Attachments to No; this example does not process attachment contents.

  3. Add the correct task action

    Add a step and choose Microsoft To-Do (Business) > Add a to-do (V3). Authenticate the intended account and select its To-do List. Do not choose Planner’s similarly named task action when the destination is your personal list.

  4. Map the email fields

    Set Title to the email trigger’s Subject dynamic value. In Content, add the From and Message Id dynamic values with descriptive labels. Leave optional due-date and reminder fields blank for this first test instead of guessing a deadline from the message.

  5. Save and send one controlled input

    Save the flow and select Test > Manually where offered. Send one harmless new email from the configured address with [Followup-Test] Review sample in its subject. Check the mailbox received it, then inspect the flow’s run history.

  6. Verify the saved task

    Open the successful run and inspect the task action’s inputs and returned task identifier. In To Do under the same account, open the selected list and find the exact title and source message ID. A successful trigger alone does not prove task creation.

If no task appears

If no run starts, compare the actual arrival folder, From address, and subject with the trigger filters. This is a new-email flow, not a guaranteed backfill of existing messages moved around afterward. If a run fails, inspect the failed connector action before resubmitting the email.

The To Do connector reference specifies the current Add a to-do (V3) action. Replays and retries can duplicate tasks; this starter flow does not provide exactly-once processing. Keep the source ID and review existing runs before manually retrying a successful creation.

After verification, narrow the real sender and subject criteria before replacing the test filters. If the task belongs to a team, use the separate Planner task actions. For a Teams notification instead of a task, see the message automation procedure.