ChatGPT Prompts for Power Automate Flows

[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.

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.

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.

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.

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.

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.

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.

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.

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.

[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.

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.

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.

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.

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.

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.