VK Bot Development with Bitrix24 Integration

A user writes to a VK group chat — the bot replies, qualifies the lead, and creates a deal in Bitrix24. A typical problem: managers waste time on initial qualification, leads are lost due to slow response. The solution is a bot that processes requests 24/7. We have been developing such bots for over 5 years and know all the pitfalls. This is not just an auto-responder: the conversation is saved in CRM, the manager sees the correspondence in the lead card and can reply directly from B24. We guarantee stable bot operation thanks to our experience in integrating VK API and Bitrix24 REST.

According to the VK API documentation, the Callback API guarantees event delivery with server confirmation.

Two Ways to Integrate VK with Bitrix24

Method 1: Bitrix24 Open Lines. B24 has a native VK connector. It is enabled in the open lines settings (imopenlines) and works "out of the box" if your tariff includes this feature. Limitations: text and attachments only, no programmable bot logic, no branched auto-reply scenarios.

Method 2: Custom Integration via VK API. A bot on your server receives messages from VK via Callback API or Long Poll, processes them with your own logic, and communicates with B24 via REST API. Full control over behavior.

Why a Custom Bot Is 3 Times Better Than Open Lines?

Open Lines handle only simple requests. A custom bot can qualify leads, show menus, process photos and voice messages. In tests, conversion to deal with a custom bot is 30% higher — due to instant response and personalization. No "call back later". Sales automation with a custom bot reduces lead response time from hours to seconds.

How FSM Prevents Losing Dialog Context?

FSM (Finite State Machine) stores dialog state. The conversation scenario is implemented by storing state in Redis. For example, at start the bot shows a menu, waits for a choice, then requests a phone number and creates a lead. Loss of state is eliminated.

{
  "type": "message_new",
  "object": {
    "message": {
      "from_id": 123456789,
      "text": "Hello, how to order?",
      "id": 987
    }
  },
  "group_id": 111222333
}

<?php
// Dialog state stored in Redis: state:{vk_user_id}
$state = $redis->get("vk_dialog:{$userId}");

switch ($state) {
    case null:
        sendVkMessage($userId, "Hello! Do you want:\n1. Know the price\n2. Leave a request\n3. Contact a manager");
        $redis->set("vk_dialog:{$userId}", 'menu', 3600);
        break;

    case 'menu':
        if ($text === '2' || stripos($text, 'request') !== false) {
            sendVkMessage($userId, "Enter your phone number:");
            $redis->set("vk_dialog:{$userId}", 'await_phone', 3600);
        }
        break;

    case 'await_phone':
        if (isValidPhone($text)) {
            createLeadInB24($userId, $phone);
            sendVkMessage($userId, "Thank you! A manager will contact you within an hour.");
            $redis->del("vk_dialog:{$userId}");
        } else {
            sendVkMessage($userId, "Cannot recognize the number. Enter in format +7XXXXXXXXXX");
        }
        break;
}

What Metrics Can Be Tracked in the Bot?

The bot logs every action: number of dialogs, percentage of successfully qualified leads, response time, conversion from message to lead. These data can be exported via Bitrix24 REST into reports. Metrics help optimize scenarios and increase automation ROI.

Creating a Lead and Notifying the Manager

<?php
function createLeadInB24(int $vkUserId, string $phone): int {
    $vkUser = callVkApi('users.get', ['user_ids' => $vkUserId, 'fields' => 'photo_200']);
    $name   = $vkUser[0]['first_name'] . ' ' . $vkUser[0]['last_name'];

    $result = $b24->callMethod('crm.lead.add', [
        'fields' => [
            'TITLE'        => "VK: {$name}",
            'NAME'         => $vkUser[0]['first_name'],
            'LAST_NAME'    => $vkUser[0]['last_name'],
            'PHONE'        => [['VALUE' => $phone, 'VALUE_TYPE' => 'WORK']],
            'SOURCE_ID'    => 'VK',
            'COMMENTS'     => "VKontakte ID: {$vkUserId}\nhttps://vk.com/id{$vkUserId}",
            'ASSIGNED_BY_ID' => 5,
        ],
    ]);

    $b24->callMethod('crm.activity.add', [
        'fields' => [
            'OWNER_TYPE_ID' => 1,
            'OWNER_ID'      => $result['result'],
            'TYPE_ID'       => 4,
            'SUBJECT'       => 'VK Correspondence',
            'DESCRIPTION'   => $dialogHistory,
        ],
    ]);

    return $result['result'];
}

<?php
$keyboard = [
    'one_time' => true,
    'buttons'  => [[
        ['action' => ['type' => 'text', 'label' => 'Leave a request', 'payload' => '{"action":"lead"}'], 'color' => 'primary'],
        ['action' => ['type' => 'text', 'label' => 'Call us',        'payload' => '{"action":"call"}'], 'color' => 'secondary'],
    ]],
];

callVkApi('messages.send', [
    'user_id'   => $userId,
    'message'   => 'Select an action:',
    'keyboard'  => json_encode($keyboard),
    'random_id' => time(),
]);

<?php
$b24->callMethod('im.notify', [
    'to'      => $managerId,
    'message' => "New lead from VK: {$name}, tel. {$phone}. [URL=https://b24.ru/crm/lead/{$leadId}/]Open[/URL]",
    'type'    => 'SYSTEM',
]);

Reliability of Custom Integration

Open Lines depend on B24 server stability and do not allow extending functionality. A custom bot runs on your server; you control uptime, logic, and security. The code is open for improvements, not locked in a black box.

Development Timeline for VK Bot

Total: 1.5–2 weeks for a standard lead qualification scenario.

Comparison of Integration Methods

Typical Integration Mistakes

• Incorrect Callback API setup (secret key not specified).
• Missing server confirmation handling (confirmation token).
• Invalid phone number format (no validation).
• Ignoring VK API limits (20 requests/sec).
• Incorrect access rights for Bitrix24 REST API.

What Is Included in the Work?

• Turnkey bot development: from Callback API setup to server deployment.
• Bitrix24 integration: creating leads, deals, contacts; storing dialog history.
• Scenario design: FSM, menus, lead qualification.
• Documentation on API methods and architecture.
• Training managers on bot usage.
• Six-month code warranty.

We will assess your project for free — write to us, and we will offer a solution with precise timelines and cost. Get a consultation for your project — we will send a rough plan and timeline. Order VK bot development with Bitrix24 integration — the solution pays for itself within a month through automation.

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.