Automating Bitrix24 Business Processes: From Simple to Complex Scenarios
A travel request hangs: the manager doesn’t see the notification, the accountant misses the deadline. Each such failure costs 5,000 rubles of working time. Manual processing of 20 requests takes 4 hours for a manager. Bitrix24 business processes automate this chain—but only if you choose the right tool: BPs or CRM robots. We break down the criteria and set up the process for your tasks.
According to statistics, companies lose up to 30% of time on approvals. Automation returns those hours and saves up to 180,000 rubles per year on operational expenses. This article contains real examples from practice, technical details, and a step-by-step setup scheme. Integration with 1C via CommerceML allows automating document exchange and procurement approval.
How to distinguish a business process from a CRM robot?
CRM robots are a simplified designer for linear scenarios inside the funnel. Business processes are an engine with branching, loops, waiting for user actions, and conditions. Technically both run on \Bitrix\Bizproc\Workflow, but the BP editor gives more elements: “If-Then-Else”, “Loop”, “Parallel Actions”, “Assignment for user”. According to the Bizproc documentation, this is the main tool for complex processes.
| Criterion | CRM Robots | Business Processes |
|---|---|---|
| Complexity | Up to 10 steps | Any, with branching and loops |
| Conditions | Only by CRM fields | Full conditions, variables |
| User actions | No | Yes (assignments, confirmations) |
| Performance | Faster on large volumes | Heavier under high loads |
Use BPs when:
- user action is required (confirm, reject, specify data)
- there is branching by conditions
- the process involves several departments sequentially
- loops or parallel branches are needed
Which entities support business processes in Bitrix24?
BPs work on four entity types: list elements (requests, registers), disk documents, CRM elements, site pages (on-premise). For corporate requests, Lists are most often used. Path: Bitrix24 → Lists → [List] → Business Processes → Add. In 10 minutes, a template for vacation approval is configured.
Business process variables and their application
BPs operate with three types: parameters (passed at launch, e.g. request amount), variables (internal, e.g. voting result), document fields. They are passed via {=Variable:VariableName} or {=Document:FIELD_NAME}. For example, the variable {=Document:Sum} allows branching: if sum exceeds a threshold – approval with the financial director.
Setting up a business process in 5 steps
- Requirements analysis. We identify approval points, roles, conditions, throughput (e.g. 50 requests per day).
- Scheme design. We draw a graph in the BP editor – using assignments, conditions, waits.
- Implementation. We configure actions: upon request creation, a chain of assignments launches.
- Testing. We check on 10 test elements all branches, fix errors.
- Deployment and training. We launch into production, instruct employees, record feedback.
Practical example: procurement approval
Client – a manufacturing company: 100 purchase requests per month, the process was via email – 40% were lost. We configured a BP on the “Purchase Requests” list:
- Roles: manager (approves up to a set limit), director (above).
- Branching: if urgent → chat notification, otherwise – email.
- Result: approval time reduced from 3 days to 6 hours, resulting in significant annual savings.
What is included in the business process setup
Each project includes:
- documentation of the BP scheme (graph, roles, conditions)
- access and user rights configuration
- writing instructions for employees
- testing on 10–20 elements
- support for 30 days after launch
Typical mistakes when setting up BPs:
- Wrong choice of launch type (manual instead of automatic).
- Lack of error handling (process freezes on failure).
- Excessive assignments that slow down the process.
- Not accounting for performance: on 1000+ elements, BP may slow down.
We identify these mistakes during testing and fix them before deployment.
Process and timelines
We work in stages: analysis → design → implementation → test → deploy. In analysis we record every approval point, roles and conditions.
| BP Type | Estimated Time |
|---|---|
| Simple linear | 2–3 hours |
| With several approval stages | 4–6 hours |
| Complex with branching and variables | 1 day |
Cost is calculated individually after task analysis. We assess the project for free. Contact us for a consultation on your tasks. Order a setup and we will turn chaos into streamlined automation.
Why choose us?
Experience in Bitrix – over 10 years. We have completed 50+ automation projects. 1C-Bitrix certificates confirm qualification. We guarantee the process works – if something goes wrong, we fix it without additional charges.

