TimelinesAI Blog

Bitrix24 WhatsApp Business API: Options, Trade-Offs, and Setup Paths

Compare the five practical ways to connect WhatsApp with Bitrix24, including Twilio, Edna, Cloud API connectors, TimelinesAI, and Instant WhatsApp.

September 4, 202611 min readOrkhan Jafarli· Product & Growth Lead

Bitrix24 can work with WhatsApp through several routes, but they are not interchangeable. Twilio and Edna connect WhatsApp Business Platform accounts to Bitrix24 Contact Center. Other providers package Meta's Cloud API for Bitrix24. TimelinesAI connects the WhatsApp accounts your team already uses and syncs them with CRM records. Bitrix24's Instant WhatsApp is a website widget channel, not a full WhatsApp Business API connection.

Choose based on the number you need to keep, where agents should reply, whether you need API templates, and who will own the provider relationship. This guide was checked against current Bitrix24, Meta, and TimelinesAI documentation on September 4, 2026.

Short answer

Use a WhatsApp Business API route when your operation needs Meta-hosted APIs, approved outbound templates, webhooks, or centralized API governance. Bitrix24 documents direct Contact Center setup through Twilio and Edna. A separate Cloud API connector or custom middleware is another option.

Use TimelinesAI for Bitrix24 when the priority is connecting existing regular WhatsApp or WhatsApp Business app accounts by QR code, logging 1:1 conversations in CRM, and letting agents send from Contact, Lead, and Deal records without first building a Cloud API deployment.

Use Instant WhatsApp only when you want website visitors to start a WhatsApp conversation that agents receive in Contact Center. It does not replace a WABA connection.

What "WhatsApp Business API for Bitrix24" can mean

The search term covers several different products:

Meta's WhatsApp Business Platform Cloud API, which sends and receives messages programmatically.
A business solution provider such as Twilio or Edna that handles onboarding and connects a WhatsApp Business Account to Bitrix24.
A Bitrix24 Marketplace connector that provides its own CRM interface and routing.
A linked-account product such as TimelinesAI that connects an existing WhatsApp account and synchronizes messages with Bitrix24.
Bitrix24 Instant WhatsApp, a website widget channel that starts a customer conversation but is not a Cloud API deployment.

That distinction matters. Two products may both say "WhatsApp integration" while using different number types, billing models, messaging rules, and agent workflows.

Decision table: which route fits?

Bitrix24 Contact Center with Twilio

Best fit: Teams already using Twilio or wanting a documented provider connection inside Bitrix24 Contact Center.
Existing number: Bitrix24 says you must rent or transfer a number in Twilio, subject to Twilio's limitations. Ask Twilio whether your current WhatsApp Business app number qualifies for Meta Coexistence before assuming you need to replace it.
Bitrix24 surface: Open Channels and Contact Center.
API and templates: WhatsApp Business Platform rules apply. Outbound messages outside the customer service window require approved templates.
Main trade-off: You manage Twilio setup, verification, phone-number eligibility, webhooks, provider billing, and Meta message charges.

Bitrix24's current guide asks for a Twilio Account SID, Auth Token, and account phone number. It also requires the Bitrix24 webhook URL in Twilio's sender configuration. Bitrix24 does not charge an extra WhatsApp integration fee for this path, but Twilio and Meta charges can apply.

Bitrix24 Contact Center with Edna.io

Best fit: Teams in markets served by Edna that want Edna Pulse onboarding, templates, and Bitrix24 Open Channels.
Existing number: Confirm eligibility with Edna. Bitrix24's guide requires a Meta Business Manager account and an Edna WhatsApp Business API channel.
Bitrix24 surface: One Edna channel connects to one Open Channel. Additional numbers need additional channels and Open Channels.
API and templates: Edna supports operator and custom message templates in its documented flow.
Main trade-off: Connection, licensing, messaging, and Meta-related charges are separate. Availability depends on provider coverage and your Bitrix24 Open Channel limits.

Edna uses a Subject ID and API key to connect the channel to Bitrix24. This is a managed provider path rather than a do-it-yourself Cloud API build.

Another WABA connector or a custom Cloud API build

