WhatsApp CRM Integration to Connect Any CRM with WhatsApp
Your reps close deals on WhatsApp, then that history dies on someone's phone. WaBulkSend sends approved template campaigns from your own WhatsApp Business Platform number and gives your CRM two ways in: a REST API to create contacts and send campaigns, and signed webhooks that post every delivery status, reply text, and opt-out to an endpoint you choose. Your CRM, Zapier, Make, n8n, or your own code writes it to the contact record.
No free plan. The demo is 25 messages on your own number, one time, and no card is required to create your account.
Webhook to your CRM
ExampleNo native one-click CRM connectors and no two-way sync. Your endpoint decides what gets written where.
Create your account →The short answer: WhatsApp CRM integration connects a WhatsApp business number to your CRM through the WhatsApp Business Platform (Cloud API), so inbound messages and delivery statuses can be written to the matching contact record. The free WhatsApp Business app has no public API and cannot do this. You need a WhatsApp Business Account, a dedicated phone number, a phone number ID, an access token, and an HTTPS webhook that receives message events. Once that webhook is live, your CRM can log replies, create and update records, assign tasks, and fire follow-up automations without anyone copying and pasting a chat.
Where WaBulkSend fits, and where it does not: WaBulkSend is a bulk sender for approved WhatsApp templates. You connect your own Cloud API number, and your CRM talks to it in two directions. Outbound, the REST API creates contacts and creates and sends campaigns to a segment, a tag, or a list of phone numbers, and lets you read campaign results (creating and sending need Pro or Enterprise; Starter can read). Inbound, signed webhooks post message.status, message.failed, message.inbound with the reply text, contact.opted_out, contact.opted_in, template.status, template.quality, and campaign.completed to your endpoint. WaBulkSend does not include a team inbox, you cannot answer chats from it, and there are no native one-click connectors for HubSpot, Salesforce, Zoho, or Pipedrive and no two-way sync. If your team needs to answer chats one by one, do that in a tool built for conversations. WaBulkSend handles the campaigns and reports back by webhook.
Why WhatsApp needs to live inside your CRM
Sales teams already run on WhatsApp. A prospect asks a quick question, a rep answers from their phone, a price gets agreed, and none of it exists anywhere your business can see. When that rep leaves, the relationship leaves with them. When a manager asks why a deal stalled, nobody can reconstruct the conversation. The pipeline says one thing and the phone says another.
Integrating WhatsApp with your CRM fixes the record-keeping problem and then does something more useful: it makes WhatsApp a channel your automations can actually use. A message arrives, the CRM matches it to a contact by phone number, logs it on the timeline, moves the deal stage, and assigns a task to the owner. An outbound utility template goes out when an order ships, and the delivery receipt writes back to the record. Nobody retypes anything.
The technical requirement is straightforward. The WhatsApp Business app on a phone has no public API, so it cannot connect to a CRM. Integration runs on the WhatsApp Business Platform, Meta's Cloud API, which is what WaBulkSend is built on. Meta retired the older On-Premises API in October 2025, so Cloud API is the only supported path today. Meta gives you a webhook that streams every message event and status callback, and an endpoint to send from. With WaBulkSend in the middle, Meta's webhook points at WaBulkSend, and WaBulkSend forwards the events your CRM cares about to your own endpoint, signed so you can verify them. Our WhatsApp API integration guide covers the Cloud API side in more detail.
How to integrate WhatsApp with your CRM in six steps
From a bare Meta Business account to replies and delivery statuses landing on contact records.
Set up the WhatsApp Business Account
Create a Meta Business account and a WhatsApp Business Account, then verify the business. Verification is one of the ways you move past the starting messaging limit of 250 unique customers per rolling 24 hours.
Register a dedicated number
Use a phone number that can receive a voice call or SMS and is not already tied to another WhatsApp account. A Meta Business Account starts with 2 registered numbers and can be raised to 20, so departments can each have their own.
Connect the number to WaBulkSend
Meta issues a phone number ID and an access token. Paste them into WaBulkSend with your WhatsApp Business Account ID, and point Meta's webhook at WaBulkSend so statuses and replies are recorded.
Add your CRM endpoint as a webhook
In WaBulkSend, add an HTTPS endpoint (your CRM, a Zapier, Make, or n8n catch hook, or your own code) and pick the events: message.status, message.inbound, contact.opted_out, campaign.completed, and more. Every call carries an HMAC signature to verify.
Map contacts and automate
Match the phone number in each event to a CRM contact, create one if it is new, write the reply or status to the timeline, then trigger the follow-up in your CRM: assign an owner, move a stage, open a task.
Send from the CRM through the API
Create an API token in WaBulkSend. Your CRM or automation tool calls the REST API to add contacts and to create and send a campaign on an approved template to a segment, a tag, or a list of phone numbers (Pro or Enterprise).
What WaBulkSend sends to your CRM
These are the webhook events WaBulkSend posts to your endpoint, signed with an HMAC SHA256 header. The data flows one way, from WaBulkSend to your endpoint. What gets written to a contact, deal, or ticket is up to your CRM or automation tool.
| Webhook event | What you get | Typical CRM action |
|---|---|---|
| message.inbound | Sender phone number, WhatsApp profile name, message type, the reply text, and the campaign it answered when known | Log the reply on the contact timeline, create the contact if new, notify the owner |
| message.status | Sent, delivered, read, or failed for each campaign recipient, with timestamps | Update the activity record, mark the step done |
| message.failed | The Meta error code and reason for a failed recipient | Fix the number, alert ops, retry later |
| contact.opted_out / opted_in | Phone number, name, source (a STOP reply or a change in the app), time | Set or clear a do not message flag in the CRM |
| template.status / template.quality | Approval, rejection, or pause, and quality rating changes from Meta | Flag a template before Meta pauses it |
| campaign.completed | The finished campaign and its totals | Report results, start the next step in your CRM |
How the major CRMs handle WhatsApp
Some CRMs ship their own WhatsApp channel, others connect through the Cloud API and a webhook. WaBulkSend works with all of them the same way: through its REST API and webhooks, not through a native connector. Seat prices and message caps for six of them are in our best WhatsApp CRM comparison.
HubSpot
HubSpot ships a native WhatsApp channel for the Conversations inbox on Marketing Hub or Service Hub Professional and Enterprise. It logs chats to contacts and triggers workflows, with a shared cap of 1,000 template messages a month.
HubSpot WhatsApp integration →Zoho CRM
Zoho has first-party WhatsApp business messaging inside the CRM under Business Messaging, plus a WhatsApp channel in Zoho SalesIQ for a unified chat inbox. Both need a WhatsApp Business API account behind them.
Zoho WhatsApp setup guide →Pipedrive
Pipedrive relaunched a native WhatsApp channel, in beta on the Growth plan and above, connecting through Meta's Cloud API. It handles 1:1 conversations on the deal but does not broadcast, so pair it with a sender for campaigns.
Pipedrive WhatsApp integration →ActiveCampaign
An official BSP whose native channel can actually broadcast to a segment, built up from its Hilos acquisition. WhatsApp sits alongside email and SMS in automations, though it rides inside the full suite with demo-based pricing.
ActiveCampaign WhatsApp integration →Salesforce
Service Cloud ships a native Enhanced WhatsApp Channel through the Messaging add-on, and Marketing Cloud sells WhatsApp separately. Large orgs often wire the Cloud API straight into Leads, Cases, and Opportunities instead, using Flow to route ownership.
Salesforce WhatsApp integration →Your own CRM
Anything that can accept an HTTPS POST can take WaBulkSend's signed webhooks. Receive the event, verify the signature, match the phone number, and write the record. Call the WaBulkSend REST API to add contacts and send template campaigns back out.
WhatsApp API integration →Spreadsheets and no CRM yet
If contacts still live in a sheet, export it as CSV or Excel and upload it to WaBulkSend. Replies are counted per campaign and recorded on each contact. Move to a CRM once the volume justifies it.
Send from Excel →Why the free app cannot integrate with a CRM
This is the single thing most teams get wrong before they start.
| Capability | WhatsApp Business app | WhatsApp Business Platform (Cloud API) |
|---|---|---|
| Public API to connect a CRM | None | Yes, REST endpoints plus webhooks |
| Conversation logged to a contact record | No | Yes, every inbound and outbound message |
| Users on one number | One phone plus up to four linked devices | As many as the software you connect allows |
| Assign a chat to an owner | No, every linked device sees every chat | Yes, in a CRM or help desk built for conversations |
| Trigger a CRM workflow from a message | No | Yes, from the webhook event |
| Send from an automation or a deal stage | No | Yes, via the messages endpoint |
| Cost | Free | Free to call, per delivered template message |
What teams do once WhatsApp is in the CRM
Patterns your CRM or automation tool can run with WaBulkSend's REST API and webhooks. The logic lives in your CRM. WaBulkSend sends the templates and reports what happened.
Capture the reply automatically
Someone answers a campaign or messages the business number. WaBulkSend posts message.inbound with their number, WhatsApp name, and the reply text, and your CRM creates or updates the contact, tags the source, and assigns a rep.
Keep the campaign history on the record
message.status events write sent, delivered, read, and failed to the contact timeline next to the emails and calls, so a rep taking over a territory sees what went out and what landed.
Trigger from a stage change
A deal moves to Proposal and your CRM calls the WaBulkSend API to send a utility template with the quote. The delivery status comes back by webhook, so you know it landed and was read.
Follow up from your CRM workflow
No reply in two days? Your CRM workflow calls the API to send the next template, and skips it when a message.inbound event already arrived. WaBulkSend does not run sequences itself, your CRM decides when to send.
Order and delivery updates
Your store or ERP updates a record, your automation calls the WaBulkSend API to send the shipping template on WhatsApp, and the status lands on the customer timeline.
Respect opt-outs everywhere
A contact replies STOP. WaBulkSend opts them out of future campaigns and posts contact.opted_out, so your CRM can set its own do not message flag too.
What US teams need to know before they wire it up
Meta paused delivery of marketing category template messages to US phone numbers on April 1, 2025, and as of July 2026 there is no announced resume date. That does not block a CRM integration, and it does not stop the workflows most sales teams actually want. Utility templates, such as an order update, an appointment confirmation, or a quote, still deliver to US numbers. Authentication templates still deliver. Any reply you send inside the 24-hour customer service window, after a customer messages you first, needs no template at all and is free up to 1,000 replies per business number each month.
Practically, that means a US CRM integration should be built around conversations the customer starts, plus utility messages tied to a real transaction. Click-to-WhatsApp ads still work as a way to get people to message you first, which opens that free window. Design the automation so an inbound message opens the door and your templates carry transactional information, not promotions. WaBulkSend sends approved templates only, so free-form replies inside that window come from whatever tool your team answers chats in.
On billing, Meta moved from per-conversation to per-message pricing on July 1, 2025. You pay when a template message is delivered, priced by the template's category, and service messages inside the open 24-hour window are free for the first 1,000 per business number each month and billed at the utility rate for the destination country after that, since October 1, 2026. Calling the API itself costs nothing. See the full breakdown on our WhatsApp Business API pricing page.
Frequently asked questions
Can WhatsApp be integrated with CRM?
Yes. WhatsApp integrates with a CRM through the WhatsApp Business Platform, also called the Cloud API. You register a business phone number, get a phone number ID and an access token, and subscribe an HTTPS webhook to message events. Your CRM then logs every inbound and outbound message on the contact record and can send replies back through the API.
How do I integrate WhatsApp with my CRM?
Create a Meta Business account and a WhatsApp Business Account, verify the business, register a dedicated phone number, and collect the phone number ID and access token. With WaBulkSend, you paste those into the app, add your CRM, Zapier, Make, or n8n endpoint as a signed webhook, and match the phone number in each event to a contact. Your CRM sends outbound template campaigns by calling the WaBulkSend REST API. You set up the Meta side yourself, WaBulkSend does not register numbers for you.
Does the WhatsApp Business app have an API for CRM integration?
No. The free WhatsApp Business app has no public API, so it cannot be connected to a CRM. It is built for a single business owner on a phone with up to four linked devices. Any real CRM integration, including conversation logging and automation, requires the WhatsApp Business Platform Cloud API.
Which CRM works best with WhatsApp?
Zoho CRM is the cheapest native option, with WhatsApp on every paid edition from $14 per user a month. HubSpot ships a native channel on Marketing Hub or Service Hub Professional and Enterprise, capped at 1,000 messages a month. Pipedrive has a native channel in beta on Growth and above. Salesforce and custom CRMs connect through the Cloud API and a webhook.
Is WhatsApp CRM integration free?
Calling the WhatsApp Cloud API is free, and the first 1,000 replies per business number each month inside the 24-hour customer service window cost nothing. You pay per delivered template message, priced by category. Your CRM may also charge for its messaging add-on. HubSpot, for example, includes a shared allowance of 1,000 template messages a month across connected WhatsApp accounts.
Can I sync my old WhatsApp chats to a CRM?
Generally no. Integrations sync messages from the moment the connection goes live, not historical threads. HubSpot states plainly that existing WhatsApp conversations do not import. Plan the switch on a date, export anything critical beforehand, and treat the integration as the start of a clean record.
Will messages still show in the WhatsApp app after I connect a CRM?
Not on the same number. Once a phone number is registered to the Cloud API, it leaves the WhatsApp Business app and its messages route to your API endpoint instead. HubSpot warns about this too. Use a dedicated number for the integration and keep any personal or in-store number separate.
Does WaBulkSend have a native HubSpot or Salesforce integration?
No. WaBulkSend has no native one-click connectors and no two-way CRM sync. It connects to any CRM through its REST API (create contacts, create and send campaigns, read results) and signed outbound webhooks (message.status, message.inbound with the reply text, contact.opted_out, campaign.completed, and more). Your CRM, Zapier, Make, n8n, or your own code receives the events and writes them to the record. WaBulkSend also has no team inbox, so chats are not answered from it.
How many phone numbers can one WhatsApp Business Account have?
Meta Business Accounts are initially limited to 2 registered business phone numbers, and that limit can be raised to 20. A Meta Business Account is also initially limited to 20 WhatsApp Business Accounts, and each WhatsApp Business Account holds a maximum of 250 message templates. That is enough for sales, support, and separate brands to each run their own number under one CRM integration.
Put WhatsApp replies and statuses on the contact record
WaBulkSend sends your template campaigns on the official WhatsApp Cloud API and posts every status, reply, and opt-out to your CRM by signed webhook, so you stop losing deal history to someone's phone. One-time demo: 25 messages on your own number, no card required.
Start sending