Route WhatsApp home-service requests by urgency with Groq, Supabase, and Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 11 nodes and runs on WhatsApp events (messages). Along the way it connects Groq Chat Model, Supabase, WhatsApp Business Cloud and Google Sheets.
How it runs
Trigger: On WhatsApp events (messages).
- Set Configuration (Edit Fields (Set)): sets 10 fields: business_name, whatsapp_phone_number_id, oncall_technician_number…
- Extract Request Details (Basic LLM Chain): sends a prompt to an LLM, with model: Extraction Chat Model; output parser: Extraction Parser
- Log Request (Supabase): insert
- Is Emergency? (If): checks a condition and branches into true / false
- Notify On-Call Technician (WhatsApp Business Cloud): send
- Confirm Emergency to Customer (WhatsApp Business Cloud): send
- Add to Service Queue (Google Sheets): append
- Confirm Queued to Customer (WhatsApp Business Cloud): send
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Supabase
n8n-nodes-base.supabase - If
n8n-nodes-base.if - WhatsApp Business Cloud
n8n-nodes-base.whatsApp - Google Sheets
n8n-nodes-base.googleSheets - WhatsApp Trigger
n8n-nodes-base.whatsAppTrigger - Edit Fields (Set)
n8n-nodes-base.set
From the author
Quick Overview This workflow routes incoming WhatsApp home-service requests by using Groq to classify urgency and extract key details, logs every request to Supabase, and either alerts an on-call technician for emergencies or appends routine jobs to a Google…