ZetaLine Site Notifications for MAX

ZetaLine Site Notifications for MAX integrates your WordPress site with the MAX messenger.
All emails sent via wp_mail() can be duplicated to selected users or group chats in MAX.
Additionally, the plugin can send notifications when new posts are published, forms are submitted, and WooCommerce orders are created or change status.

Key features:

• Sends the content of WordPress emails to MAX.
• Supports a list of recipients by user_id and chat_id.
• Flexible message templates and formats (Markdown, HTML, plain text). If a template is not set, the full email body (including all form fields) is sent to MAX.
• Optional email filter: send notifications only for specific email addresses.
• Post notifications: send a message to MAX when a post is published, with customizable template and post types.
• WPForms integration: sends form submissions directly to MAX even if WPForms email notifications are disabled. Each field is listed on a separate line in the message.
• WooCommerce integration:
  • Uses woocommerce_checkout_order_processed to send details about new orders to MAX (order number, customer name, total amount, items).
  • Uses woocommerce_order_status_changed to notify about cancelled and failed orders, including customer details, total and item list.
• HTML cleanup: all incoming text from emails, forms and WooCommerce is cleaned from HTML tags and entities before sending, so messages stay readable and safe.
• Per‑context recipients: you can configure different recipients for emails, posts, forms and WooCommerce orders.
• Tabbed settings page in the admin with detailed inline documentation.

External services

This plugin connects to the MAX Bot API to deliver configured WordPress notifications to users and group chats in the MAX messenger.

The service is used only when a site administrator enters a MAX bot token and at least one recipient user_id or chat_id in the plugin settings. When a configured notification event occurs, the plugin sends an HTTPS request to the MAX Bot API endpoint at https://platform-api2.max.ru. Depending on the enabled notification type and message template, the request may include the bot token in the Authorization header, the selected user_id or chat_id in the request URL, and notification text generated from WordPress email content, form submission fields, post titles/excerpts/URLs, or WooCommerce order details such as order number, customer name, email, phone, payment method, order total, product names, quantities, prices and item metadata.

This service is provided by MAX. Terms of use: https://legal.max.ru/ps. Privacy policy: https://legal.max.ru/pp.

How do I create a bot and get a token?

Create or open your chatbot in the MAX business platform: https://business.max.ru/.
According to the MAX API documentation, the token is available in Chatbots → Go → Advanced settings → Configure.
Copy the token and paste it into the plugin settings. The token is sent to the MAX API in the Authorization: <token> header.

How do I find my user_id or chat_id?

• user_id: the simplest way is to open the My ID bot and press Start: https://max.ru/id503215983600_1_bot.
  The bot shows your MAX user ID for connecting websites, plugins, CRM systems, notifications and other integrations.
  You can also ask the user to open your own bot and send any message to it. Then call GET https://platform-api2.max.ru/updates?types=message_created with the header Authorization: <your token>.
  In the response, look for message.sender.user_id – this is the ID of the user who sent the message.
  Do not confuse it with message.recipient.user_id, which is the bot ID.
• chat_id: add your bot to a group chat, make it an admin and send a message to the group.
  You can also temporarily add the My ID bot to a group chat as an administrator; it will show the chat ID.
  Receive the event through a Webhook subscription or call the same GET /updates endpoint while testing.
  The event object will contain the chat_id value you can use in the plugin settings. GET /chats is no longer supported for listing chats.

Why does the test message fail with an SSL or certificate error?

The plugin uses the official MAX Bot API domain https://platform-api2.max.ru. MAX documentation says that, for correct operation on the new API domain, requests must be redirected from platform-api.max.ru to platform-api2.max.ru and the Ministry of Digital Development certificate must be added to the trusted certificates list.

Download the official root certificates from the Gosuslugi page: https://www.gosuslugi.ru/crt. Ask your hosting provider to install these certificates into the server CA trust store for PHP/cURL/OpenSSL. This is a hosting/server configuration task, not a separate MAX setting.

