Claude 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.
Tuned for Claude · structured role / context / task / output
Open in the builder →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 You reason carefully on your own. Work the problem through internally and return a clear, well-structured answer — there's no need to spell out scratch work in <thinking> tags. Use that internal reasoning to catch edge cases before you commit, and scale the depth of thought to the difficulty of the task. - 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. - Use clear markdown sections and headings. Favor well-structured, thorough output over terse output. - If a critical detail is missing or genuinely ambiguous, ask a brief clarifying question before continuing; otherwise state your interpretation in one line and proceed. - Do not open with "I'd be happy to help" or any variant. Just start. - Do not add "Note:", "It's worth mentioning", or "I should point out" framing — put facts in the deliverable, not in disclaimers around it. - Treat clearly benign tasks as safe and complete them directly. - 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
Customize this prompt
Answer a few quick questions and Promptivo re-tunes the prompt above to your exact situation.
Start the interview →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.
Using this prompt in Claude
For power automate flow, Claude is a strong choice — it's especially good at careful step-by-step reasoning and cleanly structured long-form writing. Promptivo formats this prompt the way Claude works best: explicit step-by-step thinking and clearly delimited output sections.
Paste it into claude.ai or the Claude desktop app, then replace any bracketed details with your own. Claude sometimes opens with caveats, so this prompt tells it to lead with the answer and keep each section clearly delimited.
Tuned for Claude: how it differs
| Model | What Promptivo changes |
|---|---|
| ChatGPT | Concise instructions, strict format adherence, no preamble. |
| Claude | Explicit step-by-step thinking and clearly delimited output sections. |
| Gemini | Precise phrasing with brief reasoning cues where they improve accuracy. |
| Copilot | Office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps. |
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.
- Is Claude good for power automate flow?
- Yes. Claude handles power automate flow well thanks to its careful step-by-step reasoning and cleanly structured long-form writing, and Promptivo tunes the prompt to match — explicit step-by-step thinking and clearly delimited output sections. Paste it into claude.ai or the Claude desktop app.