You stop missing WhatsApp leads by making sure every new message creates a record, gets an acknowledgement and lands with a named person who is reminded if they do not reply. n8n can run that flow automatically: it receives the message from the WhatsApp Business Platform, updates your CRM and alerts your team in the tool they already watch.
This guide covers the prerequisites, the workflow, key decisions, common mistakes and data protection.
Why WhatsApp enquiries slip through
WhatsApp is personal by design. Messages often arrive on one phone, are read by whoever picks it up and are then buried under the next conversation. Nothing records that a lead arrived, who owns it or whether anyone replied.
The cause is rarely a lack of effort. It is a lack of a system: no record, no owner and no reminder. Automation closes those three gaps, but it does not replace the person who has the conversation.
What you need before you build
API access to WhatsApp: Automation needs the WhatsApp Business Platform, using the Cloud API hosted by Meta, either directly or through a Business Solution Provider. The ordinary WhatsApp Business app on a phone does not offer an official integration route on its own.
An n8n instance: You can use n8n's hosted service or self-host it on your own server. Self-hosting gives you more control over where data sits, but you take on updates, backups and monitoring.
A system of record: A CRM or, at minimum, a shared database with an API. The workflow needs somewhere durable to write each lead and its status.
Agreed rules: Who owns which enquiries, what counts as a reply and how long a lead may wait before it is escalated. Write these down before anyone opens n8n.
The workflow, step by step
Receive: A WhatsApp trigger or webhook node in n8n receives each incoming message with the sender's number, profile name and message content.
Deduplicate: Webhooks can be delivered more than once. Store each message ID and skip any you have already processed, or you will create duplicate leads and replies.
Match or create: Look up the number in your CRM. If the contact exists, attach the message to their record; if not, create a new lead with WhatsApp as the source.
Acknowledge: Send a short reply confirming the message arrived and when to expect a response. Do not promise a callback time your team cannot meet.
Route and notify: Assign the lead using clear rules such as keywords, a menu choice, the number messaged or the time of day. Alert the owner in Slack, Microsoft Teams, email or the CRM itself.
Remind and escalate: Flag any lead without a reply after the agreed time and escalate it to a manager or shared queue. A scheduled check of the CRM for open leads is usually more dependable than a long wait inside one execution, because it survives restarts.
Log: Record each step against the lead so you can see later what happened to every enquiry.
Decisions that shape the build
Rules or AI classification: Keyword and menu rules are predictable and easy to audit. An AI model can classify free-text enquiries or draft replies, but it needs testing, a fallback route and human review before anything it writes reaches a customer.
Hosted or self-hosted n8n: Hosted is quicker to start. Self-hosted suits organisations with data residency requirements or an existing cloud and DevOps team.
Direct API or a provider: Going direct to Meta avoids a middle layer. A Business Solution Provider can add a shared inbox, onboarding help and support, usually for an additional fee.
Where replies happen: Decide whether staff answer from a shared inbox, the CRM or another tool. Replies sent outside the integrated tool are not recorded, which reopens the gap you set out to close.
Common mistakes to avoid
Unofficial tools: Scripts that drive WhatsApp Web break WhatsApp's terms and can get a number restricted or banned. Use the official platform.
Ignoring the 24-hour window: You can reply freely within 24 hours of the customer's last message. After that, you need a pre-approved message template, so prepare follow-up templates in advance and check Meta's current pricing.
Over-automating the conversation: Long menus and repeated bot messages put people off. One clear acknowledgement followed by a prompt human reply is usually the better experience.
Silent failures: Set up an error workflow in n8n so a failed CRM write or an expired access token raises an alert instead of quietly dropping leads.
No owner for the workflow: Someone must own the automation itself, review failures and update the routing rules when the team changes.
Data protection and UK GDPR
This section is general information, not legal advice. Confirm what applies to your organisation with a qualified adviser.
Phone numbers, names and message content are personal data. Be clear about your lawful basis for processing them, mention WhatsApp and your CRM in your privacy notice, and collect only what you need to handle the enquiry.
Set retention rules for messages and logs, including n8n's execution history, which can store full message content unless you configure it otherwise. Check where each tool stores data and that you have agreements with each processor.
If you plan to send follow-up or promotional messages, gather opt-in first; WhatsApp requires it for business-initiated messages. The ICO's guidance on UK GDPR and on direct marketing is the place to start.
Testing and measuring the flow
Before going live, test real scenarios: a new contact, a returning customer, a duplicate message, a message out of hours, a voice note or image, and a CRM outage. Each should end in a recorded lead or a clear alert.
After launch, track a few simple measures: leads received, time to first human reply, leads escalated and leads with no recorded outcome. Review them weekly at first and adjust the rules.
How Softweb Planet can help
Softweb Planet designs and builds n8n workflows through our AI Automation & Workflow Automation service and connects them to your sales tools through our CRM Solutions work. Our AI Chatbots & Virtual Assistants service can add AI triage with a clean handover to your team.
We start with a discovery call to understand your enquiries, tools and rules, then send a written proposal with a clear scope. You get a named lead and working software to review every one to two weeks. Costs depend on scope, and we give a fixed quote after discovery.