Skip to main content
Promptivo logoPromptivo
Build a prompt

Prompt for a Power Automate flow

A Power Automate prompt for ChatGPT, Claude, Gemini or Copilot that turns a plain description of what should happen into a flow design: exact trigger, connectors and actions, conditions, error handling and a test plan.

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 saves Outlook attachments to a SharePoint library and posts a summary to a Teams channel.


# 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

Power Automate fails quietly when the trigger is wrong, so the prompt forces the trigger event and a trigger condition into the Context block before any action is designed.

Generic AI answers invent connector and action names. The prompt requires the names as they appear in the designer and tells the model to say when an action may not exist.

Most broken flows have no failure branch. The prompt asks for run-after error handling and a notification path, not just the happy path.

Licensing and policy surprise people late: premium connectors, DLP blocks and the SharePoint 5,000-item threshold are called out up front.

Questions, answered

Can ChatGPT or Copilot build a Power Automate flow?
They can design one well when the prompt states the trigger, the connectors, each action in order, the conditions, and what to do on failure. Copilot in Power Automate can also generate the flow from a short paragraph, and this prompt has an output option written for it.
What should a Power Automate prompt include?
The trigger event, the systems involved (Outlook, SharePoint, Teams, Dataverse), the steps in order, any approval or condition, error handling, how often it runs, and any licensing or policy limits such as no premium connectors.
Why does my flow stop at 5,000 SharePoint items?
Unfiltered reads hit the list view threshold. Filter with an OData query and enable pagination on the Get items action. The prompt asks the model to design for this.

Related prompts