Bitrix24 Integration with Beeline Business Telephony
Beeline Business provides corporate telephony in two formats: SIM cards with corporate numbers and a virtual PBX (Beeline Virtual Office). The integration with Bitrix24 is built differently for these two cases — it is important to establish which specific Beeline product the company is using.
Beeline Virtual Office: API and Webhooks
"Virtual Office" is Beeline's cloud PBX with a web management interface. The integration API is available through the Beeline partner program or upon request to corporate support.
Beeline provides webhooks for call events. Configuration in the Virtual Office management portal: Settings → Integrations → API. Supported events:
| Event | Trigger |
|---|---|
call.start |
Inbound call registered |
call.answer |
Employee answered |
call.end |
Conversation ended |
call.record_ready |
Recording ready for download |
Webhook request authorization: Beeline adds the X-Beeline-Signature header with an HMAC-SHA256 signature of the request body. The secret is set during integration configuration.
Corporate SIM Cards with Forwarding to Bitrix24
If the company uses Beeline corporate mobile numbers without a virtual PBX, the Bitrix24 integration is built differently. There are no real-time events here — Bitrix24 cannot see mobile calls directly.
Possible solutions:
- Switch to Beeline Virtual Office — mobile numbers become extensions in the PBX, integration via API.
- SIM connectors (GSM gateways) — hardware devices that take a SIM card and register it as a SIP account. Connected to Bitrix24 directly or through an intermediate PBX via SIP trunk.
- Cloud SIM connectors — services such as SimCom that virtualize mobile SIMs and provide a SIP interface.
Setup via the Official Bitrix24 + Beeline Connector
Beeline and Bitrix24 have an official partnership. In Bitrix24 under "Telephony," connection is available via "Telephony Application." Process:
- In Bitrix24: Telephony → Connect Telephony → Select Beeline Business application.
- Authorization via corporate Beeline account.
- Mapping Beeline extension numbers to Bitrix24 users.
After connection, Beeline PBX calls begin appearing in Bitrix24 through the platform's standard telephony mechanisms.
Recordings and Analytics
Beeline Virtual PBX stores recordings in the cloud. When the call.record_ready event arrives, a download link is provided. Storage duration depends on the plan (from 7 days to 1 year). For uploading to Bitrix24 — standard scheme via telephony.externalCall.attachRecord.
Call analytics in Bitrix24 (reports on volume, duration, missed calls) is built on the data the handler passes when registering calls. For corporate reporting, Beeline also provides its own statistics API — analytics can be built in parallel across both systems.
Case Study: Retail Chain, Corporate Numbers in 6 Cities
A nationwide retail chain with sales offices in 6 cities. Each office operated on its own Beeline Virtual PBX number. Requirement: a single Bitrix24 for all offices, with calls from each city visible only to managers in that city.
Architecture: six separate Beeline Virtual PBX accounts, six webhook endpoints on a single handler server. The handler identifies the office by URL (or by a source header) and inserts the correct LINE_NUMBER for Bitrix24. Call visibility is controlled via CRM access rights in Bitrix24 — each office manager sees only their own calls.
Non-standard requirement: when transferring a client from one office to another (client purchased in Moscow, question for St. Petersburg) — the call must appear for the St. Petersburg manager. Implemented via the transfer event in Beeline Virtual PBX: on transfer, a new call is created in Bitrix24 with the correct office.
Setup time: 6–10 business days (due to coordination across 6 Beeline accounts).