Bitrix24 AI chatbot that writes leads and deals for you

What the Bitrix24 connection does

The Bitrix24 CRM integration links a MyChatBot assistant to your Bitrix24 account through a REST app you create. Once connected, the assistant creates and updates leads and contacts and creates deals in Bitrix24 mid-conversation, so nobody has to copy details from a chat into the CRM.

You set the scope. In Entities & Data Fields Configuration you turn on Leads and Deals and tick the standard and custom Bitrix24 fields the assistant is allowed to fill.

Three fields behave in a special way:

• Status is the lead’s stage. Values must match your Bitrix24 statuses exactly; Sync statuses pulls the current list.
• Source is set automatically to AI- plus your assistant’s name, so AI leads are easy to filter.
• Chat Link is added to every lead or deal, in the Comments field and in a dedicated Chat Link field.

For deals, you choose a pipeline in Select Pipeline, and new deals land there.

What the AI agent does inside Bitrix24

After connecting, the assistant gets four tools. You don’t run them by hand: the assistant decides when to use each one from your instructions.

1. create_crm_lead creates a lead from full_name (required), phone, Status and enabled custom fields. The contact is found or created by phone and linked, and the chat link is added.
2. edit_crm_lead updates the lead already tied to this customer: a new Status and any enabled fields.
3. create_crm_deal creates a deal from full_name and phone (both required), optional products and custom fields. Products are added, new ones created if needed, and the deal goes to your selected pipeline.
4. add_crm_client_contact creates or updates a contact with full_name and phone (both required). If the customer already has a lead, the contact is linked to it, and the MyChatBot profile stays in sync.

The phone number is the key: records are matched to a customer by phone, so when the assistant has the number, MyChatBot avoids creating duplicate contacts. Instructions are plain language, for example: when a customer shows interest, create a lead with name and phone and status New; when they confirm a purchase, create a deal with the chosen products.

Which channels feed Bitrix24

Integrations are configured per assistant, not per channel. Every channel connected to that assistant can produce Bitrix24 records, because the same assistant with the same tools answers on each of them.

That includes the Website Widget, WhatsApp, Telegram, Instagram, Facebook Messenger, TikTok, Viber, Gmail, SMS, OLX, Calls and the Webhooks API.

The chat link shows a manager which conversation a lead came from. When the assistant creates a deal in Bitrix24, a copy with the deal amount stays on the platform for analytics, linked to the conversation, so revenue can be filtered by agent and channel.

Running several assistants? Connect Bitrix24 to each one that should write to the CRM, or reuse an existing connection as a copy.

Example: from first message to a Bitrix24 record

An online store connects its assistant to Bitrix24 with Leads and Deals on and a pipeline selected. The status names below are examples; yours must match your funnel.

1. First message. A customer asks on Instagram whether a product is in stock. The assistant answers from its knowledge base.
2. Interest. The customer asks about delivery. As instructed, the assistant asks for a name and phone number.
3. Lead. The assistant calls create_crm_lead with full_name, phone and Status New. Bitrix24 gets a lead linked to a contact matched by phone, with source AI- plus the assistant’s name and a Chat Link.
4. Update. The customer wants a call back tomorrow morning. The assistant calls edit_crm_lead, sets Callback Requested and adds the time to the comments.
5. Deal. The customer confirms the order. The assistant calls create_crm_deal with full_name, phone and the chosen products, and the deal lands in the selected pipeline.
6. Manager. A manager opens the deal, follows the Chat Link and reads the whole conversation before calling.

Because each step is matched by phone, the lead, contact and deal stay tied to one customer, not three separate cards.

How to set it up

Setup has two sides: a REST app in Bitrix24 and a connection in MyChatBot. Every screen is covered in the Bitrix24 CRM integration guide. In short:

1. As a Bitrix24 administrator, fill in the Registration of technology partnership form on vendors.bitrix24.com.
2. In My Applications, click Add Application, choose Worldwide, create an app with Use Rest API and set the Application URL to https://app.mychatbot.app/integration?integration=Bitrix.
3. Click Test to get the Client ID and Client Secret, enter your domain and install the app.
4. In MyChatBot, open Integrations, select the assistant, find Bitrix24 CRM, click Connect, enter Domain, Client ID and Client Secret, and Submit.
5. Turn on Leads and Deals, tick fields, click Apply fields, pick a pipeline and click Sync statuses.
6. Tell the assistant in its instructions when to create or update leads and deals.

Then message the assistant on a connected channel, leave a name and phone, and check that the lead shows up in Bitrix24.

Requirements and limits

• Admin access. Creating the REST app needs Bitrix24 administrator rights and the technology partnership registration.
• Plan. CRM integrations, Bitrix24 among them, are added on the Pro plan and carry over to Multipro and Corporate. On Standard, or with no active plan, the card shows PRO and can’t be selected. See pricing.
• One CRM per assistant. While Bitrix24 is connected, other CRM systems are greyed out for that assistant.
• Exact statuses. A status must match Bitrix24 character for character, or the update fails. Re-run Sync statuses after changing your funnel.
• One-way stage sync. Sync statuses copies Bitrix24 stages into MyChatBot and changes nothing in Bitrix24. Dragging a card on the MyChatBot Leads board does not move the Bitrix24 deal.
• Phone. Deals and contacts require a phone, and matching works by phone, so collect it early.
• Currency. Deal amounts copied for analytics use the currency your CRM sends, with no conversion.