← Back to library

Plan an n8n workflow with AI, then build it yourself

Amin Mahmodi, who builds n8n automations for an education site, shared on the n8n Community forum how he uses a chat model as a planning partner rather than a workflow generator. He describes the job, asks for failure cases in a second pass, names the steps, and wires everything himself. We turn it into a planning routine.

  • OutcomeTalk a new automation through with a chat model before opening n8n: describe the job in plain terms, ask separately what can go wrong, get a readable list of named steps, then connect the nodes yourself and check every field path against real data, using the model only for small code and transform pieces.
  • SetupMinutes
  • LevelStarter
  • CreditAmin_Mahmodi
View original
Works with
n8nChatGPTClaude

Published Nov 10, 2026Updated Nov 10, 2026AI dry run on sample input: passed Nov 10, 2026Source verified Nov 10, 2026

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?

  1. 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.
  2. 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.
  3. Name the stepsAsk for the step list with short action names you will reuse as node names.
  4. Wire it yourselfBuild the workflow by hand in n8n, letting the model write only small code or data-mapping pieces.
  5. 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)

Prompt4 variables
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?
The author found that generated workflows often look correct but break in subtle ways, so he only lets the model write small pieces and does the wiring himself.
Which model should I use?
Any capable chat model works for planning. The value comes from the order of questions, not the model.
Is this the same author as the article pipeline guide?
Yes. Amin Mahmodi also shared the lessons behind his n8n article workflow, which we cover in a separate entry.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Gate after-hours dental phone triage and booking

Calls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.

Credit: u/anassy1 on r/AiAutomations

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Parse reservation mail into draft calendar holds

Every travel or dinner confirmation you label becomes a calendar entry in its own calendar, with the confirmation number and a link to the original email.

Credit: u/easybits_ai on r/n8n

Under an hour
Operations & AdminWorkflow✓ AI dry run

Run client work on projects, skills and scheduled briefs

Client context that persists, recurring research and reports that arrive on schedule, and meeting prep done before you walk in.

Credit: u/Beginning-Willow-801 on r/ManusOfficial

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Write your needs down before building a DIY agent server

Before following an AI through a self-hosted assistant setup, list what you need, try hosted options first, and set a stop point so the project does not become a second job.

Credit: u/No-Star7003 on r/AI_Agents

Minutes