What it does: Reads all your Make scenarios and writes what each one does, which apps it touches, if it's risky, and who owns it.
Use it when: You have scenarios nobody remembers building, and you're not sure what runs on its own.
You get: One table of every scenario with an owner and a done check, and the 3 to look at first.
You are my automation lead, a pro with 15 years of keeping a small business's automations known, owned and safe. Goal: list every Make scenario I have, what it does, what apps it touches and who owns it, so I have one page that shows what runs my business on its own and nothing runs that nobody knows about. Context: I run a small business. Over time I and my helpers built scenarios and forgot some of them. They need an owner each, because a scenario with no owner breaks quietly or keeps sending things nobody wants. First, check that you can open my Make account through the Make connector. Tell me how many scenarios you found, and how many are on and off. If you can't open it, stop and follow the Make steps at simpleai.community/connect/, or ask me to paste a list of my scenario names and what each one does instead. Ask me these, then run. Skip any I already answered. 1. Who are the people on my team who build or own scenarios? (Default: just me. Put [check: owner] where you can't tell.) 2. Should I look at turned off scenarios too? (Default: yes, list them in their own group.) Do this: 1. List every scenario: name, on or off, folder, how it starts (a schedule, a webhook or an app event) and how often it runs. 2. For each one, read its modules and write what it does in one plain line, like "New Tally form, add to HubSpot, email me." Only say what the modules show. Don't guess more. 3. List the apps and connections each one uses. Mark any that send email or texts to customers or people outside my team, take or move money, or change customer records. Those are the risky ones. 4. Check the last run date. Mark any that are on but had no run in 30 days, and any with errors in the last 7 days. 5. Check for doubles: two scenarios that start from the same trigger and do the same thing. List them side by side. Only call it a double if the modules match. 6. Give each scenario one owner from my team list, so one person owns each part. Use the folder or name if it shows who built it. If you can't tell, write [check: owner]. 7. For each one, write what done looks like in one line, so the owner can check it worked, like "Every new form lead is in HubSpot within 5 minutes." 8. Pick the 3 scenarios to look at first: risky ones with errors, then on with no runs, then doubles. Say why in one line each. Give me a table with one row per scenario: name, on or off, how it starts, how often, what it does, apps, risky (yes or no), last run, owner, what done looks like. Then the 3 to look at first, 3 lines. Keep the summary at the top under 60 words. Example of one row, match this: "Lead to CRM | on | app event | each new entry | New Tally form, add to HubSpot, email me | Tally, HubSpot, Gmail | yes | Oct 27 | Jo | Every form lead is in HubSpot within 5 minutes." Before you show me, check: - The number of rows matches the number of scenarios you found at the start. - Every "what it does" line traces to that scenario's modules, not its name alone. - Every risky mark is a scenario that sends outside my team, moves money or changes customer records. Rules: - Read only. Drafts only. Ask me before you turn on, turn off, run, edit or delete any scenario, or change anything. - Never make up a name, number, date, price, link or promise. Use only what is in Make and what I tell you. - If something is missing, write [check: what is missing] in that spot and keep going. - Mark a scenario risky only if it sends to customers or people outside my team, takes or moves money, or changes customer records. Email only to me is not risky. - Never show passwords, API keys or webhook links in your answer. Write [hidden] instead. Last, save these steps as a skill called 'Scenario Map' in Claude or ChatGPT so you do it this way each time I want to know what runs in Make. To run it again, just say: "Run my Scenario Map skill."
You need
Make![]()
Any AITested on sample data
Built on Extreme Ownership's Decentralized Command: let each person own their part.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Sample data run (simulated tool).
Watch: no video for this one yet.
AuthorCorey Leon