⚡ Productivity
Make.com Scenario Outline from a Trigger and Action List
Outline a Make.com scenario from pasted triggers and actions. No invented apps, webhooks, or mappings.
0Reviews
Prompt
Act as a Make.com architect outlining a scenario from a trigger and action list. You outline a Make.com (formerly Integromat) scenario from modules the user already has. You do not invent an app, a webhook URL, or a field mapping. This is not n8n, not Zapier, not Jira automation, and not a GitHub Action. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Make.com plan and region I use: [Plan] - Trigger module I already connected: [Trigger] - Action modules I already connected, in order: [Actions] - Field mappings I can prove (source -> target): [Map] - Filters and routers I allow (or NONE): [Filters] - Error handler I allow (or NONE): [Errors] - Webhook URL I may print (or NONE): [Hook] - What I must never call: [Never] - Words I must not use: [Banned] - Scheduling I can prove (or NONE): [Schedule] Generate: 1. Honesty ledger: plan, trigger, every action app, mappings, hook, schedule. Forbidden: apps and URLs not listed. 2. Module chain: Trigger then Actions in order. Number them. Do not insert a router unless Filters names one. 3. Mapping table: only Map rows. Missing fields write NOT IN INPUTS rather than guessing. 4. Filters: only Filters. If NONE, linear chain. 5. Errors: only Errors. If NONE, default scenario-level halt, do not invent a Slack alert. 6. Hook: only Hook. If NONE, no webhook URL. 7. Schedule: only Schedule. If NONE and Trigger is not polling, write schedule not specified. 8. Compliance pass: quote Banned words, n8n nodes, invented apps. Cut them. Constraints: - Make.com scenario outline only. Not n8n, Zapier, Jira automation, or GitHub Actions. - Never invent an app, webhook, or mapping. - Do not add modules that are not in Trigger or Actions. - If Hook is NONE, do not mint a URL. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Plan: Make.com Core, EU region Trigger: HubSpot CRM 'New deal in stage Closed Won' (connection already named HS-prod) Actions: 1) Google Sheets 'Add a row' spreadsheet Deals-Won tab Won. 2) Gmail 'Send an email' from billing@northwind.example. No Slack module connected. Map: deal name -> sheet column A; amount -> column B; contact email -> Gmail To. Close date not mapped. Filters: NONE (no router) Errors: NONE (do not Slack) Hook: NONE Never: Slack, Salesforce, production webhook mint Banned: n8n, Zapier, Slack webhook, 200 operations guess Schedule: instant via HubSpot trigger; no extra cron
Example Output
1. Ledger. Make.com Core EU. Trigger HubSpot New deal Closed Won HS-prod. Actions: Google Sheets Add a row Deals-Won/Won; Gmail Send from billing@northwind.example. Map: name->A, amount->B, contact email->Gmail To. Close date unmapped. Filters NONE. Errors NONE. Hook NONE. Schedule instant. Forbidden: Slack, Salesforce, n8n, Zapier, minted webhook, ops count. 2. Chain. 1 HubSpot Closed Won. 2 Google Sheets Add a row. 3 Gmail Send. No router. 3. Map. A deal name. B amount. Gmail To contact email. Close date NOT IN INPUTS. 4. Filters. NONE. Linear. 5. Errors. NONE. Halt on error. No Slack. 6. Hook. NONE. 7. Schedule. Instant HubSpot. No cron. 8. Compliance. Cut banned. Gaps: sheet id, Gmail template, close date column, error email, operations quota. 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. 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.