CRM: Common Scenarios
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
CRM Integration begins with an application task: creating a customer or a deal, updating a card, retrieving lists, passing Sales Intelligence, or embedding an application interface.
Tutorials help you select a working scenario so you do not have to assemble a chain of methods manually. Each scenario specifies access permissions, the request order, identifiers to be passed between methods, a code sample, and the result to be verified.
Quick links: How to Choose a Direction and Common Scenarios
User documentation: CRM overview
Connection with CRM Objects
Scenarios work with core CRM objects and related data.
Leads, contacts, companies, and deals. Core customer and sales cards can be created, updated, and retrieved using the crm.lead.*, crm.contact.*, crm.company.*, and crm.deal.* methods.
Activities and Timeline. Calls, emails, meetings, tasks, and comments are linked to CRM cards via activity and timeline comment methods.
Company details, addresses, and line items. Related data is stored separately from the CRM card. These are created and linked to a customer, deal, or document using company details, addresses, line items, and catalog methods.
SPAs. Custom CRM types operate via entityTypeId — an object type identifier. To create items, pipelines, stages, and custom fields, use the universal crm.item.* methods.
Sales Intelligence. The source of inquiry and the customer route are passed to the CRM via UTM parameters, the TRACE field, or the crm.tracking.trace.add method.
CRM Widgets. An application interface can be embedded into a CRM card via a custom field or a tab. To register handlers, use the widgets methods and embedding points.
Getting Started
- Define the integration task: create an object, modify data, retrieve a list, pass analytics, or embed an interface.
- Select a direction in the How to Choose a Direction table.
- Open the overview for the selected direction and find a scenario for your task.
- Verify the access permissions and scopes specified in the scenario.
- Prepare the CRM object, field, stage, or user identifiers required for the requests.
- Execute the methods in the order described in the scenario.
How to Choose a Direction
|
If needed |
Open |
What you will find |
|
Create a lead, contact, company, deal, activity, document, or SPA item |
19 scenarios for creating CRM objects and related data. Main methods and groups: |
|
|
Change card fields, phones, email, activity date, activity link, or payment date |
10 scenarios for updating CRM data. Main methods and groups: |
|
|
Find duplicates, get activities, stages, pipelines, addresses, suppliers, or items by filter |
7 scenarios for retrieving data from CRM. Main methods and groups: |
|
|
Pass UTM tags, |
3 scenarios for passing analytics data. Main methods: |
|
|
Add the application interface to a CRM card |
2 scenarios for a lead custom field and a CRM card tab. Main methods and embedding points: |
Common Scenarios
The table below is a selection of tasks used to begin working with the CRM. For a full list of materials, see the direction overviews: add data, edit data, retrieve lists, Sales Intelligence, and CRM widgets.