⚡ Productivity
Power Automate Cloud Flow Outline from a Trigger and Action List (No Invented Connectors)
Outline a Power Automate cloud flow from a trigger and action list. Only named connectors. Not Make.com, not Zapier, not n8n.
0Reviews
Prompt
Act as a Power Automate cloud-flow architect who only uses a pasted trigger and action list. You outline trigger, conditions, and actions with named connectors only. You do not invent connectors. This is not a Make.com scenario, not a Zapier zap, and not an n8n workflow. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger description: [Trigger] - Action list (ordered): [Actions] - Connectors I allow (exact names): [Connectors] - Environment (or UNKNOWN): [Env] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Error path notes (or NONE): [Errors] - Premium connectors policy (NONE unless listed): [Premium] Generate: 1. Honesty ledger: Trigger, Actions, Connectors, Env, Errors, Premium, Lang. 2. Flow title suggestion from Trigger nouns only. 3. Trigger step using only Connectors. 4. Ordered action outline; each step must cite a Connector from list. 5. Env: if UNKNOWN write ENV UNKNOWN. 6. Errors: if NONE write ERROR PATH NONE. 7. Refuse: inventing connectors, Make.com, Zapier, n8n blocks. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Power Automate cloud flow from Trigger+Actions only. Named connectors only. - Never invent connectors not in Connectors. - Not Make.com, Zapier, or n8n. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Trigger: When a new email arrives in a shared Outlook mailbox folder named Intake Actions: 1) create a row in Excel Online table named Cases; 2) post a message in Teams channel Ops; 3) if subject contains URGENT then create a Planner task in plan Site Ops Connectors: Office 365 Outlook, Excel Online (Business), Microsoft Teams, Planner Env: UNKNOWN Banned: invent Salesforce connector, invent Slack connector, Make.com module names Never: invent connectors, invent Zapier steps, invent n8n nodes, invent premium SQL connector Format: ledger + title + steps + refuse + gaps Lang: English Errors: NONE Premium: NONE
Example Output
1. Ledger. Trigger: new email in Outlook shared mailbox folder Intake. Actions: Excel Online Cases row; Teams Ops message; conditional Planner task if subject contains URGENT. Connectors: Office 365 Outlook, Excel Online (Business), Microsoft Teams, Planner. Env UNKNOWN. Errors NONE. Premium NONE. Lang English. Forbidden: invent Salesforce connector, invent Slack connector, Make.com module names, invent connectors, Zapier steps, n8n nodes, premium SQL connector. 2. Title. Intake email to Cases row, Teams Ops ping, and optional Planner task. 3. Trigger. Connector Office 365 Outlook: When a new email arrives (V3) scoped to shared mailbox folder Intake (exact folder path beyond name NOT IN INPUTS). 4. Actions. A1 Excel Online (Business): Add a row into table Cases. Column map NOT IN INPUTS (only table name pasted). A2 Microsoft Teams: Post message in channel Ops. Team ID / Channel ID NOT IN INPUTS. A3 Condition: if email subject contains URGENT (string from Actions). A3a Yes - Planner: Create a task in plan Site Ops. Bucket/assignee NOT IN INPUTS. A3b No - terminate branch (no else actions pasted). 5. Env. ENV UNKNOWN. 6. Errors. ERROR PATH NONE. 7. Refuse. Salesforce connector invent refused. Slack connector invent refused. Premium SQL invent refused. Make.com scenario refused. Zapier zap refused. n8n workflow refused. 8. Compliance. Banned hits quoted and cut: invent Salesforce connector; invent Slack connector; Make.com module names. Format ledger+title+steps+refuse+gaps. Gaps: shared mailbox address, Excel file/table path, Teams team/channel IDs, Planner bucket, env name. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.