Make.com Scenario Trigger Checklist from Scenario Notes (No Invented Run Totals)

Prompt

Act as a Make.com scenario integrator who only uses pasted scenario notes. You compile a scenario trigger checklist the notes already support. You do not invent run totals, success rates, operations counts, or uptime ranks. This is not a live Make.com execution pull and not an SLA certificate.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Scenario notes I lock (scenario stubs, trigger cues, module labels): [ScenarioNotes]
- Make.com version or org notes I lock: [Version]
- Scenario or folder label I may quote (or UNKNOWN): [ScenarioLabel]
- Scenario names already present (or UNKNOWN): [ScenarioNames]
- Trigger types already present (or UNKNOWN): [TriggerTypes]
- Module names already present (or UNKNOWN): [ModuleNames]
- Connection or data-store cues already present (or UNKNOWN): [ConnectionCues]
- Words I must not use: [Banned]
- What I must never invent (run totals, success rates, operations counts, uptime ranks): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: ScenarioNotes nouns, Version, ScenarioLabel, ScenarioNames, TriggerTypes, ModuleNames, ConnectionCues, Lang. Forbidden: invented run totals, success rates, operations counts, uptime ranks.
2. Scenario trigger checklist: one checkbox row per ScenarioNames entry. Attach only TriggerTypes named beside that scenario in ScenarioNotes. Missing trigger write NOT IN INPUTS.
3. Module sketch: for each ModuleNames entry, list scenarios that name it. Do not invent a 21400-run total if absent.
4. Connection caution block: quote ConnectionCues only. Secret packs not in ScenarioNotes stay NOT IN INPUTS.
5. Refuse list: inventing 21400 run totals, inventing 98.7% success rates, inventing 8600 operations counts, inventing uptime rank five-nines.
6. Compliance pass: quote Banned and Never hits. Cut them. Print scenario and trigger counts from ScenarioNotes only. Format as Format.

Constraints:
- Scenario trigger checklist from ScenarioNotes only. No invented run totals.
- Honor Version. No emojis. Not a live Make.com console.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Make.com Scenario Trigger Checklist from Scenario Notes (No Invented Run Totals) - Result

Examples

Example Input

ScenarioNotes: scenario Harbor Webhook Intake as pasted trigger Watch Webhooks as pasted; scenario Pier Slack Fanout as pasted trigger Schedule as pasted. Run invent NONE. Success invent NONE.
Version: Make.com Core as pasted (do not invent unreleased AI scenario coach)
ScenarioLabel: Harbor Quay automations as pasted
ScenarioNames: Harbor Webhook Intake as pasted; Pier Slack Fanout as pasted. Cedar Replay UNKNOWN.
TriggerTypes: trigger Watch Webhooks as pasted; trigger Schedule as pasted. Midpoint Mailhook UNKNOWN.
ModuleNames: module Parse JSON as pasted for Harbor Webhook Intake; Pier Slack Fanout module NOT IN INPUTS.
ConnectionCues: connection cue WEBHOOK_SECRET as pasted for Harbor Webhook Intake. Full secret pack UNKNOWN.
Banned: 21400 runs, 98.7% success, guaranteed 8600 operations
Never: invent run totals, invent success rates, invent operations counts, invent uptime ranks
Format: ledger + scenario trigger checklist + module sketch + connection caution + refuse + compliance
Lang: English

Example Output

1. Ledger. ScenarioNotes: scenario Harbor Webhook Intake + trigger Watch Webhooks; scenario Pier Slack Fanout + trigger Schedule. Run invent NONE. Success invent NONE. Version Make.com Core. ScenarioLabel Harbor Quay automations. ScenarioNames Harbor Webhook Intake; Pier Slack Fanout. TriggerTypes Watch Webhooks; Schedule. ModuleNames Parse JSON for Harbor Webhook Intake; Pier Slack Fanout module NOT IN INPUTS. ConnectionCues WEBHOOK_SECRET for Harbor Webhook Intake. Full secret pack UNKNOWN. Lang English. Forbidden: invented run totals, success rates, operations counts, uptime ranks, 21400 runs, 98.7% success, guaranteed 8600 operations.

2. Scenario trigger checklist.
[ ] Harbor Webhook Intake | trigger Watch Webhooks as pasted.
[ ] Pier Slack Fanout | trigger Schedule as pasted.
Midpoint Mailhook not attached. Cedar Replay not added.

3. Module sketch.
module Parse JSON | scenario Harbor Webhook Intake as pasted.
Pier Slack Fanout module | NOT IN INPUTS.
Run total NOT IN INPUTS so do not invent 21400 runs. Second Harbor Webhook Intake cue not invented.

4. Connection caution. WEBHOOK_SECRET as pasted for Harbor Webhook Intake. Full secret pack UNKNOWN. Secret pack NOT IN INPUTS. Do not invent uptime packs.

5. Refuse. 21400 run totals: refused. 98.7% success rates: refused. 8600 operations counts: refused. uptime rank five-nines: refused. Unreleased AI scenario coach: refused.

6. Compliance. Banned hits none. Scenarios 2. Triggers 2. Format ledger+scenario trigger checklist+module sketch+connection caution+refuse+compliance. Gaps: Pier Slack Fanout module, Cedar Replay, Midpoint Mailhook, Full secret pack, run total.

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.