Bitrix24 Business Process Automation: Robots, Triggers and the Workflow Designer
Bitrix24 business process automation lets you replace manual follow-ups, status changes and approval chains with rule-based robots and visual workflow sequences - all without writing a single line of code on the Professional plan and above.
The Three Building Blocks: Robots, Triggers and Business Processes
Bitrix24 (Alaio) automation rests on three distinct but complementary tools - robots (lightweight rule-based actions), triggers (event listeners that kick off those actions), and full business processes (multi-step workflows with branching logic and human approval gates) - and understanding the difference between them is the first step to designing a reliable automation layer.
Most teams reach for robots and triggers first because they require no visual programming: you pick an action, set a condition and save. Business processes are the heavier tool, reserved for scenarios that branch, loop, require multiple approvers or produce a formal output like a signed document.
| Tool | Initiated by | Complexity | Typical use case |
|---|---|---|---|
| Robot | Stage change or scheduled time | Low | Send email, assign task, update field |
| Trigger | Field change, incoming message, form submit | Low - Medium | Move deal to next stage when payment received |
| Business Process (BP) | Button click or field change | Medium - High | Multi-level document approval with comment threads |
All three tools are available within the standard portal functionality on the Professional plan; work requiring custom code is handled separately and scoped independently.
How Robots Work in CRM Deals, Leads and Contacts
A robot is a single automated action attached to a CRM pipeline stage - when a deal, lead or contact enters that stage, Bitrix24 executes the robot immediately or after a set delay, without any human involvement.
Robots live inside deal, lead and contact cards. Common configurations our teams set up across client projects include:
- Send an email or SMS to the contact when a deal moves to "Proposal Sent"
- Create a task for the responsible manager with a deadline tied to the deal's closing date
- Change a field value automatically - for example, flagging a lead as "Hot" when a form is submitted from a specific source
- Assign a responsible user based on predefined routing rules (territory, product line, language)
- Schedule a follow-up activity a fixed number of days after the last interaction
Because robots are stateless - they fire once and finish - they are the right choice for notifications and field updates. For anything that needs to wait for a human response before continuing, you need a business process.
Triggers: What They Are and When They Fire
A trigger is an event listener: it watches for a specific change inside Bitrix24 (or from an external source) and, when that change occurs, moves the CRM entity to a designated stage or launches a robot chain.
Triggers and robots are designed to work together. A trigger detects the event; robots execute the consequences. Common trigger events used in real projects:
- A specific field in the deal card is changed (e.g., contract amount updated)
- An inbound email or chat message arrives on an open deal
- A form on the website is submitted and a lead is created
- A date field is reached (e.g., contract expiry date passes)
- A payment status changes in a connected accounting or e-commerce system
Incoming events from different channels flow through triggers into the CRM pipeline, which then fires robots or launches a full business process depending on the scenario.
Website forms, telephony, email and external systems each fire a Bitrix24 trigger that moves a CRM entity to the correct stage, after which robots execute actions such as sending notifications, creating tasks or launching a multi-step approval workflow.
flowchart LR
FORM[Website Form] -->|Lead created| TRG[Trigger]
PHONE[Inbound Call] -->|Call ended| TRG
EMAIL[Inbound Email] -->|Message received| TRG
EXT[External System\ne.g. ERP / Payment] -->|Status change| TRG
TRG -->|Stage move| STAGE[CRM Stage]
STAGE --> ROBOT[Robot Actions\ne.g. email, task, field update]
STAGE --> BP[Business Process\ne.g. approval workflow]
BP --> NOTIFY[Notifications to\nApprovers / Manager]
BP --> RESULT[Output: document,\nstatus, comment]
The Workflow Designer: Visual Logic for Complex Approvals
The Bitrix24 workflow designer is a visual drag-and-drop editor where you connect action blocks, condition branches and parallel paths into a single automated sequence - no coding required, though the logic can be as complex as a multi-department approval chain.
Each configured business process equals one chain of transformations: from the moment it starts (manually via a button, or automatically via a field change) to the moment it produces its final result. A single process can have multiple terminal outcomes - approved, rejected, returned for correction - each routed to a different downstream action.
Key capabilities of the workflow designer:
- Sequential and parallel approval steps - send to one approver, then another, or to both simultaneously
- Conditional branching - take different paths based on deal amount, department, document type or any custom field
- Timers and deadlines - escalate automatically if an approver doesn't respond within a set window
- Comment and verdict capture - at each approval step, participants can leave a comment and record their decision (approve / reject / request revision)
- Return-to-initiator branch - up to one correction loop is configurable: the document goes back to the person who started the process, who can revise and resubmit for a fresh approval run
- Notifications - email, push and internal Bitrix24 messages can be sent at any step
The designer operates entirely within the platform's no-code interface. When requirements exceed what standard blocks can handle, custom development is scoped separately.
Document and Purchase Approval Workflows in Practice
A well-structured approval workflow in Bitrix24 captures the document's key parameters (date, number, amount) at launch, routes it through one or more approvers who leave comments and verdicts, and - if rejected - can return it to the initiator for a single correction cycle before restarting the approval.
Based on our implementation experience, the most common approval workflows across industries are:
- Contract approval - initiated by a sales manager, reviewed by legal and finance, signed off by the director
- Procurement / supply request - material request from a project team routed to the purchasing manager and CFO
- Invoice approval - triggered when an invoice is attached to a deal, routed by amount threshold
- HR document approval - leave requests, overtime records, employee onboarding checklists
- Project estimate sign-off - budget approval before a project moves to active status
A real project delivering approval automation for a client (two approval workflows: document approval and materials procurement approval) was scoped and delivered within a 4-week window, illustrating that even multi-step workflows can be configured quickly when requirements are clear up front.
For teams evaluating broader automation scope, see Bitrix24 Implementation Hours by Module for a detailed breakdown of configuration effort per functional area.
Smart Processes: Custom CRM Entities with Built-In Automation
Smart Processes extend Bitrix24's CRM beyond deals and leads by letting you create entirely new entity types - such as contract registries, equipment logs or warranty case trackers - each with its own pipeline stages, fields and automation rules.
Where standard CRM entities (leads, deals, contacts, companies) don't fit a specific operational need, Smart Processes fill the gap. Typical examples from our client projects:
- Contract registry - tracks all active contracts with automated renewal reminders
- Addendum register - linked to parent contracts, with its own approval flow
- Equipment inventory - availability tracking with assignment workflows
- Warranty case tracker - customer-reported issues routed to the service team with SLA timers
Smart Processes support the same robots, triggers and business processes as standard CRM entities, so automation built for deals can be replicated and adapted for any custom entity type.
For industries with complex asset and booking workflows - such as car rental companies or logistics and freight forwarders - Smart Processes are often the primary tool for modelling operations that don't fit a standard sales funnel.
How a Typical Automation Setup Is Delivered
In a standard Bitrix24 automation project, the configuration phase spans roughly 8 working days: 1 day for process inventory, 2 days for business process setup, 2 days for robots and triggers, 1 day for notifications, and 2 days for scenario testing and error correction.
The delivery sequence our teams follow across projects:
| Step | Activity | Working Days |
|---|---|---|
| 5.1 | Process inventory - identify which workflows need automation | 1 |
| 5.2 | Business process configuration - roles, rights, approval logic | 2 |
| 5.3 | Robots and triggers - standard automations: emails, tasks, field updates on date events | 2 |
| 5.4 | Notification setup - email and push alerts for new deals, tasks, comments, document changes | 1 |
| 5.5 | Scenario testing (UAT) - verify all processes fire correctly, fix errors | 2 |
| Total | 8 days |
Before configuration begins, the implementation partner conducts structured discovery interviews with the client - reviewing existing process documentation, auditing current tool usage and drafting a technical specification that maps each workflow to a Bitrix24 solution. This document is updated after each interview session and finalised before build work starts.
Training is delivered at handover: typically a two-hour remote group session, recorded, covering the configured approval and notification workflows. This gives the team a reference they can return to without needing to contact support for routine questions.
For a full picture of what goes into scoping a Bitrix24 project, the Bitrix24 Onboarding Questionnaire covers the 50+ questions that surface automation requirements before a line of configuration is written.
What Operations and Sales Teams Actually Automate
The highest-ROI automation scenarios in Bitrix24 are those that eliminate repetitive human handoffs: moving deals between stages, notifying the right person at the right time, routing documents for approval, and updating records when external events occur.
A practical reference of automation scenarios by team:
Sales Teams
- Auto-assign new leads by territory, source or product
- Send proposal emails when a deal reaches "Negotiation" stage
- Create a follow-up task if a deal sits in a stage for more than N days (stalled deal detection)
- Notify the manager when a high-value deal is won or lost
- Update the deal's probability field as it progresses through stages
Operations / Back-Office
- Route procurement requests through a multi-level approval chain
- Generate a task for the logistics team when a deal moves to "Ready to Ship"
- Send contract renewal reminders 30 and 7 days before expiry
- Archive completed projects and notify stakeholders
Management
- Receive a daily digest of deals that moved stages
- Get an instant alert when a deal exceeds a certain value
- Monitor approval bottlenecks via the workflow audit log
Teams moving from a simpler CRM will find the automation depth a significant step up. If you're evaluating whether Bitrix24's automation layer fits your current operational stage, Signs You Have Outgrown Your Spreadsheet or Starter CRM walks through the common indicators. For teams coming from a competing platform, the AI Call Analysis in Bitrix24 article shows how automation extends beyond the CRM into conversation intelligence.
All automation described here operates within the standard no-code interface of the Bitrix24 Professional plan. Scenarios requiring custom logic - for example, integrating with a proprietary ERP or building non-standard approval branches - are scoped as separate development work. See Bitrix24 ERP & Accounting Integration for what that integration layer looks like in practice.
Frequently asked questions
What is the difference between a Bitrix24 robot and a business process?
A robot is a single automated action (send email, update field, create task) that fires when a CRM entity enters a specific stage. A business process is a full multi-step workflow with branching logic, human approval gates and multiple possible outcomes - it's the right tool when a robot's one-shot execution isn't enough.
Do I need to know how to code to set up Bitrix24 automation?
No. Robots, triggers and the workflow designer all operate within Bitrix24's no-code interface on the Professional plan and above. Custom code is only required for non-standard integrations or logic that exceeds the platform's built-in blocks, and that work is scoped separately.
Can a business process return a document to the initiator for corrections?
Yes. The workflow designer supports up to one return branch per process: if an approver rejects a document, it goes back to the person who initiated it with the reviewer's comment attached. The initiator corrects and resubmits, which starts a fresh approval run.
How long does it take to configure robots and business processes in a typical project?
Based on our project data, the automation configuration phase typically takes around 8 working days: process inventory, business process setup, robots and triggers configuration, notification setup and UAT testing. This assumes requirements are documented before build work starts.
What are Smart Processes and how do they relate to automation?
Smart Processes are custom CRM entity types you create when standard deals, leads or contacts don't fit your workflow - for example, a contract registry or equipment log. They support the same robots, triggers and business processes as standard CRM entities, so your automation logic transfers directly.
Which Bitrix24 plan is required for full business process automation?
The full workflow designer and advanced automation features are available on the Professional plan and above. Some basic robots are available on lower tiers, but multi-step approval workflows with branching logic require Professional or Enterprise.
Based on real practice
This article is based on 15 internal documents from ACP Group's practice - work plans, specifications and Bitrix24 implementation cases.
Need help with Bitrix24?
ACP Group is a Bitrix24 Gold Partner. We'll review your task, estimate the effort in hours and propose a plan - free of charge.