When should you use it?
- You built a support or booking chatbot in n8n and are about to hand it to a client
- Users report the bot going silent or forgetting what they said a few turns earlier
- Your agent node can call tools that book, refund, cancel or send things
Not for: Bots with no tools that only answer from a fixed FAQ; the approval gate matters less there; Replacing proper monitoring and on-call coverage for a busy production service; Platforms other than n8n without adapting node names and settings
What do you need, and what do you get?
You need
- The existing n8n chatbot workflow with its AI Agent node, memory node and tools
- A stable identifier for each person (customer ID, phone number or email), not only the chat session
- A list of actions the bot must never take without a person checking first
- A Slack channel or mailbox where approvals can be answered
You get
- An error path that sends a short holding message and alerts you when the model fails or returns nothing
- Memory configured per person, with a history window sized for real support threads
- A short system prompt of hard rules, such as never inventing order numbers
- An approval step (a Wait node after a Slack or Gmail message) in front of each irreversible tool
- A test log showing the bot recalls an early detail and survives a forced model failure
How does it work, step by step?
- Catch failed model callsRoute errors and empty agent output to a branch that replies with a polite holding message and pings you, so the conversation never just stops.
- Key memory to the personSet the memory node's session key to a per-user identifier and raise the message window; around 10 to 20 messages fits most support chats.
- Test recallMention a detail early in a test chat and ask about it five or six turns later. Fix the memory settings if the bot has lost it.
- Write the hard rulesKeep a brief list in the system prompt: do not make up order or booking numbers, and ask before committing to anything.
- Gate irreversible actionsPut a Slack or Gmail approval message and a Wait node in front of booking, refund, cancellation or outbound-send tools.
- Break it on purposeBefore handover, force a model timeout and an empty response in a test run and confirm the holding reply and alert both fire.
The prompt
Our own prompt, inspired by Abid_Nawaz and written to work in n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are the support assistant for {business_name}. Rules you must follow: - Use only facts from {knowledge_source} and the tools provided. If you do not know, say so and offer to pass the question to a person. - Never create, guess or repeat order numbers, booking references or prices that a tool did not return. - Before calling {irreversible_tools}, summarize what you are about to do and tell the customer a team member will confirm it. - Keep track of the details this customer has given you in this conversation and earlier ones, and do not ask for them again. - If a tool fails, apologize briefly, say someone will follow up, and do not claim the action happened.
Inspired by Abid_Nawaz: How I build error-proof AI chatbots in n8n (3 mistakes to avoid). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A session key tied to the browser tab or chat window gives a returning customer a bot with no memory of them.
- Very large history windows raise token costs and can bury the current question. Size it to real conversations, not the maximum.
- Prompt rules alone are not a hard stop. For anything with money or legal weight, the approval gate in the workflow is what actually prevents the action.
- Holding messages that promise a reply need a real follow-up path, or customers wait forever.
Our take
Most n8n chatbot tutorials stop at the moment the bot answers its first question, which is exactly where real trouble begins. Abid_Nawaz's post is short and unglamorous, and that is its value. The three faults it names match what we see in broken support bots: users met with silence when the model call fails, memory tied to the wrong key so returning customers start from zero, and agents allowed to act with nothing standing in the way. None of the fixes needs new tools; they are settings and a couple of extra nodes. We would add one habit: break the bot deliberately before handover, because an error branch that has never fired is an assumption, not a safeguard. In our dry run on a mock workflow for a fictional bike repair shop, a forced model timeout produced the holding reply and an alert within the same run, the bot recalled a customer's bike model six messages later after we keyed memory to the phone number, and a refund request stopped at the approval step until we answered the mock Slack message.
Where the time goes back: Fixing silent failures, forgetful memory and unchecked actions before handover saves the support tickets, apologies and cleanup that follow a chatbot going wrong in front of customers.
FAQ
Which n8n nodes does this use?
Will the approval step slow the bot down?
Is the forum post a downloadable template?
Source and credit
Inspired by Abid_Nawaz. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How I build error-proof AI chatbots in n8n (3 mistakes to avoid)
- Creator
- Abid_Nawaz
- Published on
- n8n Community
- Original date
- Oct 21, 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
- Oct 28, 2026: passed. Dry-run tested by our AI test agent on sample input. Fallback, per-person memory and approval gate all held under forced failures.
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
- Oct 28, 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.