> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Bitrix24
> Manage leads, contacts, companies, and calendar with the Bitrix24 CRM from Brain Studio.
**Bitrix24** is an all-in-one CRM and business management platform. In **Brain Studio**, this integration lets your flows and agents manage leads, contacts, companies, and calendar events directly from conversations.
## What Bitrix24 enables
When you connect **Bitrix24**, you can:
* **Capture** leads from WhatsApp conversations or other channels with enriched data
* **Query** existing contacts and companies to respond with CRM context
* **Update** pipeline status based on each conversation's real progress
* **Convert** qualified leads into contacts and companies without manual entry
* **Schedule** sales meetings directly in the Bitrix24 calendar from the flow
***
## Installation
### Prerequisites
1. An **active Bitrix24 account**.
2. A **paid** Bitrix24 plan with access to **inbound webhooks**. This module is not available on the free account.
3. Permissions to create or edit integrations from **Applications -> Developer resources**.
### How to get credentials
To connect **Bitrix24** in Brain Studio, you need the **Webhook URL** of an **inbound webhook** with permissions for the modules used by this integration.
In Bitrix24's left menu, go to **Applications**.
Inside **Applications**, open **Developer resources**.
In the developer resources screen, open the **Other** category.
Click **Inbound webhook** to open webhook settings for Brain Studio.
At the top you will see **Webhook to call REST API**. Copy the full URL.
This URL allows actions in Bitrix24 with the webhook's assigned permissions. Store it as sensitive credentials and never expose it in public code or shared channels.
In **Assign permissions**, select:
* **CRM (`crm`)**
* **Calendar (`calendar`)**
With these permissions, you can use the **lead, contact, company, event, and calendar section** tools available in Brain Studio.
Click **Save** to activate the webhook with selected permissions.
### How to connect it
The most direct way is to use [**Jelou Agent**](/en/guides/getting-started/jelou-agent): describe what you need and the agent connects **Bitrix24** automatically inside the flow.
If you prefer manual installation, open **Marketplace** and follow these steps with the Webhook URL from the previous step.
In Brain Studio, open **Marketplace** from the left menu.
Find the integration and click **Connect**.
Fill out the form with your Bitrix24 **Webhook URL**.
The integration appears as **connected**.
You can use it in **Canvas** or add it as a tool in **AI Agent**.
***
## Available tools
At a high level, actions are grouped as:
* **Create** - lead, contact, company, calendar event, calendar section.
* **Query** - get and list leads, contacts, companies, events, and sections.
* **Update** - lead, contact, company, calendar section.
* **Delete** - lead, contact, company, event, and calendar section.
The integration exposes 23 tools in Brain Studio. Below is each one with purpose, inputs, and example.
Creates a new lead in Bitrix24 CRM to capture potential clients or sales opportunities. Returns the created **lead ID**.
**Inputs:**
* **title** (string, required) - Lead title.
* **name** (optional, string) - Contact first name.
* **last\_name** (optional, string) - Contact last name.
* **company\_title** (optional, string) - Company name.
* **phone** (optional, string) - Phone number.
* **phone\_type** (optional, string) - Phone type (default `"WORK"`).
* **email** (optional, string) - Email address.
* **email\_type** (optional, string) - Email type (default `"WORK"`).
* **status\_id** (optional, string) - Lead status (for example `"NEW"`, `"IN_PROCESS"`).
* **source\_id** (optional, string) - Lead source (for example `"WEB"`, `"CALL"`).
* **opportunity** (optional, string) - Estimated deal amount.
* **currency\_id** (optional, string) - Currency code (for example `"USD"`, `"EUR"`).
* **assigned\_by\_id** (optional, string) - Responsible user ID.
* **comments** (optional, string) - Additional comments.
**Example:**
```json theme={null}
{
"title": "Interested in Enterprise plan",
"name": "Juan",
"last_name": "Pérez",
"phone": "+573001234567",
"email": "juan@empresa.com",
"source_id": "WEB",
"opportunity": "5000",
"currency_id": "USD"
}
```
Returns full information for a specific lead by ID.
**Inputs:**
* **id** (string, required) - Lead ID.
**Example:**
```json theme={null}
{
"id": "42"
}
```
Lists CRM leads with optional filters. Returns paginated results.
**Inputs:**
* **status\_id** (optional, string) - Filter by status (for example `"NEW"`, `"IN_PROCESS"`).
* **source\_id** (optional, string) - Filter by source.
* **assigned\_by\_id** (optional, string) - Filter by owner.
* **start** (optional, string) - Pagination offset.
**Example:**
```json theme={null}
{
"status_id": "NEW",
"start": "0"
}
```
Updates an existing lead. Only fields included in the request are modified.
**Inputs:**
* **id** (string, required) - Lead ID to update.
* **title** (optional, string) - New title.
* **phone** (optional, string) - New phone number.
* **phone\_type** (optional, string) - Phone type (default `"WORK"`).
* **email** (optional, string) - New email.
* **email\_type** (optional, string) - Email type (default `"WORK"`).
* **status\_id** (optional, string) - New status.
* **opportunity** (optional, string) - New estimated amount.
* **comments** (optional, string) - New comments.
**Example:**
```json theme={null}
{
"id": "42",
"status_id": "IN_PROCESS",
"opportunity": "8000"
}
```
Permanently deletes a lead from CRM.
This action cannot be undone.
**Inputs:**
* **id** (string, required) - Lead ID to delete.
**Example:**
```json theme={null}
{
"id": "42"
}
```
Creates a new contact in Bitrix24 CRM. Contacts represent people you do business with. Returns the created **contact ID**.
**Inputs:**
* **name** (optional, string) - First name.
* **last\_name** (optional, string) - Last name.
* **phone** (optional, string) - Phone number.
* **phone\_type** (optional, string) - Phone type (default `"WORK"`).
* **email** (optional, string) - Email.
* **email\_type** (optional, string) - Email type (default `"WORK"`).
* **post** (optional, string) - Job title or position.
* **company\_id** (optional, string) - Associated company ID.
* **source\_id** (optional, string) - Contact source.
* **assigned\_by\_id** (optional, string) - Owner ID.
* **comments** (optional, string) - Comments.
**Example:**
```json theme={null}
{
"name": "María",
"last_name": "García",
"phone": "+573009876543",
"email": "maria@empresa.com",
"post": "Procurement Manager",
"company_id": "10"
}
```
Returns full information for a specific contact by ID.
**Inputs:**
* **id** (string, required) - Contact ID.
**Example:**
```json theme={null}
{
"id": "15"
}
```
Lists CRM contacts with optional filters. Returns paginated results.
**Inputs:**
* **company\_id** (optional, string) - Filter by company.
* **source\_id** (optional, string) - Filter by source.
* **assigned\_by\_id** (optional, string) - Filter by owner.
* **start** (optional, string) - Pagination offset.
**Example:**
```json theme={null}
{
"company_id": "10",
"start": "0"
}
```
Updates an existing contact. Only fields included in the request are modified.
**Inputs:**
* **id** (string, required) - Contact ID to update.
* **name** (optional, string) - First name.
* **last\_name** (optional, string) - Last name.
* **phone** (optional, string) - Phone number.
* **phone\_type** (optional, string) - Phone type (default `"WORK"`).
* **email** (optional, string) - Email.
* **email\_type** (optional, string) - Email type (default `"WORK"`).
* **post** (optional, string) - Role.
* **comments** (optional, string) - Comments.
**Example:**
```json theme={null}
{
"id": "15",
"post": "Operations Director",
"phone": "+573001112233"
}
```
Permanently deletes a contact from CRM.
This action cannot be undone.
**Inputs:**
* **id** (string, required) - Contact ID to delete.
**Example:**
```json theme={null}
{
"id": "15"
}
```
Creates a new company in Bitrix24 CRM. Companies represent organizations you do business with. Returns the created **company ID**.
**Inputs:**
* **title** (string, required) - Company name.
* **company\_type** (optional, string) - Company type (for example `"CUSTOMER"`, `"SUPPLIER"`).
* **industry** (optional, string) - Industry code.
* **phone** (optional, string) - Phone number.
* **phone\_type** (optional, string) - Phone type (default `"WORK"`).
* **email** (optional, string) - Email.
* **email\_type** (optional, string) - Email type (default `"WORK"`).
* **web** (optional, string) - Website.
* **address** (optional, string) - Address.
* **assigned\_by\_id** (optional, string) - Owner ID.
* **comments** (optional, string) - Comments.
**Example:**
```json theme={null}
{
"title": "ABC Company S.A.",
"company_type": "CUSTOMER",
"phone": "+573001112233",
"email": "info@empresaabc.com",
"web": "https://empresaabc.com"
}
```
Returns full information for a specific company by ID.
**Inputs:**
* **id** (string, required) - Company ID.
**Example:**
```json theme={null}
{
"id": "8"
}
```
Lists CRM companies with optional filters. Returns paginated results.
**Inputs:**
* **company\_type** (optional, string) - Filter by type.
* **industry** (optional, string) - Filter by industry.
* **assigned\_by\_id** (optional, string) - Filter by owner.
* **start** (optional, string) - Pagination offset.
**Example:**
```json theme={null}
{
"company_type": "CUSTOMER",
"start": "0"
}
```
Updates an existing company. Only fields included in the request are modified.
**Inputs:**
* **id** (string, required) - Company ID to update.
* **title** (optional, string) - Name.
* **company\_type** (optional, string) - Type.
* **industry** (optional, string) - Industry.
* **phone** (optional, string) - Phone number.
* **phone\_type** (optional, string) - Phone type (default `"WORK"`).
* **email** (optional, string) - Email.
* **email\_type** (optional, string) - Email type (default `"WORK"`).
* **address** (optional, string) - Address.
* **comments** (optional, string) - Comments.
**Example:**
```json theme={null}
{
"id": "8",
"address": "Calle 100 #15-20, Bogotá",
"company_type": "SUPPLIER"
}
```
Permanently deletes a company from CRM.
This action cannot be undone.
**Inputs:**
* **id** (string, required) - Company ID to delete.
**Example:**
```json theme={null}
{
"id": "8"
}
```
Creates a new event in Bitrix24 calendar. Returns the created **event ID**.
**Inputs:**
* **name** (string, required) - Event name.
* **from** (string, required) - Start date/time (ISO 8601, for example `"2025-06-15T10:00:00"`).
* **to** (string, required) - End date/time (ISO 8601).
* **section\_id** (string, required) - Calendar section ID where event is created.
* **type** (optional, string) - Calendar type (for example `"user"`, `"group"`, `"company"`).
* **owner\_id** (optional, string) - Calendar owner ID.
* **description** (optional, string) - Event description.
* **location** (optional, string) - Location.
* **importance** (optional, string) - Event importance (default `"high"`).
* **accessibility** (optional, string) - Availability status (default `"busy"`).
* **is\_meeting** (optional, string) - Whether this is a meeting with attendees.
* **attendees** (optional, array) - Attendee user IDs.
**Example:**
```json theme={null}
{
"name": "Demo with potential client",
"from": "2025-06-15T10:00:00",
"to": "2025-06-15T11:00:00",
"section_id": "3",
"location": "Meeting room",
"importance": "high"
}
```
Returns full information for a specific calendar event by ID.
**Inputs:**
* **id** (string, required) - Event ID.
**Example:**
```json theme={null}
{
"id": "101"
}
```
Lists calendar events with date-range and section filtering.
**Inputs:**
* **from** (optional, string) - Range start date (ISO 8601).
* **to** (optional, string) - Range end date (ISO 8601).
* **type** (optional, string) - Calendar type (for example `"user"`, `"group"`).
* **owner\_id** (optional, string) - Calendar owner ID.
* **section** (optional, array) - Section IDs to filter.
**Example:**
```json theme={null}
{
"from": "2025-06-01",
"to": "2025-06-30"
}
```
Permanently deletes a calendar event.
This action cannot be undone.
**Inputs:**
* **id** (string, required) - Event ID to delete.
**Example:**
```json theme={null}
{
"id": "101"
}
```
Creates a new calendar section in Bitrix24. Returns the created **section ID**.
**Inputs:**
* **name** (string, required) - Section name.
* **type** (optional, string) - Calendar type (default `"user"`).
* **owner\_id** (optional, string) - Owner ID.
* **description** (optional, string) - Section description.
* **color** (optional, string) - Background color in hex format (for example `"#9cbeee"`).
* **text\_color** (optional, string) - Text color in hex format.
**Example:**
```json theme={null}
{
"name": "Client meetings",
"type": "user",
"color": "#5bc8e2",
"description": "Demo and sales follow-up events"
}
```
Lists available calendar sections.
**Inputs:**
* **type** (optional, string) - Calendar type to query (for example `"user"`, `"group"`).
* **owner\_id** (optional, string) - Calendar owner ID.
**Example:**
```json theme={null}
{
"type": "user"
}
```
Updates an existing calendar section. Only fields included in the request are modified.
**Inputs:**
* **id** (string, required) - Section ID to update.
* **name** (optional, string) - New name.
* **type** (optional, string) - Calendar type (default `"user"`).
* **owner\_id** (optional, string) - Owner ID.
* **description** (optional, string) - New description.
* **color** (optional, string) - New background color (hex).
* **text\_color** (optional, string) - New text color (hex).
**Example:**
```json theme={null}
{
"id": "3",
"name": "Demos and follow-up",
"color": "#f4c542"
}
```
Permanently deletes a calendar section.
This action will delete all events in this section and cannot be undone.
**Inputs:**
* **id** (string, required) - Section ID to delete.
**Example:**
```json theme={null}
{
"id": "3"
}
```
***
## How to use in Brain
Once connected, you can use **Bitrix24** in two surfaces:
### In AI Agent
Best when users want to create leads, update contacts, or query CRM in natural language.
In Canvas, select or add the **AI Agent** node.
In the right panel, open the **Tools** tab.
Use **Add tool**, search for **Bitrix24**, and enable it.
Choose full integration or enable only the modules you need (CRM, calendar).
**Bitrix24** appears in the agent's tools list, and you can open its settings with the gear icon.
The agent will automatically decide when to create a lead, query a contact, or register an event based on the conversation.
### In Canvas
Best when you need full control of the flow (for example: qualify lead -> create contact -> assign owner -> notify).
In the left panel, open **Marketplace** and drag **Bitrix24** into the flow.
With the node selected, in **Tools** choose the action (for example **Create lead**).
Fill in the JSON request body and, if needed, **Save response** in a memory variable.
Link **Task completed** and **There was an error** outputs to the next nodes.
The node is ready to run in the order defined by your flow.
**Configuration example:**
The node editor shows a JSON body aligned with the **Create lead** tool. `title` and `phone` are the minimum recommended fields to identify the prospect.
```json theme={null}
{
"title": "WhatsApp lead - {{$memory.nombre_cliente}}",
"name": "{{$memory.nombre_cliente}}",
"phone": "{{$memory.telefono}}",
"email": "{{$memory.email}}",
"source_id": "WEB",
"opportunity": "{{$memory.monto_estimado}}",
"currency_id": "USD"
}
```
***
## Use cases
The agent runs a qualification conversation and creates the lead in Bitrix24 with all relevant captured data, before the prospect has spoken to any human.
**Typical flow:**
* Prospect starts conversation on WhatsApp
* The agent goes through qualification questions: need, budget, timeline, and authority
* When qualification is complete, the flow creates the lead with **Create Lead**, including name, company, estimated amount, source, and comments with conversation summary
* It is automatically assigned to a sales rep based on business criteria
**Impact:**
* The lead reaches CRM with full context, not just name and phone
* The sales team receives pre-qualified prospects ready to close
* Reduces risk of losing leads due to delay or forgotten manual entry
**Ideal for:** real estate, insurance, education, and financial services with WhatsApp lead acquisition.
The agent moves the lead through Bitrix24 pipeline stages as it detects progress signals in conversation, without reps manually updating CRM.
**Typical flow:**
* Prospect shows initial interest -> flow updates lead to `IN_PROCESS` with **Update Lead**
* Prospect asks for proposal or demo -> flow updates `status_id` and estimated amount
* Prospect confirms purchase intent -> flow converts the lead by creating contact with **Create Contact** and company with **Create Company**
* Sales rep sees real-time pipeline updates in Bitrix24
**Impact:**
* Pipeline always reflects real status without relying on team discipline
* Sales managers get accurate visibility for revenue forecasting
**Ideal for:** B2B sales teams with defined Bitrix24 pipelines and high conversation volume.
When a known customer contacts you on WhatsApp, the agent identifies them in CRM, retrieves data, and responds with context: company, active leads or deals, and assigned team contact.
**Typical flow:**
* Customer sends a WhatsApp message
* Flow searches Bitrix24 by phone or email with **List Contacts**
* If found, it retrieves full contact data with **Get Contact** and company data with **Get Company**
* Agent responds with personalized context or transfers to assigned rep with a ready briefing
**Impact:**
* Agent checks CRM before asking, so customers do not repeat known information
* Rep receives transfer with full context, not just "someone wants to talk"
* Smoother customer experience for recurring accounts
**Ideal for:** B2B companies with an active customer portfolio managed in Bitrix24.
When a lead passes qualification threshold, the flow creates contact, company, and the first sales meeting in Bitrix24 in a chained sequence, without manual intervention.
**Typical flow:**
* Agent detects close signal in conversation (proposal request, budget confirmation, etc.)
* Flow creates contact with **Create Contact** and company with **Create Company**
* It offers available slots and, once confirmed, creates event with **Create Event** in assigned rep calendar
* Rep receives notification with prospect briefing
**Impact:**
* Removes three manual post-qualification steps: create contact, create company, schedule meeting
* Time between qualification and first meeting drops from hours/days to minutes
**Ideal for:** companies with short to mid sales cycles where response speed is a key differentiator.
Before a meeting, the sales rep asks the agent and gets a full customer summary directly in chat, without opening Bitrix24.
**Typical flow:**
* Rep asks the agent "what do I know about the 3pm customer?"
* Flow queries event with **List Events**, identifies attendee, and retrieves profile with **Get Contact** and **Get Company**
* If there are active related leads, it retrieves them with **Get Lead**
* Returns structured summary: company, role, contact history, active opportunity, and notes
**Impact:**
* Rep enters meetings prepared without spending time navigating CRM
* Fewer mistakes from confusing customers or lacking context across many accounts
**Ideal for:** sales teams with dense calendars and multiple active Bitrix24 accounts.
***
## Integrations that pair well with Bitrix24
Send **follow-ups and confirmations** by email after creating or updating a lead in CRM.
[Gmail documentation](/en/guides/integraciones/productividad/gmail)
Sync **team meetings** between Bitrix24 and Google Calendar for teams using mixed tools.
[Google Calendar documentation](/en/guides/integraciones/agendamiento/google-calendar)
Notify the sales team when a **new lead** is created or a **deal stage** changes.
[Slack documentation](/en/guides/integraciones/productividad/slack)
Export **leads or contacts** to a spreadsheet for **management reporting** or pipeline tracking.
[Google Sheets documentation](/en/guides/integraciones/productividad/google-sheets)
***
## Related articles
Catalog of integrations available in Marketplace.
General flow to install and use integrations in Brain Studio.
The agent will automatically decide when to create a lead, query a contact, or register an event based on the conversation.
### In Canvas
Best when you need full control of the flow (for example: qualify lead -> create contact -> assign owner -> notify).
***
## Use cases