Instant lead alerts on WhatsApp with n8n
A webhook catches the form submission, n8n validates and enriches it, sends a template message to the salesperson on duty and starts a timer that escalates if nobody claims the lead. The escalation matters more than the notification, because it is what stops leads going cold.
TL;DR verdict
Email alerts don't work, because email is where notifications get ignored. WhatsApp works because your salespeople already have it open. Add an escalation step, or all you have built is a faster way to ignore leads.
| Step | n8n node | What it does |
|---|---|---|
| Trigger | Webhook | Receives the form submission the moment it is sent, with signature verification on |
| Validate | IF | Drops obvious spam and malformed submissions before anyone is notified |
| Enrich | HTTP Request | Adds whatever context you have: company, campaign source, previous contact |
| Route | Switch | Picks the salesperson on duty by region, product or a simple rotation |
| Notify | WhatsApp Business Cloud | Sends a template message with the lead details and a claim link |
| Log | HTTP Request | Writes the lead and the notification time to the CRM |
| Escalate | Wait + IF | After a set interval, checks whether the lead was claimed and notifies a manager if not |
Which we'd pick, scenario by scenario
1. Catch the submission
Point the form at an n8n Webhook node, not at an email inbox. A form that emails a shared address has already lost, because nobody owns a shared address. Verify the signature and reject unsigned posts.
2. Filter before you notify
An IF node that drops obvious spam protects what makes this work: your team's trust in the alert. After two junk notifications people start ignoring the channel, and the workflow stops doing anything useful.
3. Route to a person, not a group
A Switch node that picks one owner by region, product or rotation makes one person accountable. Broadcast to a group and everybody assumes somebody else has it, which is how a lead sits untouched for an afternoon.
4. Send a template message
Business-initiated WhatsApp messages have to be templates, so the alert is a pre-approved template with the lead details filled in. Submit it for approval in the Meta console before you build the node: Meta's review can take up to 24 hours, and a rejection sends you round again.
5. Escalate on silence
A Wait node followed by an IF that checks whether the lead was claimed is the part that changes the numbers. Fifteen minutes is a reasonable first interval. Without this step you have a notification but no process.
6. Log everything
Write the notification time and the claim time to the CRM. Once you can see time to first contact for each salesperson, the conversation about response times rests on data instead of opinions.
This workflow exists because most marketing budget is lost in the gap between a form submission and a human reply. The lead filled in your form because they were thinking about it right then. Forty minutes later they are doing something else and may have filled in a competitor's form. Nothing in the funnel is as cheap to fix as that gap, and nothing gets ignored as consistently.
Teams usually try email alerts first and decide that alerting doesn't work. The problem is ownership, not email. An alert that goes to everyone belongs to no one, and nothing happens when someone ignores an alert that has no follow-up. So the two nodes that matter here are the Switch that assigns exactly one owner and the Wait that escalates when the lead is still unclaimed. WhatsApp billing helps too. Your replies inside a customer-initiated 24-hour window are free. When a lead arrives through a click-to-WhatsApp ad and you reply within 24 hours, everything you send for the next 72 hours is free across all categories, as explained in WhatsApp Business API pricing. We cover the other reasons leads don't pick up in why your Meta Ads leads don't answer the phone.
Sources
Frequently asked
Why WhatsApp instead of email or Slack?
Because your salespeople already have it open on the phone they carry. Email alerts get batched with everything else, and Slack works only if the team lives in Slack. The best channel is the one already unlocked in their hand.
Do I need WhatsApp Business API for this?
Yes, for business-initiated messages. The regular WhatsApp Business app can't be automated this way. You need a Business Platform account and a pre-approved message template, and Meta's review of a template can take up to 24 hours.
What does it cost to send these alerts?
Alerts to your own team are business-initiated template messages, billed per delivered message by category and country. At one message per lead the cost is small next to the value of the leads it recovers.
How long should the escalation timer be?
Fifteen minutes is a sensible starting point for inbound leads, and shorter for high-intent sources like a call request. Pick a number, log the outcomes and adjust once you can see the real claim times instead of guessing.
Can the workflow contact the lead directly instead?
Yes, and that is usually the next build: an assistant that replies to the lead within seconds, qualifies them and books a meeting, with the human alert as a fallback. That is the WhatsApp bot pattern, not the alert pattern.
Which process costs you the most?
Thirty minutes, free. You leave with a concrete fix plan and what the process costs you. The plan is yours, even if you build it without us.
Book a free audit