Bitrix24-Яндекс.Трекер integration: full guide

Bitrix24-Яндекс.Трекер integration: we bridge the gap between developers and managers

Typical situation: developers live in Yandex Tracker, while managers handle client deals in Bitrix24. A task is created in Tracker — the manager doesn't see its current status. A status changes in Bitrix24 — the developer learns about it through third parties. Manual transfer eats up hours daily and invites errors. Consider a typical IT company: the development team uses Yandex Tracker for task management, while the sales department works in Bitrix24. When aligning tasks, a disconnect occurs — statuses are not synchronized, information becomes stale within an hour. Our integration eliminates this gap automatically, reducing error probability and speeding up task completion. We've already implemented such solutions for clients across various industries, including companies with hundreds of employees. We offer a turnkey integration — from design to post-launch support. Get in touch to pinpoint your case.

What problems does the integration solve?

Manual task transfer. Employees spend 30–60 minutes daily copying titles and statuses between systems. Our script automates this completely.

Loss of timeliness. Information becomes stale within an hour — the manager sees "In progress" while the task is already closed. Real-time synchronization eliminates the delay.

Status conflict. Bitrix24 has one status model, Tracker has another. A clear mapping is needed, otherwise synchronization causes confusion.

How we do it: stack and architecture

Yandex Tracker API: key methods

Tracker provides a REST API with OAuth 2.0 authentication. The organization token is passed in the header of each request. Base URL: https://api.tracker.yandex.net/v3/. Main endpoints:

For webhooks, triggers are used — configured in the Tracker interface at the queue level.

Integration architecture

The integration is bidirectional, so loops must be avoided. The solution: an "update from integration" flag (lock mechanism).

Task mapping table:

class TrackerBitrix24TaskTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string
    {
        return 'b_local_tracker_task_map';
    }

    public static function getMap(): array
    {
        return [
            new IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new IntegerField('BITRIX_TASK_ID'),   // ID задачи в Битрикс24
            new StringField('TRACKER_ISSUE_KEY'), // Например, "DEV-123"
            new StringField('SYNC_DIRECTION'),    // B24_TO_TRACKER | TRACKER_TO_B24 | BIDIRECTIONAL
            new DatetimeField('LAST_SYNC_AT'),
            new StringField('SYNC_LOCK'),         // NULL или UUID текущей операции
        ];
    }
}

Synchronization Bitrix24 → Yandex Tracker

We use the OnTaskUpdate event from the tasks module:

// /local/modules/local.trackerintegration/lib/handlers/taskhandler.php

namespace Local\TrackerIntegration\Handlers;

class TaskHandler
{
    public static function onTaskUpdate(int $taskId, array $arFields): void
    {
        $map = TrackerBitrix24TaskTable::getByBitrixId($taskId);
        if (!$map || $map['SYNC_LOCK'] !== null) {
            return; // Нет маппинга или уже синхронизируем
        }

        // Ставим лок
        TrackerBitrix24TaskTable::update($map['ID'], ['SYNC_LOCK' => uniqid()]);

        try {
            $client = new TrackerApiClient();

            $payload = [];
            if (isset($arFields['TITLE'])) {
                $payload['summary'] = $arFields['TITLE'];
            }
            if (isset($arFields['DESCRIPTION'])) {
                $payload['description'] = $arFields['DESCRIPTION'];
            }
            if (isset($arFields['STATUS'])) {
                // Маппинг статусов Битрикс24 → Трекер
                $trackerStatus = StatusMapper::b24ToTracker($arFields['STATUS']);
                $client->executeTransition($map['TRACKER_ISSUE_KEY'], $trackerStatus);
            }

            if (!empty($payload)) {
                $client->updateIssue($map['TRACKER_ISSUE_KEY'], $payload);
            }

            TrackerBitrix24TaskTable::update($map['ID'], [
                'SYNC_LOCK'    => null,
                'LAST_SYNC_AT' => new \Bitrix\Main\Type\DateTime(),
            ]);
        } catch (\Exception $e) {
            TrackerBitrix24TaskTable::update($map['ID'], ['SYNC_LOCK' => null]);
            \Bitrix\Main\Diag\Debug::addToLog('TrackerSync error: ' . $e->getMessage());
        }
    }
}

Registering the handler:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'tasks', 'OnTaskUpdate', [\Local\TrackerIntegration\Handlers\TaskHandler::class, 'onTaskUpdate']
);

Webhook from Yandex Tracker → Bitrix24

The webhook handler is a controller accessible via a public URL. In Tracker, a trigger is configured: "When status changes → POST to https://company.bitrix24.ru/local/tracker/webhook/".

