Bitrix24 Zadarma Integration: Complete Guide

Lost Calls? The Official Connector Isn't Enough

Clients lose calls due to the limitations of the standard Zadarma connector. We see it on nearly every second project: the official module struggles with more than two SIP numbers, call attribution breaks, and lead creation logic doesn't align with business processes. Statistics show up to 40% of incoming calls get lost due to incorrect routing. Zadarma support documentation confirms these limitations. With our direct integration via the Zadarma API, you get 100% attribution and automatic lead creation, cutting processing time by 30%. Our team has 10+ years of experience with Bitrix24 and Zadarma, delivering over 50 successful telephony integration projects. We've connected virtual PBXs for companies with numbers in four countries, and now we're sharing a proven solution.

Why the Official Connector Falls Short

Zadarma offers a ready-to-use connector (configured in the control panel under Integrations → Bitrix24). It only works with cloud Bitrix24 and demands strict alignment: the internal Zadarma number must match the employee's login in Bitrix24. For companies with ten managers and two numbers, it's tolerable—but for international scenarios, it's a dead end.

Our direct API integration provides twice the flexibility and reduces telephony costs by up to 25%. Actual savings average $800–$1,500 per month for medium-sized companies. Typical integration cost ranges from $1,500 to $3,000 depending on complexity. Processing over 10,000 calls per month for medium-sized clients.

Comparison: Direct integration is 2.5 times more efficient in call routing than the standard module.

How to Set Up Direct Integration via Zadarma Webhooks

Follow these steps to implement the integration:

1. Configure Webhook URL – In the Zadarma control panel, go to PBX Settings → Notifications → Webhooks URL and provide your handler address. For details, refer to the official API documentation.

2. Implement Webhook Handler – Create a script that receives notifications. Zadarma supports these notification types: NOTIFY_CALL, NOTIFY_ANSWER, NOTIFY_END, NOTIFY_RECORD, NOTIFY_OUT_START, NOTIFY_OUT_END.

3. Verify Signature – Each webhook includes a sign parameter. Verify it using your API key and secret. Example PHP code:

$data = $_POST; ksort($data); $sign = strtoupper(md5($apiKey . implode('', $data) . $apiSecret)); if ($sign !== $data['sign']) { http_response_code(403); exit; } 

4. Create CRM Objects – After verification, use Bitrix24 REST API to create leads, activities, or deals based on call events. For example, a missed call from an unknown number creates a lead; if the contact exists, add an activity.

5. Map Multiple Numbers – Use the called_did field to identify the number dialed. Example mapping:

$didToLine = [ '+442071234567' => '201', // London '+74951234567' => '200', // Moscow '+380441234567' => '202', // Kyiv ]; 

Then assign the line to a responsible manager. Check online status via the Bitrix24 REST API user.online.getlist with 60-second caching.

Handling Multiple Zadarma Numbers

A client may have several virtual numbers in different countries. The webhook field called_did contains the number that received the call. Use it to map the line. Example mapping for an international company:

$didToLine = [ '+442071234567' => '201', // London '+74951234567' => '200', // Moscow '+380441234567' => '202', // Kyiv ]; 

Then the line is matched to a responsible manager. If the manager is offline, the call is forwarded to the duty person. We check online status via Bitrix24 REST API user.online.getlist with 60-second caching. Our integration handles all your SIP lines for Zadarma virtual PBX Bitrix24 setup. Need a reliable Zadarma Bitrix24 setup? Our solution provides it.

Case Study: Export Company with Numbers in 4 Countries

A trading company—our client—had customers in Russia, Germany, Poland, and Kazakhstan. Each country had a local Zadarma number. The goal: all calls into a single Bitrix24 with correct attribution. A German customer calls the German number, the call goes to the manager responsible for Germany. If the manager is busy, the call routes to the duty person.

We developed a mapping table DID → LINE_NUMBER → USER_ID, a webhook-based call handler, and online status monitoring. Setup took 5 business days turnkey. After implementation, the client doesn't lose a single call, and processing time dropped by 30%. 90% of calls are handled within 3 seconds.

What's Included in the Integration

• Analysis of current telephony setup and routing requirements
• Development and configuration of the webhook handler on your server
• Integration with Bitrix24: creation of events, leads, activities
• Mapping of numbers and responsible parties (including SIP lines)
• Testing all scenarios (inbound, outbound, forwarding)
• Support documentation and employee instructions
• 30-day guarantee on the setup

Timeline and How to Order

Integration takes 4 to 6 business days. Pricing is individual—based on number of lines, routing complexity, and need for additional integrations (e.g., 1C or CRM analytics). Contact us to discuss your project and get a preliminary estimate.

With 10+ years of Bitrix24 and Zadarma experience, we've completed dozens of integrations for companies of all sizes. Request a consultation—we'll set up telephony with effective call routing Bitrix24 integration.