Bitrix24 is an internal employee instant-messaging channel — the same role
Telegram or Slack plays for staff. An AiHummer agent appears inside your
company’s Bitrix24 as a colleague that employees can message and mention.
The channel ships as a connector from the in-product
Marketplace and runs host-native. It is
configured from the Admin UI, like any other channel.
[!NOTE]
The Bitrix24 channel requires an active Starter, Business or
Enterprise licence. On the Community plan, installing the connector returns
HTTP 402 “upgrade required” (code plan_limit) — see
Licensing.
[!WARNING]
Bitrix24 here is strictly an internal employee IM channel. It is not
customer omnichannel, not Bitrix24 Open Lines, not a ticket queue, and
not an operator-escalation surface. Do not use it to route external
customer conversations.
A human-like agent identity
Each agent connects with its own human-like OAuth identity, so it shows up in
Bitrix24 as a distinct person rather than a generic integration bot. Visibility
respects your org structure through a department-tree ACL — an agent only
sees and participates where its identity is permitted, following the same
department hierarchy your employees do.
Besides OAuth identities, the connector also supports other provisioning paths:
auto-provisioning agent accounts via a portal administrator login
(BITRIX24_ADMIN_LOGIN / BITRIX24_ADMIN_PASSWORD) and binding to
pre-created Bitrix24 users by fixed ids (BITRIX24_AGENT_USER_IDS).
Ports and runtime
The connector listens on a single port:
Port
Purpose
8810
Connector service (health, the Deliver endpoint and OAuth consent)
How messages flow
Bitrix24 does not push inbound events to AiHummer; the connector pulls them.
Inbound — a pull poller reads new messages and posts them to the gateway at
/v1/inbound/generic.
Outbound — replies are delivered through the aihummer.connector.v1Deliver contract. Agent markdown is converted to Bitrix24 BB-code, and
delivery is idempotent, so a retried send never produces a duplicate
message.
What is supported
The channel covers the interactions that fit a human-like employee identity:
Reactions, message edit and delete.
Typing indicators.
@-mentions.
Media in outbound messages.
[!WARNING]
Some Telegram-style features are intentionally not supported in the
human-like model:
No interactive keyboards or buttons and no threads.
Inbound media and voice are not forwarded — inbound is text-only.
Plan agent flows around text-based interaction on this channel.
**Bitrix24 is an internal employee instant-messaging channel** — the same role
Telegram or Slack plays for staff. An AiHummer agent appears inside your
company's Bitrix24 as a colleague that employees can message and mention.
The channel ships as a **connector from the in-product
[Marketplace](/en/v1.0/marketplace/overview-tiers)** and runs host-native. It is
configured from the Admin UI, like any other channel.
> [!NOTE]
> The Bitrix24 channel requires an active **Starter**, **Business** or
> **Enterprise** licence. On the Community plan, installing the connector returns
> **HTTP 402 "upgrade required"** (code `plan_limit`) — see
> [Licensing](/en/v1.0/commercial/licensing).
> [!WARNING]
> Bitrix24 here is strictly an **internal employee IM channel**. It is **not**
> customer omnichannel, **not** Bitrix24 Open Lines, **not** a ticket queue, and
> **not** an operator-escalation surface. Do not use it to route external
> customer conversations.
## A human-like agent identity
Each agent connects with its own **human-like OAuth identity**, so it shows up in
Bitrix24 as a distinct person rather than a generic integration bot. Visibility
respects your org structure through a **department-tree ACL** — an agent only
sees and participates where its identity is permitted, following the same
department hierarchy your employees do.
Besides OAuth identities, the connector also supports other provisioning paths:
**auto-provisioning agent accounts via a portal administrator login**
(`BITRIX24_ADMIN_LOGIN` / `BITRIX24_ADMIN_PASSWORD`) and binding to
**pre-created Bitrix24 users by fixed ids** (`BITRIX24_AGENT_USER_IDS`).
## Ports and runtime
The connector listens on a single port:
| Port | Purpose |
|---|---|
| 8810 | Connector service (health, the Deliver endpoint and OAuth consent) |
## How messages flow
Bitrix24 does not push inbound events to AiHummer; the connector **pulls** them.
- **Inbound** — a pull poller reads new messages and posts them to the gateway at
`/v1/inbound/generic`.
- **Outbound** — replies are delivered through the `aihummer.connector.v1`
**Deliver** contract. Agent **markdown is converted to Bitrix24 BB-code**, and
delivery is **idempotent**, so a retried send never produces a duplicate
message.
## What is supported
The channel covers the interactions that fit a human-like employee identity:
- Reactions, message **edit** and **delete**.
- **Typing** indicators.
- **@-mentions**.
- **Media** in outbound messages.
> [!WARNING]
> Some Telegram-style features are intentionally **not** supported in the
> human-like model:
>
> - **No interactive keyboards or buttons** and **no threads**.
> - **Inbound media and voice are not forwarded** — inbound is **text-only**.
>
> Plan agent flows around text-based interaction on this channel.
## Where to next
- On installing connectors: [Marketplace](/en/v1.0/marketplace/overview-tiers).
- For interactive keyboards and polls, use [Telegram](/en/v1.0/channels/telegram)
or [MAX](/en/v1.0/channels/max).
- See the underlying ingestion API in
[Generic inbound](/en/v1.0/channels/generic-inbound).