// /local/tracker/webhook/index.php

$rawBody = file_get_contents('php://input');
$event   = json_decode($rawBody, true);

// Проверяем secret-заголовок (задаётся в настройках триггера Трекера)
$secret = $_SERVER['HTTP_X_TRACKER_SECRET'] ?? '';
if ($secret !== TRACKER_WEBHOOK_SECRET) {
    http_response_code(403);
    exit;
}

$issueKey = $event['issue']['key'] ?? null;
$newStatus = $event['updatedAttributes']['status']['to']['key'] ?? null;

if (!$issueKey || !$newStatus) {
    http_response_code(200);
    exit;
}

$map = TrackerBitrix24TaskTable::getByTrackerKey($issueKey);
if (!$map || $map['SYNC_LOCK'] !== null) {
    http_response_code(200);
    exit;
}

TrackerBitrix24TaskTable::update($map['ID'], ['SYNC_LOCK' => uniqid()]);

$b24Status = StatusMapper::trackerToB24($newStatus);
$task = new \CTasks();
$task->Update($map['BITRIX_TASK_ID'], ['STATUS' => $b24Status], false);

TrackerBitrix24TaskTable::update($map['ID'], ['SYNC_LOCK' => null, 'LAST_SYNC_AT' => new \Bitrix\Main\Type\DateTime()]);

http_response_code(200);
echo json_encode(['ok' => true]);

Status mapping

Statuses in the two systems don't match — a correspondence table is needed:

The mapping is stored in a configuration file or in b_option.

How to avoid loops in bidirectional synchronization?

In bidirectional sync, a lock mechanism is critical to prevent endless loops. When the OnTaskUpdate handler receives an event, it checks the SYNC_LOCK field in the mapping table. If SYNC_LOCK is not null, it means the change is already being processed by the other side — the handler exits without execution. This approach works faster and more reliably than timestamp checks because it eliminates race conditions during parallel requests. According to the official Bitrix24 documentation, the OnTaskUpdate event is triggered on any task change, so without a lock mechanism, synchronization would quickly loop. Our implementation guarantees that each update is processed exactly once.

Creating a task in Tracker from a Bitrix24 deal

An additional scenario: when a deal of a certain type is created, automatically create a task in Tracker. Implemented via a business process or through the onCrmDealAdd event handler:

public static function onCrmDealAdd(int $dealId, array $arFields): void
{
    if ($arFields['TYPE_ID'] !== 'DEVELOPMENT') {
        return;
    }

    $client = new TrackerApiClient();
    $issue = $client->createIssue([
        'queue'    => 'DEV',
        'summary'  => 'CRM Deal #' . $dealId . ': ' . $arFields['TITLE'],
        'type'     => 'task',
        'assignee' => UserMapper::b24ToTracker($arFields['ASSIGNED_BY_ID']),
        'tags'     => ['crm', 'auto-created'],
    ]);

    // Save mapping
    TrackerBitrix24TaskTable::add([
        'BITRIX_TASK_ID'   => 0, // No task, only deal
        'TRACKER_ISSUE_KEY' => $issue['key'],
        'SYNC_DIRECTION'   => 'BIDIRECTIONAL',
    ]);

    // Write the task key to the deal custom field
    \CCrmDeal::Update($dealId, ['UF_TRACKER_ISSUE_KEY' => $issue['key']], false);
}

Process of work

1. Analysis — we study current business processes, identify entities to synchronize.
2. Design — we design architecture, mapping table, lock mechanism.
3. Implementation — we write code in PHP 8.1+, using Bitrix24 ORM and Tracker REST API.
4. Testing — we check synchronization on test tasks, simulate conflicts.
5. Deployment — we deploy to production, set up monitoring.
6. Support — after launch, we provide warranty support and documentation.

Estimated timelines

Cost is calculated individually — depends on complexity and volume of work. To get a precise estimate, contact us.

Why choose our integration?

Integration via REST API and webhooks works stably without loading the server. We use tagged cache and agents for background tasks. Our engineers have over 8 years of experience in Bitrix24 development. Automatic synchronization completes in seconds, whereas manual transfer takes up to 30–60 minutes daily — our integration speeds up work by 50 times. We guarantee correct operation after launch and provide documented solutions.

What's included in the work

• Documentation for setup and operation.
• Access to the code repository.
• Employee training (1 hour online).
• Support for 30 days after launch.
• Option for modifications under new scenarios.

Order integration — our engineers will analyze your processes and offer the optimal solution. Get a consultation right now by describing your task.

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.