Kommo, Bitrix24 and Odoo
Kommo, Bitrix24 and Odoo have native connectors. A connector is more than a CRM template: it also shows the caller's open deals, can create a lead for an unknown caller, offers tools to the AI agent and posts WhatsApp conversations to the CRM.
You find the three connectors in Admin > Settings > Integrations > Integrations (/admin/integrations). You need integrations:write to install one and integrations:read to see it.
What a connector does
| Feature | What happens |
|---|---|
| Caller card | For a number, the contact (with phone and e-mail), its company (with a link to the company's page in Kommo or Bitrix24) and its open deals (Odoo: open opportunities). Only open deals are shown, so won and lost ones are left out. The card is asked for with GET /api/v1/integrations/caller-context?number= (permission self:read). |
| Lead from an unknown caller | With Create a lead for an unknown inbound caller switched on, a caller the CRM does not know becomes a lead and the call is logged on it. The lead is named Call from <number>. |
| AI agent tools | crm_lookup (contact, company and open deals for a number) and crm_log_note (add a note to the contact of a number; nothing is added when the CRM does not know the number). The AI agent only calls the tools you tick under AI agent tools. |
| Writes from automations and AI agents | create_contact, create_lead, create_task and update_deal let an automation (or an AI agent, when you tick the tool) create a contact, a lead or a task on the contact of a phone number, and change a deal's name, stage or amount. They write with the connection you made here. A contact whose phone number already exists is never created twice. |
| Call history entry | A finished inbound or outbound call is written in the CRM's own call history. Kommo: a native incoming-call or outgoing-call note with the call's unique id, duration, result and recording link. Bitrix24: an entry in the portal's call journal with the duration, the result and the recording attached; it needs the portal user of the agent, so list the extensions in the User map setting as 11=101, 12=102 (Bitrix24 user id, then the extension). Without a mapped extension (and for calls between colleagues) the call is logged as a plain note or timeline comment, as before. Switch the native entries off with the setting call_notes = false. |
| WhatsApp conversation note | When an agent archives a WhatsApp conversation, one note goes to the contact (or to a new lead, if lead creation is on): a first line with the customer's name and a link to the conversation, then the latest 30 messages. Each message is cut at 240 characters and the whole note at 2000. It is posted once per conversation and CRM. |
Credentials are write-only: sealed with your company's key and never shown again.
Connect Kommo or Bitrix24
Both sign in with OAuth 2.0. You do not paste a token.
- In Integrations, install Kommo or Bitrix24.
- Enter the account address:
https://yourcompany.kommo.com, or the Bitrix24 portal addresshttps://yourcompany.bitrix24.com. Optionally switch on Create a lead for an unknown inbound caller. - Press Connect, sign in to the CRM and allow the access. The status shows Connected.
- Press Test connection, then tick the AI agent tools you allow.
The Connect button appears only when the operator of your PBX has registered MonoPbx as an app with the CRM. If it is missing, ask your operator. More about sign-in, reconnecting and disconnecting: OAuth connections.
Connect Odoo
Odoo has no OAuth for its external API, so the connector uses an API key of an integration user.
- In Odoo, create a user for MonoPbx and, in its preferences under Account Security, a new API key.
- In Integrations, install Odoo and enter the Odoo address (
https://yourcompany.odoo.com), the API key of the integration user and the Database name. - Odoo 19 and later needs nothing more. For Odoo 17 and 18 also enter the User id: the number in the user's address in Odoo.
- Press Test connection.
Contacts are res.partner records. Open opportunities are the contact's crm.lead records. Without the Odoo CRM app the card shows no deals.
How the connectors work
- Call log. To log every finished call in your CRM, use a CRM template, whose journal records every finished external call.
- Kommo and Bitrix24 accounts. The sign-in addresses of these two CRMs depend on the account. The operator's OAuth entry holds one fixed pair of addresses per connector, so each PBX connects to one Kommo account and one Bitrix24 account.
- Richer entries. Kommo gets a common note rather than a native call entry, and Bitrix24 gets a timeline comment rather than an entry in its call journal.
- Other channels. Only WhatsApp conversations post a timeline note. A failed post is not retried.
Click-to-call from the CRM
After you connect Bitrix24, MonoPbx registers the portal's click-to-call event itself, if the company has an enabled Bitrix24 hook endpoint. Without one, create the endpoint and connect again.
Kommo and Bitrix24 ring the agent's phone when someone presses the call button in the CRM. In Kommo, add the MonoPbx widget to the contact and lead cards; Kommo sends the click to your PBX signed with the integration's client secret. In Bitrix24, register the portal event ONEXTERNALCALLSTART with the address of your Bitrix24 hook endpoint (https://pbx.example.com/hooks/int/bitrix24/<install key>, see REST hooks); MonoPbx can register it for you with the portal's event.bind once the connector is connected.