ANY OTHER CRM
Any CRM, over one API
Bitrix24 has its own full-featured app on the Bitrix24 Marketplace. Every other CRM connects through the ChatBridge24 REST API and signed webhooks, today.
A CRM connects to WhatsApp through ChatBridge24 in two directions. When a customer writes to your number, the message is posted to your CRM as a signed webhook; when your CRM needs to reach a customer, it sends an approved message template through the REST API on the Enterprise plan. Delivery and read status come back on the same webhook.
Any system that can receive an HTTPS request and make one can do this today, on a number connected to the WhatsApp Business API: the webhooks on every plan, template sends on Enterprise. It is a WhatsApp CRM integration you own, shaped around your own data.
How a CRM connects
Three movements, with one API key and one webhook endpoint.
A customer writes to your number
We store the message and post a signed webhook to your endpoint: the text, the sender’s number and name, and the conversation it belongs to. On a customer’s first message it also carries where they came from — a landing page’s campaign and form answers, utm values, or the Click-to-WhatsApp ad they tapped. You decide what it becomes in your CRM: a lead, a task, a note on a record.
Your CRM writes back
On the Enterprise plan, one API call sends an approved template, with its values, from your connected number. Every call carries an idempotency key, so a retry from your own job queue cannot send the customer the same message twice.
We tell you what happened to it
Sent, delivered, read and failed arrive on the same webhook endpoint, so the state in your CRM is a fact rather than an assumption about whether a send worked.
What your side decides
The parts that are about your own data and your own team.
Which record a message belongs to
Matching a phone number to a customer record is a decision about your own data, so your CRM makes it, in the way that fits your data model. The webhook gives you the number, the name and a conversation identifier that stays the same for the whole conversation.
Where your team answers
If your CRM has no inbox, your team answers in the ChatBridge24 shared inbox while your CRM holds the record. The two work side by side on the same number: your team replies in the inbox, and your CRM keeps the record up to date from the webhooks.
When to answer a webhook
Answer with a 2xx status once you have stored the event, because any 2xx counts as delivered. A failed delivery is retried for about eleven hours, and an endpoint that keeps failing is switched off; its events are held for up to 30 days and released by a successful test.
Native connectors
Bitrix24 natively, and every other CRM through the API.
Bitrix24 has a native connector: the full-featured ChatBridge24 app on the Bitrix24 Marketplace, with Open Channels, a WhatsApp tab on the Lead, Deal, Contact and Company cards and on the Smart Processes you choose, and automation steps; the Bitrix24 WhatsApp integration page describes it. Every other CRM connects through the API, so nobody has to wait for a connector to start.
If you would like a native connector for your CRM, tell us which CRM you run.
Where it sits
WhatsApp REST API and webhooks
Scoped keys, the required idempotency key, and the webhook queue that holds.
CRM connectors
Every way ChatBridge24 connects: the Bitrix24 app, the API and the workspace.
Standalone WhatsApp workspace
The shared inbox, templates, campaigns and the bot, with no CRM required.
Tell us which CRM
From the blog
Further reading on this subject.
WhatsApp CRM integration for any CRM
Webhooks, the REST API and the lead source a customer arrives with.