Zapier or Make Workflow Sketch
Use to map an automation before connecting live accounts or customer data.
Use case: Designs a tool-neutral workflow with triggers, transformations, failures, and human review. It can then be implemented in Zapier or Make.
Best tools
- Zapier/Make — Connects supported apps through triggers, actions, filters, and branching.
- Notion — Documents the automation specification, test cases, and ownership.
Fill in your details
Answer the questions below. Your answers are placed into the prompt automatically.
Your filled prompt (preview)
You are my Zapier/Make Workflow sketcher. Sketch an automation workflow that is realistic for the tools you have. Label unknowns.
========================================
PERSONAL CONTEXT (filled by me)
========================================
Job to automate: [JOB]
Trigger: [TRIGGER]
Apps available: [APPS]
Desired steps: [STEPS_DESIRED]
Key data fields: [DATA_FIELDS]
Failure cases to handle: [FAILURES]
Plan/limits constraints: [CONSTRAINTS]
Success looks like: [SUCCESS]
If any field is blank or still shows brackets, list the gap, continue with labelled assumptions, and never invent unverified facts, numbers, citations, or quotes.
========================================
WORKFLOW YOU MUST FOLLOW
========================================
STEP 1 — Scope
Define the automation job from [JOB], [TRIGGER], and [SUCCESS].
STEP 2 — Sketch
Map steps using only [APPS] and [STEPS_DESIRED], with [DATA_FIELDS].
STEP 3 — Reliability
Design handling for [FAILURES] within [CONSTRAINTS].
STEP 4 — Build card
Provide a build checklist and test plan.
========================================
OUTPUT FORMAT
========================================
Use these exact headings:
A. Workflow sketch
B. Apps & trigger
C. Step map
D. Field mapping
E. Error handling
F. Test cases
G. Build checklist
H. Out-of-scope notes
Rules: no fake app features; prefer boring reliability.
You are my Zapier/Make Workflow sketcher. Sketch an automation workflow that is realistic for the tools you have. Label unknowns. ======================================== PERSONAL CONTEXT (filled by me) ======================================== Job to automate: [JOB] Trigger: [TRIGGER] Apps available: [APPS] Desired steps: [STEPS_DESIRED] Key data fields: [DATA_FIELDS] Failure cases to handle: [FAILURES] Plan/limits constraints: [CONSTRAINTS] Success looks like: [SUCCESS] If any field is blank or still shows brackets, list the gap, continue with labelled assumptions, and never invent unverified facts, numbers, citations, or quotes. ======================================== WORKFLOW YOU MUST FOLLOW ======================================== STEP 1 — Scope Define the automation job from [JOB], [TRIGGER], and [SUCCESS]. STEP 2 — Sketch Map steps using only [APPS] and [STEPS_DESIRED], with [DATA_FIELDS]. STEP 3 — Reliability Design handling for [FAILURES] within [CONSTRAINTS]. STEP 4 — Build card Provide a build checklist and test plan. ======================================== OUTPUT FORMAT ======================================== Use these exact headings: A. Workflow sketch B. Apps & trigger C. Step map D. Field mapping E. Error handling F. Test cases G. Build checklist H. Out-of-scope notes Rules: no fake app features; prefer boring reliability.
Pro tip: Test with fake records before granting access to production accounts.
Expected output: A workflow map with fields, branches, safeguards, and test cases.