# Bitrix24 CRM Break down the Bitrix24 funnel and find the leads you lost CRM для управления сделками, контактами и лидами ## How the agent works with Bitrix24 CRM The agent reaches the portal through an inbound webhook: its URL already carries both the address and the key, so requests go as REST methods like crm.deal.list straight into your Bitrix24, cloud or self-hosted. It reads deals, leads, contacts, companies and invoices, computes stage-by-stage conversion, rep activity for the period and closed amounts. Long lists are fetched page by page, and the portal can push events about deal creation and changes itself — then a reaction does not wait for the next poll. The funnel in Bitrix24 is torn in two: a lead and a deal are different entities, and converting a lead gives birth to a deal, a contact and a company at once. Counting conversion on deals alone means losing the top of the funnel, so the agent ties a lead to whatever it turned into. Stages are not universal either: every deal direction has its own set, and part of the meaning sits in custom fields — the agent reads those alongside the standard ones. For writes the agent creates tasks with a deadline and context and moves deals between stages, re-reading the card first: the portal does not lock a record against parallel edits. Before creating a contact or a company it looks for duplicates by phone and email: a repeat lead in Bitrix24 blocks nothing and happily lands on top of the existing base. Bulk import and duplicate search run noticeably slower than ordinary requests — the portal answers such methods reluctantly, and waiting beats running into a refusal. The webhook link is stored encrypted and is revoked in the same Developer resources, Other section; the portal asks for no separate authorization — the key rides inside the URL of every request. The request rate is kept low: the portal quota is shared with every other integration at once, so long selections are walked page by page rather than pulled in one go. If a method is closed by permissions or there were no deals in the period, it says so directly instead of handing over an empty table. ## Integration scenarios ### Funnel and lost lead breakdown The agent computes stage-by-stage conversion, finds leads with no owner and deals abandoned after the first touch. ### Weekly sales report The agent gathers closed deals, amounts and rep activity for the week and sends the summary to Telegram in time for the stand-up. ### Sync the CRM with the books The agent reconciles Bitrix24 deals with payments in the bank or 1C and shows which won deals were never paid. ### Tasks for stalled deals The agent finds deals with no tasks and no movement and creates tasks for the reps with a deadline and context. ### Duplicates in the client base The agent walks the contacts and companies, finds duplicates by phone and email and shows where one client was entered twice under different reps. ### New lead straight into chat The agent catches the new-lead event over a webhook, pulls up the card with its contacts and source and messages the rep on duty without waiting for a poll. ## How to connect **Before you connect** - A paid Bitrix24 plan: the REST API is closed on the free tier. - A Bitrix24 portal — cloud on *.bitrix24.ru or self-hosted on your domain. ### Sign in as a user who sees the whole CRM Open your portal at .bitrix24.com. A webhook runs with its creator's permissions: it sees the deals that employee sees. ### Create an inbound webhook "Applications → Developer resources", the "Ready-made scenarios" tab → "Other" → "Incoming webhook". ### Select the webhook permissions CRM alone is enough to read the funnel. Add "Tasks" to create tasks and move deals; scopes can be changed later too. ### Copy the webhook URL You need a link shaped like https://.bitrix24.com/rest/1// — with a trailing slash and no method name. ## FAQ ### How do I connect Bitrix24? With an inbound webhook: in Bitrix24 open Developer resources, then Other and Inbound webhook, pick the permissions and paste the resulting URL when connecting. The link is stored encrypted. ### What permissions does the webhook need? CRM read access is enough for analytics. If you want the agent to create tasks and move deals, add CRM write and Tasks. The scope can always be narrowed, and the agent will ask for what is missing when it hits a wall. ### Do cloud and on-premise Bitrix24 both work? Yes, the webhook mechanics are identical: a cloud portal on *.bitrix24.ru and a self-hosted box on your own domain both connect. ### Will the agent see deal changes right away? Yes, the agent reads the REST API at the moment of the task. On top of that the connector accepts webhooks about deal creation and changes, which you can hang automatic reactions on. [Open Bitrix24 CRM](https://www.bitrix24.ru)