AiHummer docs
v1.0.x ▾
v1.0.x stable
RU EN
Channels /MAX

MAX

v1.0.x · updated 2026-06-27

MAX is a Russian messenger, and AiHummer connects to it as a channel. The agent appears in MAX as a bot: it receives inbound messages, runs a normal turn, and sends the reply back — just like Telegram and the other channels.

MAX ships as a Marketplace channel connector and is built on the MAX Bot API. It is not a service you build yourself: you install the connector from the in-product Marketplace and configure it from the Admin UI, like any other channel.

Install from the Marketplace

Open the in-product Marketplace and install the MAX module. Once installed, the channel shows up in the channels section of the Admin UI with the channel id max — use that id when you bind an agent or filter conversations by source.

Set it up from the Admin UI

  1. Create a MAX bot and obtain its token.
  2. In the Admin UI, open the MAX channel settings.
  3. Paste the bot token into MAX_BOT_TOKEN (a secret, required).
  4. Optionally set the MAX Bot API base URL in MAX_API_BASE. It defaults to https://platform-api2.max.ru, so you can usually leave this blank.
  5. Save — the connector starts receiving and sending messages.

[!TIP] MAX is the channel identified to AiHummer as max. Use that channel id when you bind an agent or filter conversations by source.

What is supported

The MAX connector covers the core conversation flows:

  • Send and receive messages between the agent and MAX users.
  • Long-poll inbound — the connector pulls incoming updates (mentions, replies, media, interactive events), so no inbound public port is required.
  • Native replies to a specific message.
  • Basic inline keyboards for quick interactive buttons.
  • Media-by-URL in outbound messages.
  • Dedupe by key, so a retried delivery never produces a duplicate.

How messages flow

Each inbound MAX message reaches the gateway over the same inbound path as every other channel, secured by the shared inbound-HMAC secret. From there the turn engine processes it like any other channel message.

[!NOTE] The gateway must have a default workspace configured to dispatch inbound messages.

Where to next