Yandex Messenger

What the agent can do

• Receives every message in the chats the bot is in, and saves attachments (up to 50 MB).
• Replies with text, reacts, shows a typing indicator and sends the files it prepared into the chat.
• Names the space after the real chat title.

Access and billing

The bot acts as itself, not as an employee. A Messenger bot token has no scope checkboxes: it authorizes everything bots can do straight away. Two conditions take the place of scopes: only an organization admin can issue it, and the bot must be added to the chats it should serve.

You do not enter an organization ID: Octo never asks for it, because the token already belongs to one bot in one organization. The token is stored encrypted and never sent back to the browser. The connection owner pays; connecting costs 10 energy once.

How to connect

1. An organization admin opens the Yandex 360 admin, Messenger, "Bots in Messenger": admin.yandex.ru/bot-platform.
2. Click "Create bot" and give it the name chats will see. The token is generated and copied to your clipboard. Yandex does not store bot tokens: a lost token can only be reissued ("Reissue token" in the bot settings).
3. In the dashboard, open Integrations, Yandex Messenger, paste the token into the Bot OAuth token field, optionally add a label, and click Create.
4. Click Health-check. The token is not validated when you create the connection, so this check matters.
5. In Messenger, add the bot to the chats you need through the chat's member list, by the bot's name.

You can also connect from Telegram: send /yandex to @octodus_bot in a direct chat. The bot deletes the message with the token right away.

Chats, spaces and the console

Every chat the bot is in automatically becomes its own space owned by the connection owner. The organization gets an integration console: employees and their spend, a monthly limit per employee, spaces, the default set of capabilities, co-owners and the organization's shared Yandex Disk.

Other services are attached to these spaces by space, by tag or by integration: Connecting services to spaces.

When the bot replies

• In a direct chat: to every message.
• In a group chat: when the bot is called by name ("Octo") or a nickname, when someone replies to its message, or in a thread the bot started.
• A new employee's first request waits for the connection owner's approval, as in Bitrix24.

Limits

• Messenger works by polling only (getUpdates), with no webhook: the bot checks for new messages every 3 seconds.
• One connection per organization per owner.
• The monthly limit per employee (in the console) applies across all of the organization's spaces, alongside space limits.

Troubleshooting

Health-check: "HTTP 401 from Yandex"

The token does not work: copied incompletely, taken from somewhere other than the bot (a "Yandex ID" token, say), or already reissued. Issue it again in "Bots in Messenger" and paste the new value.

Health-check: "HTTP 403 from Yandex"

The token is fine, but bots are disabled for the organization. A Yandex 360 organization admin has to enable bots.

Health-check: "Could not reach Yandex"

This is not about your token. Our side could not reach botapi.messenger.yandex.net: the problem is our network egress, not your setup. Retry later and contact support if it persists.

"A connection for this org already exists"

This token is already connected. Change the token or label on the existing card.

The bot is silent

Is the bot in the chat? Was it called by name, replied to, or addressed in its thread? Is the author waiting for approval?