After the hosting provider installs the certificate, test message delivery again. If WordPress still uses its own CA file instead of the server trust store, upload the CA bundle file to a private or site-local server path and enter the local filesystem path in Settings → ZetaLine Site Notifications → CA bundle path. Use a path such as /home/user/site/public_html/cert/russian_trusted_root_ca_pem.crt, not a public URL.

Do not disable SSL verification in WordPress. If the certificate is not trusted, requests to the MAX API may fail with cURL error 60: SSL certificate problem: unable to get local issuer certificate.

1.0.13

• Added MAX for Business and My ID bot links to the setup instructions.
• Added explicit setup notes for the Ministry of Digital Development CA certificates required by the new MAX API domain.
• Improved formatting for form fields, email-derived form fields, and WooCommerce order customer details.
• Updated built-in form and order templates with clearer spacing between message sections.

1.0.12

• Added an optional CA bundle path setting for servers where WordPress cURL does not use the updated system certificate store.

1.0.11

• Test messages now use the real MAX API response to determine success or failure.
• Added MAX API error details to the test message result in the settings page.
• Updated setup instructions for obtaining user_id and chat_id according to current MAX API behavior.
• Added a note about server CA bundle updates for SSL certificate errors with the MAX API.

1.0.10

• Added automatic migration from the old settings option name to keep existing settings after updating from earlier versions.

1.0.9

• Updated MAX Bot API base URL to platform-api2.max.ru.
• Replaced the new order WooCommerce hook with woocommerce_checkout_order_processed.
• Improved WooCommerce item output and added {Items} compatibility for order templates.
• Added explicit sanitization for all saved template settings.
• Replaced short public prefixes with a unique plugin prefix.
• Added the WordPress.org-required External services disclosure.

1.0.8

• Fixed Plugin Check violations for WordPress.org:
  • Removed the direct load_plugin_textdomain() call.
  • Replaced strip_tags() with wp_strip_all_tags() in post excerpt generation.
  • Added translator comments for strings with placeholders.
• Added languages/ directory so Domain Path: languages is valid.
• Updated the main plugin version and readme stable tag.

1.0.7

• Added a tabbed settings page in the admin.
• Added per‑context settings for email, posts, forms and WooCommerce orders (recipients and templates).
• Added a detailed help tab with setup instructions.

1.0.6

• Fixed a fatal syntax error introduced in version 1.0.5 by correcting the class structure around the sanitize_text() method.
• Updated the plugin version number and readme file.

1.0.5

• Improved message cleanup by stripping HTML tags and decoding HTML entities before sending.
• Added customer email, phone, payment method, product prices and total amount to WooCommerce order notifications.
• Added notifications for cancelled and failed WooCommerce orders through woocommerce_order_status_changed.
• Updated the plugin title and description.
• Publishing instructions have been updated and developer Zetaline’s details have been added.

1.0.4

• Added WPForms integration through wpforms_process_complete, so form data can be sent to MAX even when WPForms email notifications are disabled.
• Added WooCommerce integration for new order notifications with order number, customer, total and product list.

1.0.2

• Fixed user_id detection logic. To retrieve your ID, we now recommend searching for the message.sender.user_id field instead of message.recipient.user_id, as the latter contains the bot ID. Details are available on the settings page.
• Renamed the template field on the settings page and expanded the explanation: by default, the plugin sends the full email body (including all form fields), and the template is an optional setting for customization.
• Clarified the priority of the wp_mail filter to ensure proper processing of email sending.

1.0.1

• Improved email sending logic: if the “Email template” field is left blank, the plugin sends the full email body to MAX without modification. This allows duplication of any form data (MetForm, Contact Form 7, WooCommerce, WPForms, etc.).
• Updated documentation and examples on the settings page.

1.0.0

• Initial version of the plugin. Support for sending email notifications and notifications about the publication of new posts in the MAX messenger.