Best fit: Teams that already have a BSP, need a provider not covered by Bitrix24's native guides, or want custom control over routing and data flows.
Existing number: It depends on the provider's migration and Coexistence support.
Bitrix24 surface: Varies. Some apps use Open Channels; others write CRM activities or embed a separate inbox. A custom build must implement this mapping.
API and templates: Cloud API, webhooks, template approval, message status events, and Meta pricing apply.
Main trade-off: The architecture is flexible, but you must verify who owns the WhatsApp Business Account, phone number, templates, webhooks, data retention, and support escalation.

Meta's Cloud API exposes programmatic messaging and relies on webhooks for incoming messages and delivery updates. That gives developers control, but it does not create a Bitrix24 agent experience by itself. The connector or your middleware still has to match phone numbers, create or update CRM records, and route replies.

TimelinesAI linked-account integration

Best fit: Sales and support teams that want to keep using existing WhatsApp or WhatsApp Business app accounts, connect them by QR code, and add Bitrix24 logging and sending without a direct Cloud API project.
Existing number: Yes for regular WhatsApp and WhatsApp Business app accounts connected through the documented QR flow.
Bitrix24 surface: CRM activities on matched records, sending from Contact, Lead, and Deal records, broadcasts to selected records, and optional Open Channels routing.
API and templates: This is not the same architecture as choosing Meta Cloud API through a BSP. Teams that require WABA-native template governance or a specific API compliance model should choose a WABA route.
Main trade-off: You add a TimelinesAI subscription and workspace to the stack. Feature availability can also depend on the connected TimelinesAI and Bitrix24 plans.

The current Bitrix24 integration writes new 1:1 inbound and outbound messages to CRM activities. Admins can group a chat into one daily activity or switch to one activity per message. Agents can select a connected sender when they send from a CRM record. The current broadcast tool supports up to 200 selected recipients per batch. See the Bitrix24 setup guide for the installation flow and the Bitrix24 WhatsApp pricing guide for plan costs.

Bitrix24 Instant WhatsApp

Best fit: A Bitrix24 website that needs a simple inbound WhatsApp entry point.
Existing number: The customer starts the conversation from the website widget. This is not a business-number API onboarding path.
Bitrix24 surface: One Open Channel in Contact Center.
API and templates: No Cloud API account is created by this feature.
Main trade-off: Bitrix24 says the customer appears as a Guest because WhatsApp does not pass the name or phone number through this flow. Agents must reply within 24 hours of the customer's last message.

Instant WhatsApp is useful, but the name causes confusion. Treat it as a widget option, not as an alternative provider for a WhatsApp Business Account.

Keeping an existing WhatsApp number

The answer depends on what that number is connected to now.

Existing WhatsApp Business app number

Meta supports a provider onboarding flow called Coexistence. A provider that has implemented the required Embedded Signup flow can connect an existing WhatsApp Business app account and phone number to Cloud API. The business can continue one-to-one messaging in the Business app, while supported messages are mirrored between the app and Cloud API.

Coexistence is not automatic across every Bitrix24 connector. Meta requires the provider to be a Solution Partner or Tech Provider and to implement the correct signup and webhook flow. Ask the connector vendor to show that your exact number and country are eligible. Meta currently documents a fixed throughput of 20 messages per second for numbers used with both the Business app and Cloud API.

Existing regular WhatsApp number

A regular consumer WhatsApp account is not the same as a WhatsApp Business Account. A WABA provider may require you to move the number through a business onboarding or migration process. If keeping the current app-based workflow matters more than adopting Cloud API, a linked-account route such as TimelinesAI is the simpler fit.

Existing WABA or Cloud API number

Ask who owns the WABA, phone-number asset, display name, templates, and billing account. Provider migration can affect access tokens, webhooks, template ownership, and the cutover window. Do not cancel the old provider until inbound messages, outbound templates, and Bitrix24 routing pass a live test on the new path.

Cloud API rules that affect the decision

Meta charges WhatsApp Business Platform messages on a per-message basis. Rates vary by template category and the recipient's country calling code. Non-template messages can be sent only inside an open customer service window. Meta says non-template messages are not charged, and utility templates sent in response to users inside that window are also free under the current pricing rules.

Outside the customer service window, a business must use an approved template. Template categories include marketing, utility, and authentication. Your provider may add its own platform, number, or support fees on top of Meta charges.

The operational impact is more important than the rate card:

