Bitrix24 with an AI assistant: what you can set up without a developer
An AI assistant for Bitrix24 is a chat where you describe your sales process in words and it creates pipelines, stages, fields, deals and tasks in your portal through the official REST API. For Bitrix24 this is still a beta: structure, data, tasks and analytics work; robots and widgets do not yet. This guide draws the line honestly: what you can hand to an assistant such as Kai today, what is better done by hand in Bitrix24, and where an integrator is still needed.
TL;DR
- Connection is through a Bitrix24 inbound webhook, not OAuth as with amoCRM and Kommo. The webhook URL is an access key: treat it like a password; revoke it by deleting the webhook.
- Works: pipelines and stages, fields, deals, contacts, companies, tasks with deadlines, funnel analytics, a spec as PDF.
- Not yet: robots and other automations inside Bitrix24, widgets in the deal card.
- Notifications about the main events reach the Kai chat through Bitrix24's outgoing webhook.
- If robots are your main need, it is fairer to wait for the beta to end or use amoCRM/Kommo, where everything works.
What "beta" means and why it matters for Bitrix24
Bitrix24 is more than a CRM: it also holds tasks, a drive, chats, business processes and websites. The assistant works with the CRM part and tasks only. "Beta" means the core scenario works (describe the process → get a pipeline with fields, deals and tasks), but some of what Kai does for amoCRM and Kommo is not ported yet, above all automations inside Bitrix24. If you need structure and order in your data, connect now; if you need robots, read the limits section first.
Connecting in 5 minutes: the inbound webhook
With amoCRM and Kommo, Kai connects through one-click OAuth 2.0 and no passwords or keys change hands. Bitrix24 uses an inbound webhook for an external service that is not published in its Market. The steps:
- In your Bitrix24 portal open the developer section and create an inbound webhook; check the exact location in the Bitrix24 help centre.
- Give the webhook permissions for CRM and tasks. That is the minimum the assistant needs; other sections can stay unchecked.
- Copy the webhook URL and send it to the Kai chat: the Telegram bot @aiicrm_bot or the web chat.
- Kai checks the access and shows what it sees: pipelines, stages, fields, the number of deals and contacts. Now you can describe your process.
What Kai already configures in Bitrix24
- Pipelines and stages. Deal pipelines that mirror your process: 5–7 working stages, each a verifiable action by the rep.
- Fields. Custom fields on deals, contacts and companies: text, number, list, date, money. Lists for anything you will report on.
- Deals, contacts, companies. Created from a message or a voice note: "add the deal 'Smith, kitchen' for 12,000, contact Smith, phone…".
- Tasks with deadlines. A task on a deal with a due date straight from the chat, including one for every open deal without one.
- Funnel analytics. Deals per stage, where they get stuck, the most frequent loss reasons.
- Spec as PDF. The agreed plan becomes a technical specification for your team or the integrator who will build the robots.
- Notifications about the main events. Bitrix24 sends them through its outgoing webhook and Kai delivers them to the chat, for example about a new deal.
Every action goes through the official Bitrix24 REST API and looks in the portal as if an administrator had done it by hand, so everything created stays in your portal whether or not you keep using the assistant.
What Kai does not do in Bitrix24 yet, and what to do instead
| Job | Status in Kai | What to do now |
|---|---|---|
| Robots on stages: auto-tasks, owner changes, emails | No | Build them in the Bitrix24 robot designer by hand or with an integrator; Kai's spec is the list of rules. |
| Other automations inside Bitrix24 (business processes, triggers) | No | Same place; describe the rules in the Kai chat and carry them into the spec. |
| Widgets and apps in the deal card | No | Bitrix24 Market. |
| Event → action rules on Kai's side, as for amoCRM/Kommo | Notifications about the main events only | For event-driven auto-tasks, use Bitrix24 robots. |
| Telephony, open channels, Bitrix24 sites and stores | Not the assistant's job | Bitrix24 settings or a partner. |
The honest summary: today Kai for Bitrix24 is a "structure and order" tool, not an "automation" tool. For amoCRM and Kommo it is both.
When you still need an integrator
- You need robots and business processes; for now that is the beta's limit.
- Links to accounting software, telephony, a warehouse or a website with non-standard logic.
- Migration from another CRM with conversation history, tasks and files.
- Several departments with different processes and permissions to separate by role.
Kai helps here too: it works through the process with you, asks the questions an integrator asks in the first meeting and produces a spec as PDF, which makes the conversation with the contractor shorter and cheaper.
With Kai it is one message
Once the webhook is connected, a conversation with Kai is no different from one about amoCRM: you describe the business, it asks clarifying questions with answer options, shows a plan, creates everything through the API after you confirm and sends a report. Later changes are another message. Examples:
Set up a pipeline in Bitrix24 for B2B equipment sales: New enquiry → Qualified → Quote sent → Negotiation → Contract → Paid. Deal fields: Source (list), Budget (money), Quote date (date). For every open deal without a task, create a "next step" task due tomorrow.
Show how many deals sit at each stage and where they have been stuck for more than two weeks.
Prepare a spec as PDF for the integrator: which robots are needed at the "Quote sent" and "Contract" stages and what they should do.
Plans are the same as for amoCRM and Kommo: Start €29/month for one CRM; Pro €59/month, up to three CRMs, roles and integrations; Max €119/month, up to ten CRMs, priority and custom builds. The first 3 days are free, no card, about 25 requests on Start features: enough to test it on your own portal. Kai speaks English and Russian.
FAQ
Does Kai connect to Bitrix24 through OAuth like amoCRM?
No. Bitrix24 is connected through an inbound webhook that you create in your portal with permissions for CRM and tasks. The webhook URL is an access key, so treat it like a password; to revoke access, delete the webhook in Bitrix24. amoCRM and Kommo connect through one-click OAuth 2.0 with no keys.
Can Kai set up robots in Bitrix24?
Not yet. Robots, other automations and widgets inside Bitrix24 are not created; that is the main limit of the beta. Kai configures the structure, data and tasks and produces a spec as PDF, and you build the robots in the Bitrix24 designer yourself or with an integrator.
Will I get notifications about events from Bitrix24?
Yes, about the main events: Bitrix24 sends them through its outgoing webhook and Kai delivers them to the chat. Full event → action rules on Kai's side, as for amoCRM and Kommo, are not available for Bitrix24 yet.
Should I connect Bitrix24 to Kai now or wait?
If you need structure (pipelines, stages, fields), order in your data, tasks and analytics, connect now: it works, and 3 days free without a card is enough to test it on your portal. If automations inside Bitrix24 are your main need, it is fairer to wait for the beta to end or use amoCRM/Kommo, where the rules already work.
What next
Create an inbound webhook with CRM and task permissions, send the URL to Kai and ask it to show what it sees. If structure and data order are your pain, one evening closes it. If robots are, read the limits table again first.