Prompt Library

ChatGPT Prompts for Power Automate Flows

20 copy-paste prompts

20 copy-paste ChatGPT prompts for Power Automate: flow design, approval workflows, integrations across Microsoft 365, error handling, and the RPA work that shifts org from manual to automated.

In short: This page contains 20 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 15 prompts are free instantly — no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup · Founder, Techpresso

Last updated May 15, 2026·Hand-curated & tested by the AI Academy team

Flow Design

4 prompts

Flow Design from Process

1/20

[Paste manual process]. Design Power Automate flow. Output: trigger (event-based vs scheduled vs manual), action sequence, conditions + branches, output/notifications, error handling. Walk through logically; specific connectors named.

Designs Power Automate flows.

💡

Pro tip: Manual processes documented = automation candidates. AI helps design flow logic; you build in Power Automate. Translate process steps to flow steps systematically.

Approval Flow Design

2/20

Approval flow for [process]. Output: trigger, approvers (sequential vs parallel vs custom), approval form fields, rejection path, escalation, notifications, audit log, completion action. Approvals = most common automation.

Designs approval flows.

💡

Pro tip: Approval flows replace email-chain approvals. Audit trail + notifications + escalation built-in. Email approval = lost; flow approval = tracked.

Connector Selection

3/20

Connectors for [scenario integrating systems X and Y]. Output: best connector option (Microsoft / certified / community), license requirements (premium connectors cost), authentication method, common limitations, alternative if connector limited.

Selects Power Automate connectors.

💡

Pro tip: Premium connectors require per-user license. Standard connectors free. Many flows can use HTTP REST as fallback for missing connectors. Plan license cost.

Trigger Strategy

4/20

Best trigger for [scenario]. Options: scheduled (recurrence), event (when item created/modified), manual (button), HTTP, instant (Teams). Output: recommended trigger, why, alternatives, common issues. Trigger choice = flow reliability.

Chooses Power Automate triggers.

💡

Pro tip: Wrong trigger = flow doesn't run when needed or runs too often. Event triggers more responsive than scheduled; scheduled more predictable. Match to use case.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Common Automations

4 prompts

New Email → SharePoint

5/20

Flow: when email arrives matching [criteria], save attachment + email body to SharePoint with metadata. Output: trigger conditions (sender / subject / has-attachment), file path logic, metadata mapping, notifications. Email-to-SP automation = inbox decluttered.

Email-to-SharePoint flows.

💡

Pro tip: Common pattern: invoices/POs/contracts via email → archive in SharePoint. Replaces manual save+rename process. Compounds time savings across team.

Form → Notification Flow

6/20

Flow: Microsoft Form submission triggers Teams notification + Excel logging. Output: form-data parsing, conditional notification (only if X), Excel append, error handling. Form responses don't notify by default.

Form-to-notification flows.

💡

Pro tip: MS Forms responses sit in form analytics. Notification flow = team responds in real-time. Excel logging = analysis layer. Zero default; high value to add.

Recurring Task Reminder

7/20

Flow: weekly reminder for [recurring task]. Output: scheduled trigger, recipient list, message customization, escalation if not completed (track completion via Forms or check). Beat the "I forgot" excuse.

Builds recurring reminder flows.

💡

Pro tip: Email reminders ignored. Teams pings + form-based "did you do it?" + escalation = compliance. Reminder design matters.

Document Approval + Notification

8/20

Flow: SharePoint doc requires approval. Output: trigger on new/changed, route to approver group, parallel sign-offs if needed, store decision metadata, notify originator. SharePoint built-in approvals weak; PA replaces.

Builds doc approval flows.

💡

Pro tip: SharePoint native approval limited. Power Automate approval = parallel approvers + escalation + notifications + audit. Standard for serious approval needs.

Error Handling + Maintenance

4 prompts

Error Handling Pattern

9/20

Add error handling to flow [describe]. Output: try-catch pattern (configure run after settings), failure notification, retry logic, fallback action, logging to track recurring issues. Default flows fail silently; designed flows surface errors.

Adds flow error handling.

💡

