How to Build a Compliant WhatsApp Lead Intake Pipeline with Make.com
WhatsApp is the most popular communication application in Singapore, used by over 97% of the local population daily.
For service-based businesses, capturing leads via WhatsApp is the fastest way to drive engagement. But manually copy-pasting customer names, phone numbers, and booking slots from your phone to your CRM is a massive administrative bottleneck.
Here is how to build a fully automated, PDPA-compliant WhatsApp lead intake pipeline using the WhatsApp Business API and Make.com. For a real-world example of this setup in action, check out the qualification bot we built for Linc Wealth Advisers and Umar Yusof's advisory pipeline.
1. Setting Up the WhatsApp Business API
To automate WhatsApp triggers, you cannot use a standard personal or business WhatsApp mobile application. You must use the cloud-hosted WhatsApp Business API (managed via Meta Developer Console):
- Create a Meta Developer account at
developers.facebook.com. - Register your Singapore corporate phone number.
- Generate a permanent System User Access Token and copy the Phone Number ID.
2. Configuring the Intake Webhook in Make.com
Once your API is connected, create a new scenario in Make.com:
- Trigger Module: Select the WhatsApp Business Cloud API module and choose the Watch Messages event. This creates a secure Webhook URL.
- Meta Webhook: Paste the Webhook URL back into your Meta App configuration under Webhooks so Meta forwards incoming chat payloads to Make in real-time.
3. Extracting and Syncing Lead Payloads
When a new prospect sends a chat message (e.g. "Hi, I'd like to book a lashes consult"):
- Add a Router block to filter incoming text. Only trigger the pipeline if the user provides contact coordinates.
- Use an OpenAI API or Claude API module to parse the raw text and extract variables (e.g. name, interest, preferred date).
- Add a Notion CRM or HubSpot module to create a new row with the parsed fields.
4. Singapore PDPA Compliance Rules
To comply with local regulations, ensure your scenario adheres to these privacy rules:
- Active Opt-in: The first message sent by your automated system must ask the prospect to confirm their consent to be contacted.
- Safe Log Retention: Set your Meta webhook history and Make.com logs to automatically delete webhook payloads after 30 days to enforce storage limitations.