Mail events in Telegram and MAX: applications, orders, forms

What this solution does

The module transmits website mail events from 1C-Bitrix to the Telegram and MAX messengers. Chat notifications cover form submissions, new and paid orders, registrations, inquiries, and any custom events. A message appears in a manager group or personal chat within seconds of the event occurring.

The module operates with Bitrix mail events and templates rather than a fixed list. Specific events and templates are selected within rules. Three selection modes are available: manual selection of only events specified in rules; automatic selection by masks, such as SALE_*; and a mixed mode.

Two messengers are integrated into a single module: Telegram and MAX. The same set of events can be sent to both services simultaneously. Each bot has its own dedicated recipients in personal chats, groups, or channels.

The system supports sending events that lack a mail template by using a custom message template with variables and conditional blocks. HTML email content is automatically converted to messenger markup, and long messages are split into parts. A preview function allows viewing the message based on real event data, and a test send to a specific recipient is available.

The module sends events from 1C-Bitrix to Telegram and MAX: applications, orders, and form data. Personal data (phone, e-mail) is masked by field names. Passwords, keys, and confirmation codes do not appear in messages; events containing such data are not sent automatically.

A sending queue with retries on failures is implemented, along with duplicate protection and adherence to messenger limitations. Messenger failures do not slow down the website. A delivery log records every attempt, status, messenger response, and resending.

The module works where messengers are unavailable from the hosting: using proxies (SOCKS5, HTTP), a custom relay (ready-made scripts for PHP and Cloudflare Worker), and multiple routes with automatic failover. Administrators receive notifications about delivery failures, stuck queues, and disabled recipients. Bot tokens are stored in the database in encrypted form.

The interface supports Russian and English languages, uses UTF-8 encoding, and supports multiple websites.

Requirements: 1C-Bitrix: Site Management, PHP 8.2 or newer with curl, mbstring, json, and openssl extensions; a bot in Telegram and/or MAX. Bots in MAX are created by organizations, individual entrepreneurs, and self-employed persons who are residents of the Russian Federation.

General iT can connect “Mail events in Telegram and MAX: applications, orders, forms”, install and configure the module, and make sure the integration works correctly.