Escalate a WhatsApp message nobody answered in 15 minutes
Logs every inbound WhatsApp message as open, waits fifteen minutes, then re-reads the log.
The WhatsApp trigger fires on every inbound message. A Set node captures the number, message id, a 160-character preview and the arrival time — before the wait, because the payload is gone on resume. A Google Sheets append writes the message as open, which is the shared state an agent marks as answered. The Wait node then holds the execution for fifteen minutes with no cron and no polling. On resume the sheet is read again and a Code node finds this message's row by id, treating a missing row as unanswered so the flow fails towards noise rather than silence. An IF escalates only the still-open messages to a Slack channel, quoting the customer verbatim so whoever picks it up needs nothing else. Both external calls retry and route failures to an error rail on Discord — a different service from the escalation channel.
Key benefits
- ✓A fifteen-minute silence is caught while the customer is still in the conversation
- ✓The answered check re-reads the source after the wait instead of trusting stale state
- ✓A missing row escalates rather than disappearing, so the failure mode is noise not silence
- ✓The escalation carries the customer's exact words, so nobody has to open WhatsApp to triage it
- ✓No cron job and no state table — the Wait node persists the execution for you
Use cases
- →Teams whose WhatsApp line is their main support channel
- →Businesses with a stated response time on chat
- →Agencies covering a client's WhatsApp during business hours
- →Anyone who has found a furious customer message that sat unanswered all afternoon
Integrations
Workflow preview (10 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (10 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Moving data between Google Sheets, Slack and Discord in a single run
- •Adding retries and an explicit error path to external calls
- •Testing against pinned sample data before connecting anything real
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (WhatsApp, Google Sheets, Slack, Discord). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Answer WhatsApp keywords automatically and hand the rest to a human
Matches inbound WhatsApp messages against three keyword rules and answers them instantly. Anything else is handed to a human in Slack with the customer's original wording, and every message is logged so the rules can be improved from evidence.
Act on customer feedback on a schedule
Escalation on n8n: runs on a schedule across Google Sheets, Slack, Discord and Google Drive, starting at "Keep Valid Tickets". Routes each kind of record down its own branch. 22 documented nodes.
Classify support tickets: Google Sheets
Escalation on n8n: runs when a webhook arrives across Google Sheets, Discord and Slack, starting at "Normalize Ticket Payload". Classifies each item with a language model. 23 documented nodes.
Summarize documents for escalation
Escalation on n8n: runs when a webhook arrives across Google Sheets, Discord and Slack, starting at "Collect Raw Text". Pulls structured fields out of free text. 19 documented nodes.