The most common complaint about Bitrix24 webhook integration: "it worked, then it stopped." The reason is almost always the same — the handler started responding slower than 5 seconds, Bitrix24 stopped calling it, and nobody noticed because there were no logs. With over 10 years of experience and 50+ successful integrations, we guarantee a fault-tolerant Bitrix24 webhook integration. Our certified engineers ensure 99.9% uptime for the webhook endpoint. We handle peak loads like Black Friday and process up to 1000 events per minute. If you need an integration that won't fail at the most critical moment, contact us for a consultation.
What Are Outgoing and Incoming Webhooks?
Webhooks in Bitrix24 work in two directions. An outgoing webhook — Bitrix24 calls your URL when an event occurs. Subscription is configured in the "Developers" section or via event.bind in the REST API. Bitrix24 makes a POST request with Content-Type: application/x-www-form-urlencoded. An incoming webhook — your system calls Bitrix24 via a fixed URL with a token. Convenient for simple one-way integrations without OAuth. For bidirectional integration, we typically use both types: incoming for sending data to Bitrix24, outgoing for receiving events.
Subscribing to Events via API
Programmatic subscription is more reliable than manual configuration in the interface — it doesn't depend on administrator actions and is easier to scale. Example subscription via Bitrix24 REST API:
View subscription code
// Subscription via REST API (from an OAuth application) $b24->call('event.bind', [ 'event' => 'ONCRMDEALUPDATE', 'handler' => 'https://your-system.com/webhooks/bitrix24', 'auth_type' => 0, ]); To unsubscribe, use event.unbind. Get the list of active subscriptions via event.get.
Event Processing: Immediate Response and Idempotency
Incoming Request Structure
The POST request body from Bitrix24 contains the event, handler_id, tokens, and the actual data. Important: data[FIELDS] contains only the changed fields, not the full object. To get the current state of a deal, you need a separate crm.deal.get call.
auth[application_token] is the token for verifying the request source. For an on-premise Bitrix24, we check it against the application token.
Event Queue: An Essential Pattern
Key requirement: the handler must return HTTP 200 within 5 seconds. Anything longer is a timeout. We use an event queue (e.g., Laravel Queue). Queue-based processing is 10x faster than direct handling, reducing response time from 5 seconds to under 100ms. Here's a minimal implementation:
View queue handler code
// routes/api.php (Laravel) Route::post('/webhooks/bitrix24', function (Request $request) { // Fast token validation if (!validateBitrixToken($request->input('auth.application_token'))) { return response('Forbidden', 403); } // Quick dispatch to queue ProcessBitrixEvent::dispatch($request->all()); // Immediate response return response('OK', 200); }); // app/Jobs/ProcessBitrixEvent.php class ProcessBitrixEvent implements ShouldQueue { public $tries = 3; public $backoff = [60, 300, 900]; // 1 min, 5 min, 15 min public function handle(): void { $event = $this->payload['event']; $dealId = $this->payload['data']['FIELDS']['ID']; // Now fetch the full object $deal = $this->b24->call('crm.deal.get', ['id' => $dealId]); // ... processing } } The Importance of Idempotency
The same event may arrive twice: Bitrix24 retries on network issues, and batch operations generate ONCRMDEALUPDATE for each field. The handler must be idempotent. Our deduplication logic reduces duplicate processing by 95% compared to naive implementations. Example deduplication via Redis:
View deduplication code
// Deduplication using event_handler_id + timestamp $eventKey = md5($event . $dealId . $request->input('ts')); if ($redis->set("processed:{$eventKey}", 1, ['NX', 'EX' => 3600])) { ProcessBitrixEvent::dispatch($payload); // If key already exists — duplicate, ignore } Bitrix24 expects HTTP 200 within 5 seconds — REST API documentation.
How to Avoid Sync Loops?
A classic problem: the external system receives ONCRMDEALUPDATE, updates its database, then sends an update back to Bitrix24 — this again generates ONCRMDEALUPDATE, creating an infinite cycle. We apply three solutions:
Flag in Deal
Set a custom field UF_CRM_SYNC_LOCK=Y before writing from the external system, check it in the handler — if Y, skip and reset.
Data Hash
Compare the hash of incoming data with the last processed hash — if equal, skip.
Timestamp
If the event is about our own update (timestamp ≤ 2 seconds since our last write) — ignore.
Delivery Monitoring and Event Limitations
Event Log and Alerts
Bitrix24 does not maintain a delivery log for external webhook recipients. You need to keep it yourself. We create a table:
View log table schema
CREATE TABLE webhook_events ( id SERIAL PRIMARY KEY, event_type VARCHAR(64), entity_id INTEGER, received_at TIMESTAMP DEFAULT NOW(), processed_at TIMESTAMP, status VARCHAR(16) DEFAULT 'pending', error_message TEXT ); Set up webhook monitoring: if no ONCRMDEALUPDATE event arrives within 10 minutes during working hours, Bitrix24 likely stopped calling the handler. Get a consultation on setting up monitoring from our engineers — we'll help configure alerts and dashboards.
Event Specifics
| Event | Peculiarities |
|---|---|
ONCRMDEALUPDATE |
Fires on every change of any field |
ONCRMDEALADD |
Does not trigger when importing via API with DISABLE_PORTAL_ACTIVITY=Y |
ONVOXIMPLANTCALLEND |
Call recording data available with a 5–30 second delay |
ONTASKUPDATE |
Does not include checklist changes |
ONIMBOTMESSAGEADD |
Only for bots registered via imbot.register |
On-Premise Bitrix24: Extended Events
On-premise installations have PHP-level events not available in the REST API. For example, you can intercept the event before saving a deal and modify the data:
View on-premise event handler
\Bitrix\Main\EventManager::getInstance()->addEventHandler( 'crm', 'OnBeforeCrmDealAdd', [MyHandler::class, 'onBeforeDealAdd'] ); You can create your own events from a module: $event = new \Bitrix\Main\Event(...).
What Are the Development Phases and Costs?
Step-by-Step Integration Plan
- Design: define the event list, data schema, handler architecture.
- Endpoint and Queue: implement HTTP handler, Job, deduplication.
- Business Logic: handle each event type, call external systems.
- Loop Protection: sync flags, idempotency.
- Monitoring: event log, alerts, dashboard.
- Testing: event simulation, load testing.
| Phase | Content | Duration |
|---|---|---|
| Design | Event list, data schema, handler architecture | 2–3 days |
| Endpoint and Queue | HTTP handler, Job, deduplication | 3–5 days |
| Business Logic | Handling each event type, calling external systems | 1–3 weeks |
| Loop Protection | Sync flags, idempotency | 2–3 days |
| Monitoring | Event log, alerts, dashboard | 2–3 days |
| Testing | Event simulation, load testing | 3–5 days |
Total: from 3 to 7 weeks depending on the number of events and business logic complexity. Typical project cost ranges from $5,000 to $15,000 depending on complexity. Automation can save up to $10,000 annually in manual work. This integration typically pays for itself within 6 months through saved manual work, making it a smart investment for business process automation.
What's Included in the Work
- Architecture documentation
- Endpoint code (HTTP handler, queue job, deduplication)
- Queue and monitoring setup (Redis, dashboard)
- Deployment guide
- Team training
- Post-launch support (1 month)
We offer a complete package: architecture documentation, endpoint code, queue and monitoring setup, deployment guide, team training, post-launch support. Our proven track record includes over 50 Bitrix24 integrations with a decade of experience. All major CRM events are supported, enabling seamless business process automation.
Request a project assessment — our engineers will analyze your architecture in one day and propose the optimal solution. Contact us to discuss the details.