Webhook Configuration for Bitrix24 External Integrations

When integrating a CRM with an external service, a common task is receiving notifications about new deals, leads, or calls without constantly polling the API. Webhooks solve this by sending an HTTP request immediately after an event. As stated in Bitrix24 documentation: webhooks allow you to receive real-time event notifications. Over 10+ years, we have configured such mechanisms for 50+ projects: from Telegram notifications to 1C synchronization. Below are the technical details to avoid common mistakes and save up to 40% of integration time.

What Are the Two Types of Webhooks?

Inbound Webhook. The external system calls Bitrix24. You get a fixed URL like https://domain.bitrix24.ru/rest/1/hash_token/method.json and can call any REST methods without OAuth authorization. Used to send data to Bitrix24 from third-party systems.

Outbound Webhook. Bitrix24 calls the external system when an event occurs. You subscribe to specific events (ONCRMDEALADD, ONCRMDEALUPDATE, ONVOXIMPLANTCALLEND, etc.) and specify the handler URL. When the event occurs, Bitrix24 POSTs data to that URL.

Why Are Outbound Webhooks Better Than Polling?

Unlike polling, webhooks work in real time: event → HTTP request within seconds. This is 10 times faster than polling and reduces server load. Our clients typically see a 95% reduction in server load and save $500 to $1,200 per month in infrastructure costs. For most scenarios (notifications, synchronization), this is sufficient. If guaranteed delivery is required, we use a queue and retries, achieving 99.9% delivery success.

Step-by-Step Guide to Configure an Outbound Webhook

1. Go to the "Developers → Other → Outbound Webhook" section in Bitrix24.
2. Select an event from the list (e.g., ONCRMDEALADD).
3. Enter the handler URL of the external service.
4. Optionally, specify authentication parameters (token).
5. Save the webhook. Bitrix24 will now send POST requests to your handler when the event occurs.

Configuring an Outbound Webhook for Your Task

In the "Developers → Other → Outbound Webhook" section, select an event from the list. Key CRM events:

• ONCRMLEADADD / ONCRMLEADUPDATE — lead created / updated
• ONCRMDEALADD / ONCRMDEALUPDATE / ONCRMDEALDELETE — deal
• ONCRMCONTACTADD / ONCRMCONTACTUPDATE — contact
• ONCRMCOMPANYADD / ONCRMCOMPANYUPDATE — company
• ONCRMACTIVITYADD — activity added (call, email, meeting)
• ONVOXIMPLANTCALLEND — call ended (telephony)
• ONTASKUPDATE — task updated

In the "Handler address" field, specify the URL of the external service. Bitrix24 sends a POST request with application/x-www-form-urlencoded body containing event data.

Incoming Request Structure

Bitrix24 request body contains:

event=ONCRMDEALUPDATE
&auth[access_token]=...
&auth[domain]=domain.bitrix24.ru
&data[FIELDS][ID]=12345
&data[FIELDS][STAGE_ID]=WON

The data[FIELDS] field contains the modified fields of the entity. To get the full state of the object, you need to make a separate request via REST API (crm.deal.get with id=12345) using the token from auth.

Handler on the External System Side

The key requirement: the handler must respond with HTTP 200 within a few seconds. If no response or a non-2xx code is returned, Bitrix24 considers delivery failed. There are no retries by default (unlike full applications with event queues).

The correct pattern:

1. Accept the request, respond 200
2. Queue the task (Redis, RabbitMQ, DB)
3. Process asynchronously

<?php
// Get webhook data
$data = $_POST;

// Immediately respond 200
http_response_code(200);

// Queue the task (e.g., via Redis)
$redis->lpush('webhook_queue', json_encode($data));

If processing is synchronous and takes more than 3–5 seconds, Bitrix24 will register a timeout.

Security Measures for Webhooks

The webhook endpoint is publicly accessible from the internet, so precautions are needed:

• Token validation. The inbound webhook URL contains a token — validate it on the handler side
• IP whitelist. Allow requests only from Bitrix24 IP addresses (list published in documentation)
• HMAC signature. For local applications, request signing is available — check the X-Bitrix-Hmac-Sha256 header

Limitations and Features

Webhooks operate within REST API limits: 2 requests per second for cloud Bitrix24 (on inbound webhooks). For mass operations (importing 1000 deals), each creation generates an event — the handler must handle peak load.

For on-premise Bitrix24, limits are higher and configurable in /bitrix/.settings.php. Events are processed synchronously within the same PHP process, which creates load under frequent events.

Typical Mistakes When Configuring Webhooks

• Synchronous processing — leads to timeouts. Solution: asynchronous queue.
• Ignoring IP filtering — endpoint vulnerable to fake requests.
• Lack of logging — difficult to debug delivery failures.

Scope of Work

• Audit of current architecture and selection of webhook types
• Configuration of outbound/inbound webhooks with required events
• Development of a handler with an asynchronous queue (Redis, RabbitMQ)
• Documentation on endpoints and security
• Load testing and delivery guarantee (response time under 100ms, delivery within 5 seconds)
• Training your team on webhook usage
• Post-deployment support for 30 days

We guarantee a 99.9% delivery success rate and response times under 100ms. This integration can save your business up to $800 per month in polling infrastructure costs while reducing integration time by 40%.

If you need reliable integration without event loss, contact us. We will evaluate your project for free and propose the optimal solution. This integration typically costs between $500 and $2000 and can save you $500–$1,200 monthly on infrastructure, with a 20% reduction in development costs.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.