Bitrix24 Webhook Development: Setup, Processing, Integration

A deal moves to "Paid" status — within seconds, an invoice appears in the accounting system, a delivery request is created in the logistics platform, and an SMS goes to the client. Without webhooks, this would be manual work or a polling loop checking changes every minute. Webhooks are push notifications from Bitrix24 about events in the system. We, as developers with 5+ years of experience, ensure reliable implementation of such scenarios.

On average, a portal receives 50-100 events per minute at peak. Real-time processing of each is critical for business processes. Without a properly configured webhook system, companies face order delivery delays, duplicate invoices, and data loss. We solve this problem using proven architectural patterns and the Bitrix24 stack.

What Problems Do Webhooks Solve?

Webhooks automate reactions to events without human involvement. Main business tasks:

• Sync CRM deals with accounting systems (1C, ERP)
• Automatic order creation in logistics (CDEK, Russian Post)
• Sending notifications to clients (SMS, email, Telegram)
• Updating data in analytical dashboards

From practice: on one project, integration with 1C required processing 200 events per minute. We implemented async processing via RabbitMQ and achieved processing time under 1 second. That's 10 times faster than periodic polling, which had a 30-60 second delay.

Inbound vs Outbound Webhooks: What's the Difference?

Bitrix24 has two types of webhooks that are often confused:

Outbound webhooks are configured via the interface or REST API event.bind. Inbound webhooks are URLs with an embedded token that can be used to call Bitrix24 REST API without a full OAuth flow. The choice depends on the scenario: outbound for reacting to events, inbound for external management from third-party systems.

How to Set Up a Webhook Handler?

Step-by-step process for setting up a handler:

1. Register a subscription via event.bind specifying the event and handler URL.
2. Implement an endpoint that accepts POST requests from Bitrix24.
3. Verify the signature (check the authorization token and IP address).
4. Pass data to an async handler (via a queue).
5. Return HTTP 200 OK as quickly as possible.

Example subscription to deal stage change:

$client->call('event.bind', [
    'event'     => 'ONCRMDEALSTAGEID',
    'handler'   => 'https://integration.mycompany.ru/b24/webhook/deal-stage',
    'auth_type' => 1,
    'options'   => [
        'add_auth' => 'Y',
    ],
]);

The full list of available CRM events includes over 150 names: ONCRMDEALCHANGE, ONCRMCONTACTCHANGE, ONCRMLEADCHANGE, and others. The complete list is available in the official REST API documentation.

Why Is Idempotence Important?

The webhook handler must respond quickly (up to 5 seconds) and process data asynchronously. If the response is slow or not 200 OK, Bitrix24 retries the request with exponential backoff. Without idempotence, repeated processing creates duplicates: e.g., double invoices or two delivery orders. Idempotence ensures that repeated calls do not cause side effects.

public function handleDealStage(Request $request): Response
{
    if (!$this->verifySignature($request)) {
        return response('Unauthorized', 401);
    }

    DealStageChangedJob::dispatch($request->all())->onQueue('b24-events');

    return response('OK', 200);
}

class DealStageChangedJob implements ShouldQueue {
    public function handle(): void {
        $dealId  = $this->data['data']['FIELDS_AFTER']['ID'];
        $stageId = $this->data['data']['FIELDS_AFTER']['STAGE_ID'];

        // Idempotency check: already processed?
        if ($this->alreadyProcessed($dealId, $this->data['event_id'])) {
            return;
        }

        if ($stageId === 'WON') {
            $this->accountingService->createInvoice($dealId);
            $this->logisticsService->createShipment($dealId);
            $this->smsService->sendPaymentConfirmation($dealId);
        }
    }
}

How to Ensure System Reliability?

Signature Verification

Bitrix24 may pass an authorization token (auth[access_token]). The handler checks that the token belongs to the expected portal. For additional security, we add IP whitelisting — the list of Bitrix24 IPs is published in the official documentation.

Logging and Monitoring

All incoming webhooks are logged to a database table (e.g., vendor_b24_webhook_log):

• reception time
• event type
• request body (with token masking)
• processing status (pending / processed / failed)
• number of attempts

The monitoring dashboard shows: queue of unprocessed events, events with errors, average processing time. When more than 50 unprocessed events accumulate, an alert is sent via email or Telegram to the administrator.

Replay Pattern

If an external system fails (e.g., the accounting system is unavailable), some webhooks may not be processed. The module implements a replay: the administrator selects a date range and event type, and the system re-executes the handler for all events from the log.

What's Included in the Work

When ordering webhook development, you receive:

• Event map: analysis of business processes and mapping to Bitrix24 events
• Handler development (endpoint + async queue)
• Logging and monitoring setup
• Deployment and operations documentation
• Administrator training (1 hour)
• Technical support for 1 month after delivery

Timelines and Cost

Before development, we create an event map: which Bitrix24 event -> which action in the external system. This allows us to estimate the workload and identify potential conflicts.

Typical Mistakes in Webhook Development

• Missing idempotence → data duplication
• Synchronous processing → timeouts and retries
• Ignoring signature verification → vulnerability to fake requests
• Insufficient logging → hard to debug failures

Webhooks are an effective tool for integration, operating in real time without polling. They are comparable to the Webhook pattern.

Contact us for an estimate of your project — we will propose an optimal turnkey solution. 5+ years of experience and over 50 successful integrations guarantee quality. Order webhook development and get a ready solution in 2-3 weeks.

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.