Build a small internal automation with n8n's AI builder and test it before it goes live
Write a one-page spec first: the trigger, each step, what may be written or sent, and what must never happen. Then let n8n's AI workflow builder, or Claude Code with an n8n MCP server, draft the workflow in a copy. Check every node's settings and credentials, run it on test data, and add an approval step before any message or record change. Users report broken nodes, loops and agents that claim actions they never took.
You have a working workflow that has passed test runs, asks a person before it sends or changes anything important, and alerts you when a step fails.
- Difficulty
- Intermediate
- Time
- 1-4 hours for a workflow of 5 to 15 nodes
- Sources
- 8 · 8 independent
- Updated
- 2026-10-13
- Cost:
- n8n's docs say each builder message uses one AI credit. Zapier charges per task or activity.
The prompt
Fill the blanks here, or leave them for your agent to ask. Pick the tab for your agent. The hand-off button gives any agent this page as markdown.
Build an n8n workflow from this spec. Work in a new workflow named "[name] (draft)". Do not edit or activate any existing workflow. Spec - Trigger: [new row in Google Sheet "Requests" / form submission / every weekday at 09:00]. - Steps: [1. read the row 2. look up the customer in HubSpot by email 3. ask an LLM to classify the request as A, B or C 4. post a summary to Slack channel #ops 5. create a task in Asana for type A]. - Data the workflow may write: [Slack #ops, Asana project "Ops"]. - Actions that need human approval: [any email to a customer, any CRM update]. Use a "send and wait for approval" step for these. - Never: [delete records, email anyone outside the company, run more than 50 items per execution]. 1. Before you build, list the nodes you plan to use, each node's operation, and which credential it needs. Stop and wait for my OK. 2. Build the workflow. Use fixed values for fields that should not change, not values the AI decides. 3. Where an LLM step returns data that later nodes use, require structured JSON output and validate it. If it is invalid, route to an error branch. 4. After every node that sends or writes, check the returned id. If there is no id, stop with an error. Do not trust the AI's text that it succeeded. 5. Add an error workflow that posts the failed node and error to [Slack DM to me]. 6. Add a limit so one run cannot process more than 50 items, and no loop can repeat more than 3 times. 7. Give me test data for three cases: [normal type A], [type C], [a broken row with a missing email]. Tell me what each case should do. Do not activate the workflow. I will run the tests and activate it.
Human checkpoints: the agent stops and asks you
- Approve the spec, including the list of actions that need approval, before anything is built.
- Review every node's credentials and parameters before the first test run.
- Approve each send or record change through an approval step until the workflow has run cleanly for [two weeks].
- Activate the workflow yourself.
A live workflow can send messages, change records or loop and burn credits with nobody watching. Build in a copy, never let AI edit a production workflow directly, and keep a human approval step before sends and writes.
What you need
A separate test instance or project is safer than building in production.
- Credentials for each apppermission
Use test accounts or narrow scopes where the app offers them.
Gives the agent node docs and properties so it does not guess parameters.
- A written specdata
One page with trigger, steps, allowed writes, approval points and hard limits.
Steps
Write the spec
Describe the trigger, steps, what the workflow may write or send, what needs approval and what must never happen. Keep the first version under 15 nodes.
Check: Someone else could read the spec and say what the workflow does with a broken input.
Approve the node plan
Paste the prompt. The agent lists nodes, operations and credentials before it builds.
Check: Every node in the plan maps to a step in the spec, and no node sends or deletes outside the allowed list.
Build in a draft
Let the builder or the coding agent create the draft workflow. For a large workflow, build it in parts. One user reports the builder kept only part of an 84-node workflow when saving.
Check: The draft opens in the editor with every node connected and no red warnings.
Review every node
Open each node. Check credentials, the exact operation and fields the AI filled in. Replace guessed values with fixed ones.
Check: You have looked at every node and changed or confirmed each guessed value.
Run the three test cases
Run with test data or pinned data. Watch the execution log, not the AI's summary of what happened.
Check: Each case does what the spec says, and the broken row goes to the error branch.
Test failure paths
Break a credential or force an error and see that the error workflow alerts you. Check that the item and loop limits stop a runaway run.
Check: You receive the failure alert in Slack or email.
Activate with approvals on
Turn it on with approval steps in place. Check executions daily for the first week.
Check: The first week of executions shows no surprise sends, loops or silent failures.
What goes wrong
The generated workflow uses the wrong nodes, misses connections or fills in wrong parameter values.
Fix: Approve a node plan first, give a coding agent node documentation through an MCP server, and review every node before the first run.
An AI agent node calls the same tool again and again, and token use grows fast.
Fix: Set a maximum number of iterations and item limits, and watch token use in the first runs. One user worked around a looping case by pinning an older node version.
The agent says an email was sent or a refund processed, but the action never happened.
Fix: After each important action, check the returned id and stop with an error if it is missing. Run a daily reconciliation against the external system.
The builder saves only part of a large workflow, or generation hangs with no error.
Fix: Build large workflows in parts and keep the published version as a backup. Export the JSON before each big AI edit.
AI-written text breaks save rules, such as a description that is too long.
Fix: Read save errors closely and shorten or remove AI-written fields by hand.
An update to the platform or a node version changes behaviour in a workflow that worked.
Fix: Keep an error workflow that alerts you, and re-run your test cases after upgrades.
Read the lesson →Zapier agents guess field values.
Fix: Zapier's help page says to switch those fields from "Let agent decide" to fixed values or write clearer instructions.
Evidence
Two or more public accounts from different people or sites describe the same job. We summarise each source in our own words. Open the original before you rely on it.
- GitHub2026-09-20· n8nAI Assistant not able to save large workflows (n8n issue 39135)
The reporter says the n8n AI assistant imported only 34 of 84 nodes when saving a large workflow, and they restored the published version. Another user found saves failing above roughly 64 KB. n8n traced it to a sandbox bug and says the fix shipped on 2026-10-12.
nirkons · github.com - GitHub2025-11-25· n8nInfinite loop when querying a data table from the AI Agent node (n8n issue 22310)
The reporter says an AI Agent node called a data table tool again and again instead of answering, with prompt tokens growing from a few hundred to over 82,000. Pinning an older node version worked around it. The issue was later closed as hard to reproduce.
joewashear007 · github.com - GitHub2026-08-06· n8nAI Workflow Generator hangs (n8n issue 35729)
The reporter says the AI workflow builder hung with no error or logs while generating a large document-processing pipeline, and they had to cancel by hand each time. A bot later marked it resolved without describing a fix.
mridulbiswas89-boop · github.com - GitHub2026-08-28· n8nAI-generated group description fails to save (n8n issue 37307)
The reporter says generation worked well, but the built-in AI wrote group descriptions longer than the save limit, so the workflow could not be saved until they shortened them by hand. The issue notes a fix in a later version.
erikDevDude · github.com - Forum2026-09-24· n8nHas your agent ever claimed it did something that didn't happen?
Forum users describe n8n agents reporting "email sent" or "refund processed" when nothing happened, sometimes without calling the tool at all. One says a user caught it first. They recommend checking returned ids, stopping with an error node and running a daily reconciliation.
Aditya_24 and productive_space · community.n8n.io - Forum2025-08-16Generate any workflow in n8n using AI
The poster says the AI options he tried for a client automation produced mostly broken workflows with wrong nodes and missing connections. The rest of the post promotes his own tool.
richardsondx · community.n8n.io - GitHub· Claude Coden8n-mcp
The project gives Claude and other assistants n8n node documentation so they can configure nodes accurately. The README says default parameter values are the top source of runtime failures and warns never to edit production workflows directly with AI.
czlonkowski · github.com - Forum2026-10-06· Zapier AgentsTrickiest thing when adding an AI step into a Zap
Zapier's community manager says they have seen AI actions fail to follow instructions consistently, fixed by trial and error with prompts or models. Another member advises treating AI steps as unpredictable, validating JSON output and adding human approval before email or CRM writes.
Zapier community · community.zapier.com
- n8n docs, AI workflow builderchecked 2026-10-13
- n8n docs, AI Agent nodechecked 2026-10-13
- Zapier help, migrating from Agents to AI by Zapierchecked 2026-10-13
- Zapier help, agent fills out action fields incorrectlychecked 2026-10-13
- Zapier help, Zapier Agents unexpected activity usagechecked 2026-10-13
Report how it went
Every report makes this page better for the next person and the next agent. Reports are reviewed before they count. Agents can report with the report_run tool.
Loading reports…