Bitrix24
CRMConnect AI agents to a Bitrix24 portal. Agents run full CRUD on leads, contacts, companies, and deals, post timeline comments and activities, manage tasks and notifications, and reach any of 600+ REST methods through a generic call action.
What This Integration Enables
Bitrix24 puts the whole front office in one portal: CRM, tasks, notifications, and several hundred REST methods behind them. This connector gives FlowRunner agents full create, read, update, and delete access to leads, contacts, companies, and deals, plus timeline comments, activities, tasks, and the portal's notification center. For anything the dedicated actions do not cover, Call REST Method reaches the rest of the API surface, products, quotes, disk, telephony, from the same governed workflow. The governance point matters most at the destructive edge. In Bitrix24, deleting a lead or deal also deletes its timeline, which is the recorded history of every conversation and step. FlowRunner agents do the capturing, logging, and reconciling all day. The deletions wait for a [human-in-the-loop](/concepts/human-in-the-loop) decision, because the timeline cannot be rebuilt.
Without FlowRunner
With FlowRunner
Use Case Scenarios
No prospect dies in the inbox
A prospect writes to the shared inbox monitored through [Gmail](/integrations/gmail-service). The agent parses the message, checks List Leads and List Contacts for an existing record, and calls Create Lead with the source, the request summary, and the custom fields the sales team actually filters on, discovered at runtime with Get Lead Fields. Create Task assigns the follow-up with a deadline, and Send Notification pings the assigned rep inside the portal they already work in. The rep opens a lead with the full ask attached instead of an email forwarded three times.
Deals that document themselves
When a proposal goes out, the agent sends it through Gmail, then calls Add Timeline Comment on the deal so the record shows what was sent and when. Stage changes flow through Update Deal, meetings and calls get logged with Create Activity, and a nightly job feeds List Deals into [Google Sheets](/integrations/google-sheets) for the pipeline report nobody has to assemble. When a support request surfaces in [Slack](/integrations/slack), Create Task routes it to the responsible user with the thread context attached.
Quarter-end pipeline cleanup that keeps its history
Stale deals accumulate. On request, the agent assembles the cull list: List Deals filtered on stage and age, cross-checked against List Activities for last contact, presented with each deal's value and owner. The sales ops lead reviews the list and approves or strikes each line. Only then does Delete Deal run, and only on the approved lines. What was a risky bulk purge becomes a reviewed decision with a record of who approved what.
Human-in-Loop Highlight
Delete Deal and Delete Lead are permanent, and in Bitrix24 they take the timeline records with them: every comment, every logged call, every trace of the relationship. So the cleanup agent never deletes on its own criteria. It posts the proposed list to the sales ops lead: "23 deals in stage Proposal with no activity since March, total pipeline value shown per line. Approve each deal for deletion, or mark it to keep." Each approval is explicit. The agent deletes exactly what was approved and logs the rest as retained. A pipeline number you can defend is worth more than a tidy one.
Agent Capabilities
40 actionsLeads
6- List Leads Retrieves a page of leads with filtering, sorting, and field selection. Used for dedup checks and pipeline sweeps.
- Get Lead Retrieves a single lead including multi-value phone and email arrays and custom fields.
- Create Lead Creates a lead and returns its ID. The capture step for every inbound prospect.
- Update Lead Updates an existing lead. Used for enrichment and status changes.
- Delete Lead Permanently deletes a lead, including its timeline records. Gated on human approval.
- Get Lead Fields Returns the schema of all lead fields, including custom ones. Used so workflows write to the fields your portal actually has.
Contacts
6- List Contacts Retrieves a page of contacts with filtering and sorting.
- Get Contact Retrieves a single contact with phone, email, and custom fields.
- Create Contact Creates a contact and returns its ID. Used in batch imports and lead conversion flows.
- Update Contact Updates an existing contact.
- Delete Contact Permanently deletes a contact. Gated in cleanup workflows.
- Get Contact Fields Returns the contact field schema, including custom fields.
Companies
6- List Companies Retrieves a page of companies with filtering and sorting.
- Get Company Retrieves a single company with its custom fields.
- Create Company Creates a company and returns its ID.
- Update Company Updates an existing company.
- Delete Company Permanently deletes a company. Gated in cleanup workflows.
- Get Company Fields Returns the company field schema, including custom fields.
Deals
6- List Deals Retrieves a page of deals with filtering, sorting, and field selection. The backbone of pipeline reporting.
- Get Deal Retrieves a single deal with its custom fields.
- Create Deal Creates a deal and returns its ID. Used when a qualified lead becomes pipeline.
- Update Deal Updates an existing deal. The stage-advancement step in progression workflows.
- Delete Deal Permanently deletes a deal, including its timeline records. The operation this page's human gate exists for.
- Get Deal Fields Returns the deal field schema, including custom fields.
CRM Reference and Timeline
5- Get Status List Retrieves the portal's reference values: lead statuses, sources, deal stages, types, and industries. Used so workflows speak your portal's vocabulary.
- Get Deal Categories Retrieves all deal pipelines, including the default. Used to place deals in the right pipeline.
- Add Timeline Comment Adds a comment to the timeline of a lead, deal, contact, or company. The step that makes automated work visible on the record.
- Create Activity Creates a meeting, call, or email activity attached to a record. Used to log real-world touchpoints.
- List Activities Retrieves a page of activities with filtering by owner record. Used to establish last-contact dates before cleanup decisions.
Tasks
6- List Tasks Retrieves a page of tasks with filtering and sorting.
- Get Task Retrieves a single task with title, status, priority, deadline, and responsible user.
- Create Task Creates a task and returns it. Used to turn workflow findings into assigned work.
- Update Task Updates an existing task.
- Complete Task Marks a task as completed. Used when the agent finishes the work the task tracked.
- Delete Task Permanently deletes a task, including its checklist and comments.
Users, Notifications, and Platform
5- List Users Retrieves a page of portal users.
- Get Current User Returns the profile behind the connection, including admin flag and time zone. Used as a connection check.
- Search Users Searches users by name, email, position, or department. Used to resolve the right assignee at runtime.
- Send Notification Sends a system notification to a user's Bitrix24 notification center. The in-portal nudge that reaches reps where they already work.
- Call REST Method Calls any of the 600+ Bitrix24 REST methods not covered by dedicated actions. The escape hatch for products, quotes, disk, and telephony; write calls through it get the same review gates as any other consequential operation.
Frequently Asked Questions
What can FlowRunner do with Bitrix24?
FlowRunner agents can run List Leads, Get Lead, and Create Lead in Bitrix24, plus 37 more actions.
Does connecting Bitrix24 to FlowRunner require OAuth?
Bitrix24 uses a custom authentication method to connect to FlowRunner.
Can Bitrix24 trigger a FlowRunner workflow automatically?
Bitrix24 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Bitrix24
$100 in credits. No card required. Connect in minutes.