Block 1 - WhatsApp Trigger
- Type / Role
- n8n-nodes-base.whatsAppTrigger - whatsAppTrigger
- Config choices
- Version 1
This workflow implements a WhatsApp based virtual restaurant assistant that automates customer interaction from the first message to post dining follow up. The system can receive messages either fr...
n8n-nodes-base.whatsapptrigger, n8n-nodes-base.whatsapp, n8n-nodes-base.switch, @n8n/n8n-nodes-langchain.guardrails, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.chattrigger, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.chat
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Davide Boizza.
Original n8n.io sourceThis workflow implements a WhatsApp-based virtual restaurant assistant that automates customer interaction from the first message to post-dining follow-up.
The system can receive messages either from WhatsApp or a chatbot interface, normalize the input, and process it through AI guardrails to ensure safe and relevant communication.
The workflow fully automates the customer journey:
No manual intervention is required.
It works both with:
This makes it flexible and easy to integrate into different touchpoints.
The virtual waiter agent:
The workflow includes AI guardrails to:
Customer interactions are stored automatically in Google Sheets, enabling:
Using session-based memory:
The delayed follow-up:
The workflow is built with reusable components:
This makes it easy to:
This workflow automates a restaurant assistant that responds to customers via both WhatsApp and a chat widget on a website. When a customer sends a message, the system checks if it's a menu request or a general query.
WhatsApp messages first go through a switch node that separates text from unsupported formats. If the message is text, it is normalized and passed to a guardrails node that detects jailbreak attempts. If a jailbreak is detected, a fallback message is sent. If safe, the system checks whether the user asked for the menu.
If the user asks for the menu, the workflow saves the clientβs phone number and date to a Google Sheet, then sends a demo menu link via both WhatsApp and the chat interface. After a short wait (1 minute for chat, 2 hours for WhatsApp), the system sends a follow-up message asking for a Google review.
If the user asks something else, the request goes to a virtual waiter agent. The agent uses a Gemini language model, a memory buffer to keep conversation context, and two tools: a calculator and an HTTP Request Tool that fetches the restaurant menu from a ForkMenu API. The agent answers strictly based on the retrieved menu data β it never invents information. The response is then sent back to the customer via WhatsApp and the chat node.
phoneNumberId in all WhatsApp send nodes CLIENT and DATE.https://demo.forkmenu.com/api/menu/piatti/2?key=.... "active": true in the workflow JSON or click "Active" in the n8n editor.When chat message received node requires an n8n chat trigger. Embed the chat widget on your website using the n8n chat embed code.π Subscribe to my new YouTube channel. Here Iβll share videos and Shorts with practical tutorials and FREE templates for n8n.
Contact me for consulting and support or add me on Linkedin.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 35 workflow blocks. Download the JSON for the full node graph.
| Workflow | AI Restaurant Virtual Waiter Chatbot π€π for WhatsApp & Website |
|---|---|
| Complexity | advanced |
| Nodes | 35 |
| Categories | Support Chatbot, AI Chatbot |
| Author | Davide Boizza |
| Published | 04 May 2026 |
Use the JSON export at /data/workflows/15479/15479.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This workflow implements a WhatsApp based virtual restaurant assistant that automates customer interaction from the first message to post dining follow up. The system can receive messages either fr...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot, AI Chatbot use case.