Skip to main content
Promptivo logoPromptivo
Build a prompt

Prompt to turn Outlook emails into Planner tasks

A prompt for an Outlook to Planner flow in Power Automate: which emails qualify, the Planner plan and bucket, task title and due date rules, the description and checklist, and how to avoid duplicates.

Open in the builder →

Part of the workflow automation prompts collection: Power Automate, Logic Apps, Power Apps, Office Scripts, VBA, PowerShell, Copilot Studio, Zapier, Make and n8n. Writing your own? Read the automation prompt guide.

Ready-to-use prompt

# Role
You are an experienced workflow-automation architect who designs reliable, maintainable automations on the platform in use: a precise trigger, exact connector and action names, explicit conditions, error handling, and a test plan.

# Context
Design a Power Automate flow that turns flagged emails from clients into Planner tasks in the Client Work plan with a due date three days out.


# Task
Design the automation described in the context above for the stated platform: the trigger, each action in order with exact connector or action names, the conditions and approvals, error handling and retries, and how to test it before it goes live.

# How to approach this
Work the problem internally, then give only the result. Do not narrate your reasoning unless it is part of the deliverable.

- Lay the automation out in order: trigger, each action, the conditions and branches, error handling, then a test plan.

Before you finalize, verify that the trigger fires on exactly the intended event and nothing else; every action names the real connector, action, or command for the stated platform; the first failure has a handling path: retry, notify, or stop; the test plan covers the main path and that first failure.

# Constraints
- Do not invent connector, action, or command names. If unsure one exists, say so and use the closest real alternative.
- Follow the requested format exactly. Default to clean markdown. Be concise — no filler, no restating the question.
- Deliver the single best answer rather than hedging across several.
- When uncertain about a fact, API method, library name, or function signature, say so explicitly. Do not produce a plausible guess.
- Do not invent citations, URLs, or package names. If you don't know one, omit it or flag that you don't.
- Deliver the result directly — no apologies or meta-commentary about the prompt itself.

# Output format
Return only the requested output. If multiple distinct variants would clearly help, label them (e.g., "Option A", "Option B").

# Done when
- the output fully answers the goal in the Context section with no missing parts

Tuned for your model

Get a version optimized for the AI you actually use:

Why this prompt works

Most email-to-task flows create noise. The prompt asks for the qualifying rule (sender, subject, flag, folder) before anything is created.

Create a task in Planner needs a Group ID, Plan ID and bucket, and details such as the description live in a separate Update task details action. The prompt asks for these so the design is buildable.

Duplicates are the second failure. The prompt asks how a repeat email is detected, for example by conversation ID or a tracking list.

Questions, answered

How do I create a Planner task from an email?
Trigger on When a new email arrives (V3) with a filter, add Create a task (Planner) with the plan and bucket, then Update task details for the description and checklist. The prompt collects the rules for title, due date and assignment.
Can the flow attach the email to the task?
Planner tasks hold references (links), not file attachments. Include a link to the email or save the attachment to SharePoint and reference it.
How do I set a due date from the email?
Use an expression such as addDays(utcNow(), 3) or parse a date from the subject. The prompt asks for the rule so the expression is designed, not guessed.

Related prompts