The Bitrix24 plugin connects your agent to Bitrix24 as an internal employee
instant-messaging channel. Staff message the agent the same way they would
message a colleague, and the agent replies inside Bitrix24’s chat.
[!WARNING]
Bitrix24 here is an internal employee IM channel — like Telegram or Slack
for staff. It is not customer omnichannel: there are no Open Lines, no
ticket queue and no operator escalation. Do not use this plugin to front a
customer support line.
The plugin runs host-native and talks to the gateway over the
contract. End-user channel behaviour is on the channel
page Bitrix24; this page covers the plugin itself.
Facts
Field
Value
Version
1.0.0
Port
8810
Runtime
host-native
What it is
A two-way bridge between Bitrix24 chat and AiHummer. The agent appears as a
human-like identity in Bitrix24 — each agent authenticates with its own
OAuth identity rather than a generic bot account — so conversations feel like
talking to a colleague. Access follows the organisation’s department-tree
ACL, so an agent’s reach respects your Bitrix24 structure.
How it is used
Inbound: a pull poller picks up new messages and forwards them to the
gateway’s generic inbound endpoint, where the router resolves the target agent.
Outbound: replies are sent through the connector’s idempotent Deliver
step, which converts the agent’s Markdown into Bitrix24 BB-code and
guarantees a message is not sent twice.
The plugin supports rich, human-like chat behaviour:
reactions
message edit and delete
typing indicators
@-mentions
media
Limits
[!WARNING]
The human-like model intentionally does not include some Bitrix24 bot
features:
No interactive keyboards / buttons and no threads.
Inbound media and voice are not forwarded — inbound is text-only. A
colleague-style identity receives and responds to text; attachments and voice
notes sent to the agent are not relayed into a turn.
Installation
Install Bitrix24 in one click from the marketplace in the admin UI. The
host-native deployer downloads the plugin, runs its install step, renders a
sandboxed systemd unit and waits for health before marking it ready — see
Install & updates. You then connect each
agent’s OAuth identity and map the department-tree ACL.
Security and limits
Internal employee IM only — not customer omnichannel.
Per-agent human-like OAuth identity — agents are not generic bot accounts.
Department-tree ACL — reach respects your org structure.
Idempotent Deliver — Markdown is rendered to BB-code and never sent twice.
Text-only inbound; no keyboards/threads.
Host-native — runs under systemd, not in a container.
<p class="doc-plugin-logo"><img class="th-on-dark" src="/pl/bitrix24-dark.svg" alt="" width="60" height="60" /><img class="th-on-light" src="/pl/bitrix24-light.svg" alt="" width="60" height="60" /></p>
**The Bitrix24 plugin connects your agent to Bitrix24 as an internal employee
instant-messaging channel.** Staff message the agent the same way they would
message a colleague, and the agent replies inside Bitrix24's chat.
> [!WARNING]
> Bitrix24 here is an **internal employee IM channel** — like Telegram or Slack
> for staff. It is **not** customer omnichannel: there are no Open Lines, no
> ticket queue and no operator escalation. Do not use this plugin to front a
> customer support line.
The plugin runs host-native and talks to the gateway over the
contract. End-user channel behaviour is on the channel
page [Bitrix24](/en/v1.0/channels/bitrix24); this page covers the plugin itself.
## Facts
| Field | Value |
|---|---|
| Version | 1.0.0 |
| Port | 8810 |
| Runtime | host-native |
## What it is
A two-way bridge between Bitrix24 chat and AiHummer. The agent appears as a
**human-like identity** in Bitrix24 — each agent authenticates with its own
OAuth identity rather than a generic bot account — so conversations feel like
talking to a colleague. Access follows the organisation's **department-tree
ACL**, so an agent's reach respects your Bitrix24 structure.
## How it is used
- **Inbound:** a pull poller picks up new messages and forwards them to the
gateway's generic inbound endpoint, where the router resolves the target agent.
- **Outbound:** replies are sent through the connector's idempotent **Deliver**
step, which converts the agent's Markdown into Bitrix24 **BB-code** and
guarantees a message is not sent twice.
```text
employee ─▶ Bitrix24 chat ─▶ pull poller ─▶ gateway (router · turn) ─▶ Deliver (Markdown→BB-code, idempotent) ─▶ Bitrix24
```
## Supported features
The plugin supports rich, human-like chat behaviour:
- reactions
- message edit and delete
- typing indicators
- @-mentions
- media
## Limits
> [!WARNING]
> The human-like model intentionally does **not** include some Bitrix24 bot
> features:
>
> - **No interactive keyboards / buttons** and **no threads.**
> - **Inbound media and voice are not forwarded** — inbound is **text-only.** A
> colleague-style identity receives and responds to text; attachments and voice
> notes sent *to* the agent are not relayed into a turn.
## Installation
Install Bitrix24 in one click from the marketplace in the admin UI. The
host-native deployer downloads the plugin, runs its install step, renders a
sandboxed systemd unit and waits for health before marking it ready — see
[Install & updates](/en/v1.0/marketplace/install-updates). You then connect each
agent's OAuth identity and map the department-tree ACL.
## Security and limits
- **Internal employee IM only** — not customer omnichannel.
- **Per-agent human-like OAuth identity** — agents are not generic bot accounts.
- **Department-tree ACL** — reach respects your org structure.
- **Idempotent Deliver** — Markdown is rendered to BB-code and never sent twice.
- **Text-only inbound; no keyboards/threads.**
- **Host-native** — runs under systemd, not in a container.
## Where to next
- Channel: [Bitrix24](/en/v1.0/channels/bitrix24)
- [Install & updates](/en/v1.0/marketplace/install-updates)
- [Marketplace overview & tiers](/en/v1.0/marketplace/overview-tiers)