Pro tip: Default flow failure = silent. Run-after configuration on actions = catch failures + alert. Production flows need error handling; prototype flows skip.

Flow Performance Optimization

10/20

[Paste flow description]. Optimize: minimize action count, batch operations, filter early (don't pull all then filter), parallel branches where possible, choose lighter actions. Slow flows = time out + fail.

Optimizes flow performance.

💡

Pro tip: Each action adds latency. 50-action flow slow + fragile. 10-action flow fast + reliable. Optimization = production stability.

Flow Documentation

11/20

Document flow [name] for handoff/maintenance. Output: purpose, trigger, action sequence (step-by-step), inputs/outputs, error scenarios + handling, owner, last update, dependencies. Undocumented flows = unmaintainable.

Documents Power Automate flows.

💡

Pro tip: Flow author leaves = flow becomes mystery. Quarterly docs update = sustainable flow library. Most orgs let flows decay; documentation is the prevention.

Flow Audit + Cleanup

12/20

Audit [tenant's] Power Automate flows. Output: flows running, flows failing, owner mapping, business value vs cost, candidates for retirement, license utilization. Flow sprawl = real cost.

Audits Power Automate flows.

💡

Pro tip: Flow sprawl in 2 years = 100s of flows, 50% inactive, 25% failing. Annual audit + retirement = sustainable. Without audit = invisible cost accumulation.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Advanced Patterns

4 prompts

HTTP Request + JSON Parse

13/20

Flow calls API: [endpoint]. Output: HTTP action setup (method, URL, headers, auth), JSON parse for response, error handling for API failures, rate limit handling. APIs without connectors = HTTP fallback.

Builds HTTP API flows.

💡

Pro tip: Most SaaS APIs have no Power Automate connector. HTTP action = generic fallback. Authentication + parsing learned once = unlocks everything API-callable.

Loop Through Array

14/20

Flow needs to process array of items: [describe]. Output: Apply to Each setup, parallel vs sequential decision, action per item, aggregation if needed, performance considerations for large arrays. Arrays = common automation pattern.

Builds array-processing flows.

💡

Pro tip: Apply to Each = workhorse. Default sequential; parallel option in settings (5x speedup). Large arrays = batch processing pattern (slice into chunks).

Power Automate Desktop (RPA)

15/20

PAD vs cloud flows for [scenario]. Output: when desktop RPA needed (legacy app, no API, GUI automation), when cloud sufficient, hybrid pattern (cloud triggers desktop), license requirements. RPA last resort.

Decides RPA vs cloud flows.

💡

Pro tip: Desktop RPA fragile (UI changes break it). Cloud flows + API > RPA when possible. RPA when no other option (legacy systems with no API). Don't default to RPA.

Custom Connector

16/20

Build custom connector for [API]. Output: API research (OpenAPI spec ideal), authentication setup, action definitions, parameter mapping, testing, sharing with org. Custom connectors = reusable across flows.

Builds custom connectors.

💡

Pro tip: Common API used in many flows = build custom connector once. Saves repeated HTTP setup. Sharing across org = reuse compounds.

Frequently Asked Questions

Power Automate: best Microsoft 365 integration, included with M365 (basic), enterprise governance. Zapier: largest connector library, easiest start. Make: most powerful (visual flows, scenarios). Choose by primary ecosystem.

Standard = included with M365. Premium (SQL, Salesforce, Dataverse) = require per-user license ($10-20/user/mo). Many flows could be 99% standard if designed thoughtfully.

Center of Excellence (Microsoft template), naming conventions, license governance, ALM (dev/test/prod environments), monitoring + audit. Without governance = flow sprawl + cost surprises.

AI helps design + explain + troubleshoot. Doesn't build flow inside Power Automate. Copilot in Power Automate (separate Microsoft AI) = inline flow generation. ChatGPT for design; build manually.

PA: low-code, fast to build, business-user accessible, governance. Custom code: more control, complex logic, perf-critical. Most workflows = PA wins. Edge cases = custom. Start PA.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Business

7-day free trial. Cancel anytime.

Browse All Prompt Collections