When should you use it?
- You are about to build an n8n workflow and want to think it through first
- Past workflows broke on rate limits, empty responses or retries you never planned for
- Someone else will inherit your workflows and needs to read them later
Not for: Pasting generated workflow JSON straight into production; Integrations the model does not know well, unless you check every option in the docs; Tiny two-step automations you can build faster than you can describe
What do you need, and what do you get?
You need
- A chat model such as ChatGPT or Claude
- A plain description of the job, its trigger and its result
- A few real sample records for checking field paths later
You get
- A step-by-step plan in plain language
- A list of failure cases with what should happen for each
- Readable names for every node
- Small code or transform snippets, checked against real data
How does it work, step by step?
- Describe the outcomeTell the model what should happen in business terms, such as which leads arrive, what to filter and who gets told, without naming any nodes.
- Ask what breaksIn a second message, have it list what could fail and the right response to each, including rate limits, empty results, pagination, expired tokens and repeats on retry.
- Name the stepsAsk for the step list with short action names you will reuse as node names.
- Wire it yourselfBuild the workflow by hand in n8n, letting the model write only small code or data-mapping pieces.
- Check against real dataRun each expression and field path on real sample records, and confirm any node option the model mentioned actually exists.
The prompt
Our own prompt, inspired by Amin_Mahmodi and written to work in n8n, ChatGPT and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
I want to build an automation in n8n. Here is the job in plain terms: {job_description}. It starts when {trigger} and should end with {result}. Step 1: Give me a short plan in plain language. Do not name n8n nodes yet. Step 2: Separately, list what can go wrong (rate limits, empty results, pagination, expired tokens, duplicates on retry and anything specific to {apps}) and what the workflow should do in each case. Step 3: Give me the final step list with a short action name for each step that I can use as the node name. Do not generate workflow JSON. If you mention a node option, tell me how sure you are that it exists.
Inspired by Amin_Mahmodi: n8n Community: how I use prompting to sketch n8n workflows (and where it still falls apart). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Models make up node settings, most often for niche integrations. Check the node's settings before you rely on one.
- Generated workflow JSON can look correct while relying on outdated node versions or field paths that do not match your data.
- Models are optimistic about APIs. Ask about pagination and token refresh directly, because they rarely come up otherwise.
- A plan is not a test. Run the workflow on real records before it goes live.
Our take
There is a lot of excitement about agents that build whole n8n workflows from one sentence, and this post is a useful counterweight from someone who builds them for a real site. Amin Mahmodi treats the model as a planning partner that is good at questions and unreliable at wiring, which matches what we see. The most valuable habit is the separate failure-case pass. Asking what can break in its own message gets far more honest answers than hoping the first plan covers it, and it brings up the dull problems, pagination and token refresh, that sink real workflows. Naming each step in plain words is a small idea with a long payoff for whoever maintains the workflow later. Our one addition is to keep a few real records on hand from the start, since every field path the model suggests needs checking against actual data. This is a light routine rather than a system, and that is its strength. In our dry run, the planning prompt produced a six-step lead workflow, seven failure cases including a duplicate on retry, and named nodes for each step.
Where the time goes back: Failure cases surface during a ten-minute chat instead of in production, and named steps make the workflow quick to fix months later.
FAQ
Why not let the model build the whole workflow?
Which model should I use?
Is this the same author as the article pipeline guide?
Source and credit
Inspired by Amin_Mahmodi. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- n8n Community: how I use prompting to sketch n8n workflows (and where it still falls apart)
- Creator
- Amin_Mahmodi
- Published on
- n8n Community
- Original date
- Nov 10, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Nov 10, 2026: passed. Dry-run tested by our AI test agent on sample input. Plan, separate failure pass (7 cases) and named steps delivered in order; no JSON generated; uncertain node option flagged.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 10, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.