Bitrix24-Kaiten Integration: Task and Card Synchronization

Bitrix24-Kaiten Integration Development

We often encounter this situation: managers work in Bitrix24, developers work in Kaiten, and tasks live their own lives. Statuses diverge, comments are duplicated, deadlines are missed. The result is lost leads and unnecessary meetings. One fintech company lost up to 15% of leads because managers forgot to update the status in Kaiten after closing a deal. After integration, task transfer time dropped from 2 hours to 2 minutes. Our experience shows that without synchronization between CRM and project management system, any Kanban tool loses its meaning.

Why Synchronization Between Bitrix24 and Kaiten Is a Problem

Kaiten is a Russian counterpart of Jira, popular after Western vendors left. It provides a REST API and webhooks, but setting up two-way synchronization requires deep understanding of both products. Typical mistakes:

• Cyclic update: task changed in Bitrix24 → updated in Kaiten → webhook sent the change back, causing an infinite loop. Solution — lock via SYNC_LOCK in the mapping table.
• Data loss at scale: with 1000+ tasks per day, synchronization without queues leads to race conditions. We use locks and agents.
• Different terminology: in Kaiten, statuses are board columns (column_id), while in Bitrix24 they are numeric STATUS. Mapping is stored in b_option and configured per specific board.

How We Implement the Integration

We develop the solution on PHP 8.1+ using Bitrix D7 ORM. The core is the KaitenApiClient class that encapsulates HTTP requests to Kaiten (key endpoints in the table below).

For storing relations, we use our own table b_local_kaiten_task_map with fields BITRIX_TASK_ID, KAITEN_CARD_ID and SYNC_LOCK for locking.

class KaitenApiClient
{
    private string $baseUrl;
    private string $token;

    public function __construct(string $baseUrl, string $token)
    {
        $this->baseUrl = rtrim($baseUrl, '/');
        $this->token   = $token;
    }

    public function createCard(array $data): array
    {
        return $this->request('POST', '/api/latest/cards', $data);
    }

    public function updateCard(int $cardId, array $data): array
    {
        return $this->request('PATCH', "/api/latest/cards/{$cardId}", $data);
    }

    public function addComment(int $cardId, string $text): array
    {
        return $this->request('POST', "/api/latest/cards/{$cardId}/comments", ['text' => $text]);
    }

    private function request(string $method, string $path, array $data = []): array
    {
        $ch = curl_init($this->baseUrl . $path);
        curl_setopt_array($ch, [
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_CUSTOMREQUEST  => $method,
            CURLOPT_HTTPHEADER     => [
                'Authorization: Bearer ' . $this->token,
                'Content-Type: application/json',
            ],
            CURLOPT_POSTFIELDS     => $method !== 'GET' ? json_encode($data) : null,
        ]);
        $response = curl_exec($ch);
        $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
        curl_close($ch);

        if ($httpCode >= 400) {
            throw new \RuntimeException("Kaiten API error {$httpCode}: {$response}");
        }

        return json_decode($response, true) ?? [];
    }
}

What Is Included in the Work

• Analysis and design: describe synchronization scenarios (tasks, statuses, comments, files), agree on column mapping.
• Component development: Kaiten API client, Bitrix24 event handlers (OnTaskUpdate, OnCrmDealUpdate), webhook handler.
• Testing: verification on a test circuit with simulated load up to 500 tasks per hour.
• Deployment and training: configure on production, provide API endpoint documentation and administrator instructions.
• Warranty support: 1 month after delivery — bug fixes free of charge. Compliance certificate and solution license are provided.

Two-Way Synchronization: Cards and Webhook

When a task changes in Bitrix24 (event OnTaskUpdate), a handler updates the Kaiten card via PATCH /api/latest/cards/{id}. To avoid looping, we use SYNC_LOCK:

public static function onTaskUpdate(int $taskId, array $arFields): void
{
    $map = KaitenTaskMapTable::getByBitrixId($taskId);
    if (!$map || $map['SYNC_LOCK'] !== null) {
        return;
    }

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

    try {
        $client = self::getClient();
        $kaitenData = [];

        if (isset($arFields['TITLE'])) {
            $kaitenData['title'] = $arFields['TITLE'];  
        }
        if (isset($arFields['DESCRIPTION'])) {
            $kaitenData['description'] = strip_tags($arFields['DESCRIPTION']);
        }
        if (isset($arFields['DEADLINE'])) {
            $kaitenData['due_date'] = date('Y-m-d', strtotime($arFields['DEADLINE']));
        }
        if (isset($arFields['STATUS'])) {
            $columnId = StatusMapper::b24StatusToKaitenColumn($arFields['STATUS']);
            $kaitenData['column_id'] = $columnId;
        }

        if (!empty($kaitenData)) {
            $client->updateCard($map['KAITEN_CARD_ID'], $kaitenData);
        }

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

Webhook from Kaiten to Bitrix24 receives a JSON with the card.updated event:

{
  "event": "card.updated",
  "data": {
    "id": 12345,
    "title": "New task title",
    "column_id": 678,
    "assignees": [{"id": 99, "username": "[email protected]"}]
  }
}

The handler verifies the HMAC signature and, if the lock is not active, updates the task status in Bitrix24 via CTasks::Update.

Column Mapping and Auto-Creation from CRM

Example mapping for the "Development" board:

A useful case is automatic Kaiten card creation when a CRM deal moves to the "Development" stage. Implemented via OnCrmDealUpdate:

if ($arFields['STAGE_ID'] === 'DEVELOPMENT') {
    $client  = KaitenApiClientFactory::create();
    $card    = $client->createCard([
        'title'    => 'Deal #' . $dealId . ': ' . $arFields['TITLE'],
        'board_id' => KAITEN_DEV_BOARD_ID,
        'column_id' => KAITEN_BACKLOG_COLUMN_ID,
        'description' => $arFields['COMMENTS'],
    ]);
    \CCrmDeal::Update($dealId, ['UF_KAITEN_CARD_ID' => $card['id']], false);
}

Our approach saves up to 2 times the time compared to manual synchronization. Companies with integration experience confirm: automation eliminates human errors and speeds up task transfer between departments.

Development Timeline

Cost is calculated individually. Contact us — we will evaluate your project for free. Get a consultation on integration architecture and implementation timeline.

Over 5 years of experience in developing integrations for Bitrix24. Certified solutions, quality guarantee.

How to Verify Synchronization Correctness?

We recommend setting up monitoring: log each API call and check for errors. Use an agent that compares the number of tasks in both systems once an hour. If a discrepancy is found, an administrator is notified. This helps quickly identify failures and maintain data accuracy.

What Automation Brings Instead of Manual Transfer?

Manual task copying takes on average 10–15 minutes per task. With 20 tasks per day, that's 3–4 hours of work. Automation reduces this to seconds and eliminates typos and omissions. Moreover, statuses in Kaiten change automatically when a deal changes — the manager doesn't need to enter another interface.

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.