Telegram & MAX Notifications
Telegram & MAX Notifications helps you deliver website form submissions straight to the messengers you actually use.
The plugin adds a ready-to-use frontend form component for OctoberCMS and sends submitted data to Telegram, MAX messenger, or both channels simultaneously. It is designed for business websites, landing pages, service websites, callback forms, order pages, and any project where incoming requests should reach the team instantly.
Key benefits
- Send notifications directly to Telegram
- Send notifications directly to MAX messenger
- Deliver to both Telegram and MAX at the same time
- Add a ready-made contact form to any page or layout
- Use a standard embedded form or a Bootstrap 5 modal version
- Manage channel settings from backend settings
- Keep delivery resilient with fallback routing support
- Optionally use the author's proxy setup for projects that need a custom delivery route
Why this plugin is useful
Many projects need a fast and simple way to receive leads without building a full CRM or relying only on email. Telegram & MAX Notifications gives you a lightweight notification workflow: a visitor submits a form, and the message is delivered to the selected messenger channel immediately.
The plugin is especially practical for projects working across different communication environments. Some teams rely on Telegram, others use MAX, and some need both. This plugin covers all of those scenarios in a single integration.
An additional advantage is the optional proxy-based delivery route. For projects in Russia where direct Telegram delivery may require a more stable or custom route, the plugin can be used together with the author's proxy setup on an individual basis.
Delivery logic
- If only Telegram is configured, messages are sent to Telegram
- If only MAX is configured, messages are sent to MAX
- If both are configured, messages are sent to both channels
- If neither direct channel is configured, fallback routing can be used
Technical highlights
- Built for OctoberCMS 4.x
- Requires PHP 8.1+
- Uses backend settings for channel configuration
- Automatically converts HTML message content to plain text for MAX compatibility
- Logs delivery errors through the standard Laravel / October logging system
- Includes migration from older config-based setup into backend settings
Installation via Command Line
php artisan plugin:install DMdev.Telegramnotice
Documentation
Overview
Telegram & MAX Notifications is an OctoberCMS plugin that sends frontend form submissions to Telegram, MAX messenger, or both simultaneously. It also supports fallback routing, including an optional author-managed proxy setup for projects that require an alternative delivery route.
Requirements
- OctoberCMS 4.x
- PHP 8.0+
Installation
Install via OctoberCMS plugin installer
php artisan plugin:install Dmdev.Telegramnotice --from=https://github.com/mifasu/telegramnotice.git
Manual installation
cd plugins/dmdev git clone https://github.com/mifasu/telegramnotice.git telegramnotice php artisan october:up
Configuration
Open:
Backend → Settings → Telegram Notice
Telegram configuration
Fill in:
bot_token— your Telegram bot tokenchat_id— your target Telegram chat or channel ID
MAX configuration
Fill in:
max_bot_token— your MAX bot access tokenmax_chat_id— your target MAX chat or channel ID
Important: MAX does not support HTML formatting in message text. The plugin automatically converts the outgoing message into plain text before sending.
Fallback configuration
pechkin_secret— secret key for fallback delivery
If Telegram and MAX are not configured, the plugin can use fallback routing automatically.
Important: if you want to use the author's proxy-based delivery route, it must be configured individually. The site and token should be registered and linked to the destination chat or channel in advance.
Routing behavior
- Telegram only → send to Telegram
- MAX only → send to MAX
- Telegram + MAX → send to both
- Neither configured → send through fallback routing
Usage
Attach the component to a page or layout
title = "Contact" url = "/contact" layout = "default" [telegramNotice]
Render the default form
{% component 'telegramNotice' %}
Render the modal form
{% component 'telegramNotice' template="TelegramNotice::order-modal-form" %}
Component properties
btnName— submit button labelsitename— legacy site hostname for fallback usagetoken— legacy fallback token override
Accepted form fields
The component accepts these common fields:
ph,phone,phone_number,contact— phone numbername,nm,fullname— customer nametag— optional tag appended to the messagefrom— page or section labelarr[]— additional values, one line per item
Logging
Send errors are logged through the standard Laravel / October logging system.
Migration
If an older config file was previously used, the plugin can migrate those values into Backend Settings automatically on first boot when the settings fields are still empty.
Repository
GitHub repository:
-
This plugin has not been reviewed yet.
-
| 1.2.1 |
Relax composer/installers constraint to support modern OctoberCMS dependency trees and Composer 2 environments. May 22, 2026 |
|---|---|
| 1.2.0 |
Add MAX messenger support via platform-api.max.ru. New settings max_bot_token and max_chat_id. Messages sent to Telegram and MAX simultaneously when both configured. MAX text auto-converted from HTML to plain-text. Pechkin fallback used only when neither Telegram nor MAX is configured. Apr 24, 2026 |
| 1.1.3 |
OctoberCMS 4.x compatibility. Fallback uses canonical API v1 endpoint with Bearer auth and X-Site-Name header. Supports DMDEV_API_BASE_URL env override. Fix Settings model visibility, remove debug log, add LICENSE and marketplace-ready composer.json. Apr 24, 2026 |
| 1.1.2 |
Fix direct Telegram API call, persist generated pechkin_secret, improve error handling, return accurate send status. Apr 24, 2026 |
| 1.1.1 |
Moved configuration into Backend Settings model, removed physical config file, added settings migration. Apr 24, 2026 |
| 1.1.0 |
Added direct Telegram Bot API support with pechkin_secret fallback and error logging. Apr 24, 2026 |
| 1.0.3 |
Bug fixes and refactored send method. Apr 24, 2026 |
| 1.0.2 |
Added support for arr[] fields to include additional values in messages. Apr 24, 2026 |
| 1.0.1 |
Initial release. Adds TelegramNotice component and basic form templates. Apr 24, 2026 |