Bitrix24 AI: CoPilot and the 600-Request Hourly Ceiling
If you searched “Bitrix24 AI,” you’re either being pitched CoPilot inside your own portal or trying to work out whether Bitrix24 can talk to the AI tools you already pay for. Both answers are more interesting than the marketing page suggests, and the second one changed recently.
CoPilot is a writing layer bolted onto seven products
Bitrix24 brands its AI as CoPilot and ships it across the suite rather than as one assistant. Per Bitrix24’s own CoPilot page, the pieces are:
- CoPilot in CRM — “call audio-to-text transcription, call summary, field autocompletion in deals.” The field autocompletion is the useful bit: it reads a call and fills name, phone, and company on the deal.
- CoPilot in Video Calls — “AI-powered call transcription, analysis, summary, and recommendations,” with timestamped transcripts and follow-up actions.
- CoPilot in Tasks — “AI-generated task descriptions, task summaries, checklists, comments.”
- CoPilot in Chat and Feed — thread summaries, drafted replies, translation, and idea generation, triggered from the menu or by hitting the spacebar.
- CoPilot in Sites & Stores — page copy and AI-generated images from a prompt.
Bitrix24’s FAQ confirms the scope: CoPilot is available in “Feed, Tasks, Chat, CRM, Mail, Calendar, and Websites,” and “all employees in your Bitrix24 account can use CoPilot.” You can switch it off per section under Settings → CoPilot preferences rather than all-or-nothing.
Notice the shape of that list. Every item is summarize, draft, transcribe, or translate — things that happen when a human is already looking at the screen. None of it is “watch the pipeline and act.”
The metering is a shared hourly pool, not a per-seat allowance
This is the detail worth knowing before you build any process around CoPilot, and it’s buried in a help article rather than on the pricing page.
Bitrix24’s CoPilot request limit documentation is blunt: “CoPilot supports up to 600 requests per hour across all users in your Bitrix24 account.” It is not 600 per user. It’s 600 for the whole portal, and Bitrix24 states plainly that “it applies to all plans, including both Cloud and On-Premise versions.”
The recovery model is a rolling window, not a reset: “Each request uses one slot for one hour. After that, the slot is released and becomes available again,” and “slots continue to free up gradually, one hour after each request was made.” When you’re out, “you won’t be able to send new ones until slots become available.”
For a five-person agency that ceiling is invisible. For a 40-seat sales floor where every rep is summarizing calls and autofilling deals, 600 an hour is roughly 15 requests per person per hour — reachable on a busy Tuesday, and the person who hits the wall is whoever happens to click next. If you’re planning to make CoPilot part of a required workflow, plan for the pool being shared, and don’t design a process that assumes it’s always available.
Bitrix24 also notes it stores CoPilot data “for up to 14 days for technical purposes” before deleting it, and that requests go to third-party model providers under their own policies. Worth knowing if you handle client data under an agency NDA.
Bitrix24 runs two different MCP servers, and people confuse them
This is the part that’s genuinely new and where most write-ups get it wrong. There are two, they do unrelated things, and only one touches your data.
The account MCP server — https://mcp.bitrix24.com/mcp/. Bitrix24’s help documentation is explicit: “Bitrix24 lets you connect to external AI systems like ChatGPT or Manus AI using the MCP server.” An administrator turns it on first under Settings (⚙️) → MCP servers → “Allow connection of external AIs to Bitrix24,” which is off by default. ChatGPT connects by OAuth through its developer mode Create app flow; tools like Manus AI connect by generating a token under Applications → MCP connections. The action set is still small — task creation with names, deadlines, and assignees is the documented example — and Bitrix24 says it “will continue to add more integrations, features, and supported actions over time.”
So: there is no Bitrix24 entry in ChatGPT’s or Claude’s built-in connector directory. What exists is a first-party MCP endpoint you add yourself as a custom connector. That’s a real integration, but it’s a self-serve wiring job, not a one-click toggle.
The developer docs MCP server — https://mcp-dev.bitrix24.com/mcp. Entirely different animal. It serves Bitrix24’s REST API documentation — method descriptions, parameters, usage hints — to coding assistants, so the model stops, in Bitrix24’s words, “invent[ing] REST methods.” It supports Claude Desktop, Claude Code, Cursor, Codex, GitHub Copilot Chat, and Gemini Code Assist. It contains none of your CRM data. If you’re building an integration, connect it; if you want an assistant that reads your deals, it’s the wrong URL.
Scheduled work is no longer the dividing line — ChatGPT and Claude both run tasks on a timer without anyone watching. The line that still holds is event triggers. Nothing kicks off because something happened in one of your apps; it kicks off because the clock said so, which means anything time-sensitive waits for the next run.
That limitation is why the MCP path, useful as it is, doesn’t finish the job. Connecting ChatGPT to Bitrix24 means you can ask it to create a task. It does not mean a lost deal produces a follow-up on its own.
The webhook layer is where Bitrix24 gets genuinely good
Bitrix24’s REST API is old, wide, and — unusually for CRM software at this price — reachable without a partner agreement.
An inbound webhook is created from Applications → Developer resources → Ready-made scenarios → Other → Incoming webhook, documented at apidocs.bitrix24.com. You tick the scopes it’s allowed to use in the Assign permissions block — crm, task, im, telephony, calendar, user, disk are the ones most agencies want — and Bitrix24 issues a URL that acts as the key. It “does not have an expiration date (unlike OAuth 2.0 authorization tokens),” which is convenient and also means the URL is the credential: anyone who gets it has your ticked permissions. Treat it like a password.
Outbound webhooks are the half that matters more. They fire when Bitrix24 data changes and POST to a handler you specify, with a verification token so you can confirm the request came from your portal. On the CRM side that includes onCrmDealAdd (“when a deal is created manually or via the method crm.deal.add”), onCrmDealUpdate, and onCrmDealDelete, with parallel events for leads, contacts, and companies.
One trap the docs make you read carefully for: onCrmDealMoveToCategory — the funnel change event — cannot be subscribed to via an outgoing webhook at all. It’s only reachable through an application using event.bind. If your automation depends on “deal moved to a different pipeline,” the simple webhook path won’t see it and you’ll be debugging a silence.
Paste an inbound webhook URL into Carly at carlyassistant.com/integrations as a bring-your-own-key connection and point an outbound webhook at a Carly workflow, and you have both directions: something that hears deal changes and something that can write back into CRM, tasks, and chat.
What agency owners actually build on top of it
The patterns that pay for themselves are the ones CoPilot structurally can’t do, because they start with an event rather than a click:
- A deal sits in the same stage past its normal dwell time — pull the last call transcript and the email thread, and draft the specific next message to that client, not a generic nudge.
onCrmDealAddfires from a web form — enrich the company, check whether they’re already a contact under a different spelling, and route to the right account manager before anyone opens the record.- A client’s retainer hours cross 80% mid-month — a task lands on the account lead with the overage breakdown attached, while there’s still time to have the conversation.
- Friday: every deal that changed stage this week, summarized per account manager, in one message rather than five dashboard tabs.
In Carly, the trigger-and-branch plumbing under those is the free, unlimited Zapier-style workflow layer; the AI agents that read the transcripts and write the drafts start at $35/month. The contrast with CoPilot’s shared 600-per-hour pool is worth doing your own arithmetic on before you commit a team process to either.
If you’re comparing Bitrix24’s AI against the field, best AI CRM tools covers the category, and AI agents for agency owners has the setups in more detail.
FAQ
What is Bitrix24 CoPilot? CoPilot is Bitrix24’s built-in AI, available across Feed, Tasks, Chat, CRM, Mail, Calendar, and Websites. It transcribes and summarizes calls, autofills deal fields, drafts task descriptions and checklists, summarizes chat threads, translates text, and generates website copy and images.
How is Bitrix24 CoPilot metered? By a shared hourly request pool, not per-seat credits. Bitrix24 documents a limit of 600 CoPilot requests per hour across all users in an account, on every plan including cloud and on-premise. Each request holds a slot for one hour, then the slot frees up.
Does Bitrix24 have an MCP server?
Two. https://mcp.bitrix24.com/mcp/ connects external AI systems like ChatGPT and Manus AI to your account data, and must be enabled by an admin under Settings → MCP servers. https://mcp-dev.bitrix24.com/mcp serves the REST API documentation to coding assistants and holds no account data.
Is Bitrix24 in the ChatGPT or Claude connector directory? No. Neither vendor ships a prebuilt Bitrix24 connector. ChatGPT reaches Bitrix24 by adding the account MCP server as a custom app in developer mode, which requires ChatGPT Plus or Pro.
Can an ordinary admin get Bitrix24 API access? Yes. Inbound webhooks are self-serve from Applications → Developer resources → Ready-made scenarios → Other → Incoming webhook, with per-scope permissions and a key that doesn’t expire. There is no application or approval queue.
Which Bitrix24 CRM events fire outbound webhooks?
onCrmDealAdd, onCrmDealUpdate, and onCrmDealDelete, plus the equivalents for leads, contacts, and companies. onCrmDealMoveToCategory, which fires on a funnel change, is not available to outgoing webhooks and requires an application using event.bind.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
