Skip to content
OctodusDocs

Connectors

Bitrix24

The agent as a chat bot in your Bitrix24 portal: an inbound webhook with the imbot scope, connecting, reply rules, approving employees, limits and errors.

Last updated:

On this page
  1. What the agent can do
  2. Access and billing
  3. How to connect
  4. Chats and spaces
  5. When the bot replies
  6. Limits
  7. Troubleshooting

What the agent can do

  • Receives every message in the chats the bot is a member of and keeps them as context for later answers.
  • Downloads attachments from messages (up to 50 MB) and works with them.
  • Replies with Bitrix24 formatting and shows a typing indicator. The agent cannot send files into a Bitrix24 chat yet.

Access and billing

The connection uses the portal's inbound webhook: every call runs as the Bitrix24 user who created the webhook. A dedicated chat bot is registered through it. The webhook is stored encrypted and is never sent back to the browser.

The owner of the connection pays. Connecting a portal costs 10 energy once; spend per employee is on the connection card (Energy by user).

How to connect

In Bitrix24

  1. Sign in to the portal as an administrator: only an admin can create webhooks.
  2. Open Applications, Developer resources, Other, Inbound webhook.
  3. In the webhook permissions, tick "Create and manage chat bots (imbot)". Without this scope the connection fails.
  4. Save and copy the whole URL, like https://portal.bitrix24.ru/rest/1/abc…/. It already contains the portal domain and the token.

In the dashboard

  1. Open Integrations, Bitrix24 and click Connect Bitrix24.
  2. Paste the webhook into the Inbound webhook field, set the bot name and click Create.
  3. Add the bot to the portal chats where it should work.

The connection card has a health check, disable, change webhook or name, delete, and the member list. Disabling stops the bot.

Chats and spaces

Every portal chat that writes to the bot, and every direct dialog with it, automatically becomes its own space owned by the connection owner. Outside services are attached to these spaces by space, by tag or by integration (see Connecting services to spaces). Yandex Disk can be attached to new spaces like these automatically.

When the bot replies

  • In a direct dialog: to every message.
  • In a group chat: when the bot is mentioned, called by name ("Octo"), or by a nickname set for the space.

Limits

  • One connection per portal per owner.
  • The bot checks for new messages every 3 seconds and slows down on its own when Bitrix24 asks it to wait.
  • The owner's spending limits apply: per space or per employee.

Troubleshooting

"The webhook was rejected: grant the imbot scope"
Recreate the inbound webhook with "Create and manage chat bots (imbot)" ticked and paste the new URL.
"This doesn't look like a REST webhook URL"
Paste the whole URL, with /rest/, the user number and the token, not just the portal domain.
"Could not reach the portal" or an HTTP error
Check the portal address in the webhook and that the webhook still exists in Bitrix24.
"Not enough energy to connect (needs 10)"
Top up and try again.
"A connection for this portal already exists"
Use the existing card: you can change the webhook or the bot name there.
The bot is silent in a chat
Is the bot in the chat? Was it mentioned or called by name? Is the author waiting for approval (see the badge on the connection card)? Is the connection enabled?