Turnkey Notification Bot for Bitrix24 Development

Managers often miss leads because email notifications land in spam, and overdue tasks come as a surprise. A notification bot for Bitrix24 solves these issues—messages arrive directly in the employee's chat, and quick-action buttons let them accept a lead or postpone a call in one tap. By integrating with Bitrix24 REST API and event model, the bot responds to changes in CRM, tasks, and external systems. We guarantee delivery of every message using a Redis queue—no event is lost, even under peak loads. With over 5 years of experience and 50+ successful bot deployments, we ensure reliable performance.

Why a notification bot outperforms standard email

Bitrix24 email notifications often end up in spam or get lost. A bot sends messages directly to the employee's chat—open rates reach 95%. Quick-action buttons let users complete a task without navigating elsewhere: a manager can accept a lead or postpone a call with one tap. Additionally, the bot delivers notifications to the mobile app, and group alerts can be sent to shared chats.

Technical implementation: registration, sending, and events

Registering the bot

The bot is registered via REST API with a single imbot.register call:

POST /rest/imbot.register
{
  "NAME": "Notifications",
  "CODE": "notify_bot",
  "TYPE": "S",  // S = System, not shown in contacts
  "COLOR": "GREEN",
  "PROPERTIES": {
    "OPENLINE": "N"
  }
}

After registration, Bitrix24 returns a BOT_ID. This ID is used to send messages from the bot.

Sending notifications

Messages are sent via imbot.message.add. The example below shows a formatted message with buttons:

$b24->callMethod('imbot.message.add', [
    'BOT_ID'    => $botId,
    'DIALOG_ID' => 'u' . $userId,
    'MESSAGE'   => '[b]New lead:[/b] ' . $leadTitle,
    'ATTACH'    => [
        [
            'TITLE'       => $leadTitle,
            'DESCRIPTION' => "Phone: {$phone}\nSource: {$source}",
            'COLOR'       => '#ff6600',
            'LINK'        => $crmUrl,
        ],
    ],
    'KEYBOARD'  => [
        'BUTTONS' => [[
            ['TEXT' => 'Open in CRM', 'LINK' => $crmUrl, 'BG_COLOR' => '#2fc6f6'],
            ['TEXT' => 'Take to work', 'COMMAND' => 'take_lead', 'COMMAND_PARAMS' => $leadId],
        ]],
    ],
]);

ATTACH creates an info card, KEYBOARD adds buttons. When a button with COMMAND is pressed, Bitrix24 fires the ONIMBOTMESSAGEADD event—the bot processes it as an action.

Command handling

When a button with COMMAND is clicked, Bitrix24 sends the ONIMBOTMESSAGEADD event. The bot receives it, parses the command, and executes the corresponding action: accepting a lead in CRM, creating a task, or forwarding the notification. The entire process takes milliseconds.

Event sources

CRM and tasks

We register handlers on onCrmLeadAdd, onCrmDealUpdate, onTaskUpdate via event.bind. When a deal moves to "Won" stage—the bot notifies the manager and supervisor with the amount and link. For tasks, status, deadline, or assignee changes trigger notifications.

External systems

Monitoring (Zabbix, Prometheus) sends a POST to the bot's webhook endpoint → the bot messages the duty engineer. Similarly for payment systems, 1C, third-party CRMs. A Bitrix24 webhook easily integrates with any external service.

Scheduled checks

Cron runs a script every hour: it checks overdue tasks via tasks.task.list, deals with no activity for N days via crm.deal.list, and sends a summary to those responsible.

Notification scenarios and reliability

Group notifications

The bot can write to group chats. In that case, DIALOG_ID is the chat ID (chatXXX). To create a service chat, use im.chat.add; add the bot as a participant via im.chat.user.add.

Queue and delivery guarantee

With multiple event sources, we use a queue (Redis, RabbitMQ). The webhook handler instantly accepts the event and puts it in the queue (200 response in < 1 second). A worker picks from the queue and sends to Bitrix24, preventing message loss when the REST API is temporarily unavailable. This guarantees delivery under peak loads.

Project scope and timelines

Total: 1–2 weeks depending on the number of scenarios and sources.

Setup steps and included services

1. Register the bot via imbot.register.
2. Get the BOT_ID and save it in configuration.
3. Set up event handlers (event.bind) for required events.
4. Implement message sending via imbot.message.add with needed parameters.
5. Test scenarios and go live.

What's included in the work

• Analysis of notification scenarios and selection of event sources
• Bot registration and REST route setup
• Connecting 1 to 5 sources (CRM, tasks, webhooks)
• Implementing quick-action buttons (accept lead, go to deal)
• Setting up Redis queue and error handling
• Testing all scenarios in test and production environments
• Launch and one-month monitoring
• Documentation and admin training

We guarantee reliable delivery—over years of practice, we've deployed more than 50 bots. A notification bot is 5 times faster than email and independent of mail filters. Clients typically achieve a 500% ROI within the first year, with savings of over $10,000 annually from reduced manual work.

In one project for a logistics company, we reduced notification delays from 5 minutes to under 1 second by using a Redis queue and asynchronous processing. The bot now handles over 10,000 events daily with zero loss.

Contact us to assess your project—we'll determine the optimal bot architecture and calculate timelines in 1 day. Order your turnkey Bitrix24 notification bot—from analysis to launch in 1–2 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.