Bitrix24 CRM integration
The conversation ends and the CRM is already up to date. Your assistant creates the contact, records the company, opens a lead when there is real intent, leaves your team an internal note, and books the follow-up as a task.
Connecting Bitrix24
Register a Local Application in your portal
This is the one integration with real setup: Bitrix24 needs an application created inside your own portal, with CRM and Tasks permissions granted. The guide walks through it step by step, including which paths to fill in.
Collect three values
Your portal domain — the company.bitrix24.com one — plus the application's Client ID and Client secret from its settings page.
Paste them into the assistant
Open the assistant, turn on Enable integration, choose Bitrix24 CRM, and enter the three values in the connection window.
Authorise in your portal
You are redirected to your own Bitrix24 to approve the application's permissions, and sent back. The integration is live from that moment.
Set the two groups, then run a conversation
Decide what the assistant may do in front of a customer and what only you may ask of it. Then play a customer in the Playground and go look at what appeared in the CRM.
Where the pipeline leaks
The lead exists only in a chat log
Somebody asked a real buying question at eleven at night. It is in the widget history, not in the funnel, and by the time anyone reads it the person has bought elsewhere.
Entering it afterwards is nobody's favourite job
Name, phone, company, what they wanted, what you promised. Typed out after the fact, from memory, if at all — which is why half the fields in any CRM are empty.
Duplicates pile up quietly
Every form that writes straight into the CRM creates a new record each time. The same customer appears three times under two spellings, and your reports quietly stop meaning anything.
The follow-up is remembered by a person
"Call them Friday" lives in somebody's head or on a sticky note. It is the cheapest thing in the world to automate and the most expensive thing to forget.
Two groups of tools, and you decide what goes in each
Bitrix24 in Mingleego is eleven tools, and they are deliberately split in two, because the two halves are used by different people. The Customer group is what may happen while the assistant is talking to a visitor: create a contact, update a contact, create a company, create a lead. The assistant collects the details the way a person would — the name comes up early, the phone when it is actually needed — and confirms the important fields before writing them. The User group is for you, the owner of the CRM: search contacts, companies and leads; leave an internal comment on any of the three; create a task. The searches also do quiet work in the background — the assistant looks for an existing record before creating a new one, which is what keeps the duplicates out. The comments are the underrated half. An internal note on a lead is where the context goes: what the customer actually asked, what was promised, which objection came up. It is visible to your team and invisible to the customer, and it is the difference between a CRM record and a name with a phone number next to it.
What it looks like in practice
A night-time lead, in the funnel by morning
The widget takes the question, records the contact, opens the lead and notes what the person actually wanted.
Every channel writes to one portal
Telegram, WhatsApp, Instagram, the site widget — one assistant, one Bitrix24. No per-channel exports and no separate inboxes.
The callback becomes a task
"Call me back on Friday" turns into a Bitrix24 task with a responsible person attached, in the same conversation that produced it.
Looking someone up without opening the CRM
In the Playground: find this contact, show me the open leads for that company, add a note about the call.
CRM plus your own documents
With document search on, the assistant answers from your price list or policy while it is recording who asked.
In the language they wrote in
The language is detected from the message. A Ukrainian enquiry gets a Ukrainian answer and a correctly filled record.
The eleven tools
Create and update contacts
The assistant gathers name, phone and email over the conversation rather than as a form, confirms the important fields, and writes the record. If the person already exists, it updates instead of adding a second one.
Create a lead
Not for every conversation — for the ones that show real buying intent. That is the record your sales team works from, created at the moment the interest was expressed rather than the morning after.
Create a company
For conversations with a business dimension: a B2B enquiry, a partnership, a corporate request. The organisation is recorded alongside the person.
Search contacts, companies and leads
By name, email, phone or partial match. Used both when you ask the assistant to find someone, and quietly before it creates anything — which is how the duplicates are avoided.
Internal comments on any record
A note on the contact, the company or the lead: what was asked, what was promised, what the objection was. Your team sees it, the customer never does.
Create a task
Title, description and a responsible person. When the conversation produces a clear next action — a callback, a document to prepare, a check-in — it becomes a task instead of a good intention.
Before you connect your portal
Yes, for Bitrix24 specifically. It needs a Local Application registered in your own portal with CRM and Tasks permissions, and you copy its Client ID and secret into the connect window. It is the only integration here with that requirement — HubSpot, Slack, Notion and Calendly all use a managed application and need no setup at all.
Let the CRM fill itself in
One Local Application, three values, and every conversation on every channel starts landing in Bitrix24 as a contact, a lead and a task.
Create an assistant