An n8n WhatsApp order bot for a restaurant broke 5 ways
Huzaifa Aamish built a WhatsApp chatbot in n8n that answers menu questions and takes orders for a demo burger restaurant, using Gemini and self-hosted n8n on a laptop with Meta's free test number. He shared five things that broke and the fixes: messages never reached n8n until he set up a tunnel and subscribed the business account, the access token died after 24 hours, read receipts triggered extra runs, the bot forgot the order one message later until memory was keyed to the phone number, and voice notes got no reply. He shares the workflow free on GitHub.
Copy this prompt
You take orders for [RESTAURANT] on WhatsApp. Menu with prices: [MENU]. Answer only from this menu and these hours: [HOURS]. To take an order, confirm each item, size and quantity, read back the total, and ask for a name and pickup time. If someone asks for something not on the menu, a refund or a complaint, say a staff member will reply and stop. Never make up prices or items.
Our own prompt for the AI step in a bot like this, written from the post. We haven't run it ourselves. Text in [BRACKETS] is what you replace.
Watch out for
- His bot ran a demo restaurant on a test number. Before real customers use it, have a person see every order, and check WhatsApp's business messaging fees.
- He found that none of the failures showed an error to the customer, just a slow or silent bot. Test with a real phone after every change.
Where this comes from
Original post by Huzaifa_Aamish on n8n Community, Nov 17, 2026. We rewrote it in our own words. The result is what the poster reports.
Read the original