Notification Transports (Telegram / MAX) (EcomLabs)

What this solution does

The module sends notifications about Bitrix events (including email and SMS events) to the Telegram and MAX messaging platforms. Features include text templates, a message queue with retries, event logging, user chat binding to bots, webhooks, and testing tools.

Access is provided via the administration menu: «Notification Transports» (sections: Templates, Queue, Log, Bindings, Tools / Test). Global module settings are located at: Settings → Product Settings → Module Settings → Notification Transports (Telegram / MAX).

Configuration is organized into three tabs: General, Telegram, and MAX.

The General tab contains the following parameters:

- Send attempts: the number of retries for sending a message from the queue upon failure.

- Binding token TTL (minutes): the validity period of a one-time deep-link token used to bind a user's chat to a bot.

- Queue batch size: the number of jobs processed by the agent in a single run.

- Preferred messenger: selection of priority (Telegram, MAX, or none) when a user has multiple active bindings.

The Telegram tab includes:

- Enable Telegram: toggle to activate or deactivate the delivery channel.

- Telegram bot token: the key obtained via @BotFather.

- Bot name (without @): the username for t.me/... links, which can be automatically retrieved using the «Check bot» tool.

- Webhook secret: the secret_token used to verify incoming requests from Telegram.

The eComLabs notification transport module supports integration with Telegram and the MAX platform. For Telegram, settings include disabling link previews during message sending, specifying a manual administrator chat ID for tests and admin notifications, and using a public webhook for reading at the path bitrix/tools/ecl_eventtransports_webhook_telegram.php.

For the MAX platform, options include enabling or disabling the channel, entering the bot access token, and setting the bot name for deep links and display. Configuration involves a webhook secret for verifying incoming requests, a manual administrator chat ID, and the API URL defaulting to platform-api2.max.ru. SSL verification can be disabled if the certificate chain is untrusted, including certificates from the Ministry of Digital Development. The deep link template includes placeholders #BOT# and #TOKEN# for binding. The system allows configuring the bot's response text after successful binding and a welcome message for requests without a token. A public MAX webhook for reading is also available.

The administrative panel features a notification templates section for Telegram and MAX channels. Users can view the list of templates, create and edit them by binding to a Bitrix event code (SMS or email), define message text, and manage activity status.

The Notification Transports (Telegram / MAX) module by eCom Labs manages message delivery via Telegram and MAX channels. Event codes are automatically pulled from the site's email and SMS event types. The system follows a rule where each combination of event code and transport generates a unique template. When the OnBeforeEventSend, OnBeforeEventAdd, or OnBeforeSmsSend handlers are triggered, the module queues a task if a matching template exists and a recipient binding is configured.

The task queue (queue_list) records the channel, event, user, order, chat_id, status (New, Retry, Sent, Error), attempt count, error text, and date. Available actions include retrying the send operation or deleting the record. The queue is processed by the agent \Ecl\EventTransports\Service\QueueService::agent().

The log (log_list) maintains a history of send attempts, indicating success or failure, channel, event, chat_id, link to the queue record, and date. Log entries can be deleted.

Bindings (bindings_list) map Bitrix users to chat_ids in Telegram and MAX. Each binding has a status (active or disabled) and can be removed.

The Tools and Test section displays webhook URLs for Telegram and MAX. For Telegram, functions include checking the bot (getMe), setting up the webhook, verifying webhook status, and deleting the webhook. For MAX, functions include setting up the webhook, retrieving bot information (/me), checking webhook status, and deleting the webhook.

The 'Notification Transports (Telegram / MAX)' module by eCom Labs manages connections between Bitrix users and messaging platforms. Key capabilities include generating binding links for a specific Bitrix user ID and transport type, updating binding status, performing unbinding, and sending test arbitrary text messages to linked users. Manual binding via MAX user_id or Telegram chat_id is available if the webhook is not yet configured.

In the user profile settings, a 'Messengers' tab displays the binding status for Telegram and MAX, along with buttons to initiate binding or unbinding.

The ecl:eventtransports.bind component, titled 'Binding to Telegram / MAX', is designed for placement within the personal cabinet or user profile to manage messenger connections. Component parameters allow independent control over showing Telegram and MAX; both are enabled by default.

The component operates exclusively for authorized users. It displays the connection status (bound or unbound) and the chat ID. Binding and unbinding actions are executed via an AJAX request to the ecl_eventtransports_user_bind_ajax.php file located in the tools directory. When the 'Bind' action is triggered, the system can generate a deep link to the bot containing a one-time token, with the time-to-live (TTL) configurable in the module settings. Upon user transition to the bot and confirmation, the webhook records the binding in the database.

The module connects via a visual editor or by programmatically calling the ecl:eventtransports.bind component. The tools section includes bot token verification: testing the Telegram bot using the getMe method and retrieving information about the MAX bot via the /me command. A successful response confirms the token is valid and the API is accessible; for Telegram, the bot name may be automatically saved to the module settings. Telegram webhooks operate only over HTTPS; requests using HTTP return an error. Webhook subscription is configured on the module's public URL using the secret token from the settings. Webhook status, last errors, and pending updates are displayed via dedicated buttons. Incoming requests are processed by scripts in the bitrix/tools directory: ecl_eventtransports_webhook_telegram.php and ecl_eventtransports_webhook_max.php. These scripts verify the secret, handle user binding data, and create or update binding records. The test send feature delivers a message to the bound user's chat ID, verifying the complete delivery path from settings through the messenger API. The module also utilizes queues and agents for event processing.

eComLabs module for sending notifications via Telegram and MAX. When a Bitrix event triggers, the system finds the corresponding template and queues the task. An agent processes the message batch considering the number of attempts and group size, then records the result in the journal as success or failure.

General iT can take care of implementing “Notification Transports (Telegram / MAX) (EcomLabs)”, including installation, configuration and result verification.