Sales reps cannot assume they can send any free-text follow-up at any time from a Cloud API connector.
Marketing and automation teams need an approval and change process for templates.
Finance should model Bitrix24, provider, phone-number, and Meta usage costs separately.
Support needs to know whether failed delivery status comes from Meta, the provider, the connector, or Bitrix24.

For a cost model, use the Bitrix24 WhatsApp integration pricing guide together with the provider's current rate card and Meta's pricing page.

How to choose without creating a migration problem

Answer these questions before you install anything:

Which number must survive the change? Record whether it is on regular WhatsApp, the Business app, or Cloud API, and who owns it.
Where should agents work? Decide between Bitrix24 Contact Center, CRM record actions, a provider inbox, or the WhatsApp app.
Do you need outbound templates? If campaigns must start outside the service window, choose a route that supports template creation, approval, and reporting.
How should Bitrix24 store conversations? Check whether the connector creates activities, Open Channel chats, Leads, Contacts, or Deals, and how it handles duplicate phone numbers.
Who handles failures? Write down the support owner for Meta onboarding, provider billing, Bitrix24 permissions, and CRM mapping.
What does the full stack cost? Include the Bitrix24 plan, provider or connector subscription, phone-number fees, Meta charges, and implementation time.
What must be proven before cutover? Test inbound messages, free-text replies, a template sent outside the service window, delivery status, attachments, record matching, and agent permissions.

Do not make the production number your first test. Use a pilot number or a limited agent group, then document the working path before migrating the rest of the team.

When TimelinesAI is the better fit

TimelinesAI is the better fit when a team already has working WhatsApp or WhatsApp Business app numbers and wants Bitrix24 visibility without first moving those numbers into a direct Cloud API provider setup.

It is also a strong fit when agents need to send from Contact, Lead, and Deal records, admins need configurable CRM activity logging, or a manager wants one integration for several connected numbers. Optional Open Channels routing is available when the Bitrix24 plan supports that surface.

Choose a WABA provider instead when the requirement is specifically Meta Cloud API, approved template governance, API-level throughput, or a policy that forbids a linked-app architecture. The products solve overlapping CRM problems, but they are not the same technical route.

You can install the TimelinesAI app from Bitrix24 Marketplace or start a TimelinesAI trial. If you want to see the CRM flow first, book a demo.

Frequently asked questions

Does Bitrix24 support WhatsApp Business API natively?

Bitrix24 documents WhatsApp connections through Twilio and Edna inside Contact Center. Those are provider-based WhatsApp Business Platform routes. Bitrix24 also has Instant WhatsApp, but that is a website widget channel rather than a WABA connection. Marketplace apps provide additional architectures.

Can I connect my existing WhatsApp Business number to Bitrix24?

Possibly. A linked-account connector such as TimelinesAI connects an existing WhatsApp Business app account by QR code. For Cloud API, an existing Business app number can remain in the app only when the selected provider supports Meta's Coexistence onboarding and your account meets the requirements. Confirm eligibility before signing a provider contract.

Do I need a new phone number for Bitrix24 WhatsApp API?

Not always. Bitrix24's Twilio guide describes renting or transferring a number. Meta Coexistence can let an eligible Business app number connect to Cloud API through a supporting provider. TimelinesAI uses the WhatsApp accounts already connected to its workspace. The correct answer depends on the route, country, and current number type.

Is TimelinesAI a WhatsApp Business API provider?

The Bitrix24 product described here uses a linked-account flow: users connect WhatsApp or the WhatsApp Business app to TimelinesAI by QR code, then authorize Bitrix24. It should not be evaluated as if it were the same deployment as Meta Cloud API through Twilio, Edna, or another BSP.

What is the difference between Open Channels and CRM activities?

Open Channels is Bitrix24's queue-based agent chat surface. CRM activities are timeline records attached to Leads, Contacts, Companies, or Deals. A connector may support one, the other, or both. TimelinesAI supports CRM activity logging and optional Open Channels routing; the documented Twilio and Edna paths use Contact Center and Open Channels.

Which option is fastest to set up?

For a team keeping existing app-based WhatsApp accounts, the TimelinesAI QR flow avoids a separate Cloud API project. For a team already standardized on Twilio, Edna, or another BSP, its current provider path may be faster because the WABA, templates, and billing are already in place. The slow part is usually number eligibility and business verification, not the Bitrix24 install itself.