Bitrix24 ↔ Zadarma integration

Zadarma calls move Bitrix24 deals forward: a missed call becomes a task, a finished call updates the stage by your rules, and Bitrix24 automations can place a call themselves

Zadarma already has a ready connection with Bitrix24: dialling from the card, a pop-up client card on calls, recordings and call statistics inside Bitrix24. For many teams that is enough, and we will say so. The Bitrix24 ↔ Zadarma pair is for what comes after the call: your own rules for which deal a call belongs to, a task for every missed call, a stage change after an answered call, and calls started by a Bitrix24 automation, for example a call-back to a lead who left a request at night. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: Bitrix24 →System page: Zadarma →

What moves between the systems

Zadarma → Bitrix24Zadarma reports the moments you switch on, such as call start, answer and call end; the pair finds the lead, contact or deal by phone number using your matching rule.
Zadarma → Bitrix24A missed or unanswered call creates a call-back task in Bitrix24 for the responsible manager, attached to the right card.
Zadarma → Bitrix24An answered call is written to the timeline of the deal with duration and a link to the recording, and by your rule can move a new lead to the next stage.
Bitrix24 → ZadarmaA Bitrix24 automation, for example on a new website request, asks the pair for a call: Zadarma first rings the manager's number, then connects them to the client.
Bitrix24 → ZadarmaWhich manager answers for which card is taken from Bitrix24, so a call started from an automation always goes through the responsible person's number.

What we connect

First we look at the ready Zadarma connection in your Bitrix24: if it already covers your case, we stop there and tell you so.
In Zadarma you pass us the account's user key and secret; every request of the pair is signed with them, and in the notification settings we switch on only the call moments we need.
In Bitrix24 an administrator creates an inbound connection with access to the CRM and tasks, and an outbound one for automations that ask for a call.
We agree the rules: which phone field is matched, what happens when two cards share a number, which call outcome moves which stage, and who gets the missed-call task.
We test on a handful of real calls in both directions, check the tasks and the timeline with your team, then switch the rules on for everyone.

Automation scenarios

A missed call nobody returns

Before a client calls during lunch, the call is visible in statistics, but no one is responsible for calling back.

After a task with the client's card lands on the responsible manager and stays open until it is done.

A night request waits until noon

Before requests from the website pile up overnight and the manager calls them one by one when they get to it.

After at the start of the working day a Bitrix24 automation starts a call for each request through the manager's number.

The lead stays «new» after a talk

Before the manager talked to the lead but forgot to move the stage, and the funnel report shows untouched leads.

After an answered call moves the lead by your rule, and the recording link is in the timeline.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

CRM API methods manage leads, deals, contacts, companies, estimates, invoices and Smart Processes: creating and updating entities, moving them through funnel stages, logging the history in the timeline, generating documents, and launching automation.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
Bitrix24 supports two kinds of webhooks: an inbound one that calls API methods on behalf of the employee who created it, and an outbound one that sends a Bitrix24 event to an external handler URL.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
Call event notifications are configured at a dedicated address with separate switches for each moment: call start, an internal call, call end, outbound call start, outbound call end, and call answered.
Source: zadarma.com ↗ checked 2026-09-25
A call recording is retrieved through a dedicated API method that returns a temporary link to the mp3 file, found by the call's ID.
Source: zadarma.com ↗ checked 2026-09-25
Click-to-call is a dedicated API method: it takes a 'from' number and a 'to' number, calls the first one, then connects it to the second.
Source: zadarma.com ↗ checked 2026-09-25
The ready Bitrix24 connection includes one-click dialling from inside Bitrix24, a pop-up client card on incoming and outgoing calls, listening to call recordings, and full call statistics — all inside Bitrix24 itself.
Source: zadarma.com ↗ checked 2026-09-25

Limits

The limits come from both systems. The ready Zadarma connection for Bitrix24 already covers dialling, the pop-up card, recordings and statistics, so the pair does not repeat it and should not run in parallel with it for the same actions. A recording link from Zadarma is temporary, so the timeline shows where to open it again rather than a permanent copy. Bitrix24 limits how fast requests may come, so on a busy line updates are queued. In Bitrix24 Cloud ongoing access for outside connections exists only on some plans. A call started by an automation always rings the manager first: if the manager does not pick up, the client is not called.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Zadarma already connects to Bitrix24. Why do we need this?

Often you do not, and we will say so after looking. The pair is for your own rules on top: which deal a call belongs to, tasks for missed calls, stage changes after a call, and calls started by Bitrix24 automations.

Where are the recordings kept?

In Zadarma, as before. The pair asks Zadarma for a link to the recording by call ID; the link is temporary, so the recording itself is not copied anywhere.

Can an automation call a client without a manager?

No. The call method rings the first number, the manager's, and only then connects the client. No recorded messages are played to clients by this pair.