WhatsApp in Bitrix24: what actually gets created in your portal
The Open Channel connector, the tab on every CRM card, the automation steps and the event handlers — named, with what each one does, what it does not create, and how to inspect all of it yourself.

On this page
ChatBridge24 is a standalone WhatsApp Business platform, and it is also available as a full-featured app on the Bitrix24 Marketplace. Installed in a portal, it is a WhatsApp CRM integration that lives inside Bitrix24 itself. This article lists, by name, everything the app creates in your portal — what each item does and where to find it — so that you know what you are installing and can inspect all of it afterwards.
Four things are registered when the ChatBridge24 Bitrix24 WhatsApp integration is installed. Every one of them is visible in the portal and every one can be inspected. All four are registered automatically at install and checked again afterwards, so nothing depends on anybody finding a settings page.
1. An Open Channel connector, saabsoft_wa
The connector is what makes WhatsApp appear in Contact Center → Open Channels, as a channel named ChatBridge24 that you can bind to a queue. Once a number is bound, inbound WhatsApp messages arrive in the Open Channel, an agent replies from Bitrix24’s own messenger, and delivery and read receipts travel back.
Two properties worth knowing:
- A number is bound to an Open Channel explicitly, by you. Installing the app registers the connector; it does not route anything. Binding changes how leads are created and how conversations are assigned, so it stays a decision rather than a default.
- Open Channels is optional. You can use ChatBridge24 as a WhatsApp inbox and an automation engine without binding a channel at all, and bind one if and when you want WhatsApp conversations in your Open Channels.
2. A tab on every CRM card
Four placements are registered: the detail tabs of Lead, Deal, Contact and Company. Each adds a tab to that card in which an agent can read the WhatsApp thread and reply without leaving the record.
The matching deserves a description, because it decides whose conversation appears on whose card. A CRM card is matched to a WhatsApp thread in three ways, in order: the Open Channels identifier stored on the record, a link resolved earlier and saved, then the phone number.
The tab looks the record up as the signed-in agent, not as the application, so Bitrix24’s own CRM permissions decide whether this agent may read that record.
3. Automation steps for your rules
The app adds a WhatsApp step to the automation designer for Leads, Deals, Contacts, Companies and Smart Processes, so a rule can send a WhatsApp message as one of its steps. The step is WABA · Send approved template: it sends one of your approved WhatsApp message templates from a WhatsApp Business API number, with its values filled from the record.
A rule runs with nobody watching, so this step carries the most guard-rails:
- Who is addressed is one field, and an empty one refuses. The “Send to” field is the only statement of the recipient. If it is empty, the step refuses and says why — it never falls back to the record’s own phone number, so a rule can only message the person it names.
- Every outcome is recorded. The app’s run log keeps one row per outcome, including each refusal and its reason. By default each send, and each refusal that needs someone’s attention, is also written on the record’s timeline, where your team works.
- Limits that protect the number. A ceiling on runaway rules, a per-recipient cooldown and a consecutive-failure breaker that an administrator clears.
4. Event handlers
The app binds handlers for the events it needs: an agent’s reply in an Open Channel, an Open Channel line being deleted, changes to the portal’s user list — so automation knows who on your team is staff — and the app being uninstalled, plus a test event the app sends to itself to confirm its own connection to your portal. Handlers are matched by event name, so checking them again is safe.
What is not created
As important as the list above, and shorter:
- No custom fields on your CRM entities. When the first WhatsApp message creates a Lead or a Contact, ChatBridge24 fills Bitrix24’s own fields — the phone number when it is known, the Open Channels identifier, the comment and source information, and the UTM fields when the lead’s source carries them — and nothing of its own.
- No users, no workgroups and no automation rules of its own. The step is there for your rules to use.
- Nothing on a card that was not matched. A conversation appears on a record only when the matching described above finds it.
How to inspect all of it yourself
Everything above is visible in your own portal:
- Contact Center → Open Channels — the ChatBridge24 channel, and which of your numbers is bound to which queue.
- Any Lead, Deal, Contact or Company — the app’s tab, and whether the thread it shows is the one you expect.
- The automation designer — the WhatsApp steps, and every rule that uses them.
- The app’s own Automation page — the run log, with one row per outcome, including every refusal and the reason for it.
On the official WhatsApp Business API
The app connects numbers through the WhatsApp Business API, Meta’s own interface: approved message templates, the 24-hour reply window and per-message pricing, and a customer’s messages normally arrive with their phone number. It is also where the Bitrix24 WhatsApp bot runs: a scenario you draw in the app can greet every new chat, ask what you need to know and hand the customer to a person.
Every number works through the same WhatsApp shared inbox, the same connector and the same CRM tab, and every number is priced the same way: per connected number, with your whole team included — see ChatBridge24 pricing.
Need a hand with the rest of your portal? ChatBridge24 is built by Saabsoft, an official Bitrix24 partner specialising in CRM implementation, customisation and digital transformation — see Saabsoft’s Bitrix24 Dubai page. For companies across the Emirates, Saabsoft’s Bitrix24 UAE team can configure the integration and the CRM around it together.
Common questions
Does installing the app route my WhatsApp into the CRM automatically?
No. Installing registers the connector; binding a number to an Open Channel is a separate, explicit action, because it changes how leads are created and how conversations are assigned. Open Channels is optional.
Does a WhatsApp group chat create CRM records for its members?
No, and that is deliberate. A group is one Open Channel chat with no phone number attached, and its members never become leads or contacts in your CRM. They appear in ChatBridge24’s own Contacts, marked as added from a group; a CRM record is created only for somebody who messages the business directly.
What happens to the WhatsApp automation steps when the app is updated?
ChatBridge24 checks its registrations whenever an administrator opens the app and puts back anything that has gone missing, including after an app update. If a rule’s WhatsApp step seems to do nothing after an update, opening the app once as an administrator restores it.
Last updated 25 October 2026.


