Setting up No-Code Automations for Bitrix24
A manager forgets to move a deal to the next stage. A supervisor doesn't get a notification about an overdue task. A customer waits for a commercial proposal that no one sent — typical picture in CRM without automation. Bitrix24 has three tools that let you close these gaps without writing a single line of code: robots, business processes, and smart processes. Each solves its own class of problems, and confusion between them is the main reason automation doesn't work.
Robots — Automation on CRM Stages
Robots are tied to deal, lead, invoice, and proposal stages. A deal moves to "Contract Preparation" stage — the robot sends a letter to the customer, creates a task for legal, changes the responsible party. Logic is simple: stage event → action.
What robots can do:
- Send email, SMS, and chat messages
- Create tasks and documents
- Change entity fields (status, responsible, sum)
- Wait for a condition (like field fill-in) then proceed
- Call webhooks — for integration with external services
Limitations. Robots work linearly within one stage. No branching, no loops, no parallel routes. If you need "if amount > 100,000 — director approval, else — straight to work", a robot won't work. For that — business processes.
Business Processes — Visual BPMN
Business process (BP) designer is a full constructor with conditions, loops, parallel branches, and approval blocks. BP runs manually, on schedule, or via a robot.
| Feature | Robots | Business Processes |
|---|---|---|
| Conditional branching | No | Yes |
| Parallel routes | No | Yes |
| Voting approval | No | Yes |
| Loops | No | Yes |
| Tied to CRM stages | Yes | Via robot trigger |
| Working with lists | No | Yes |
Typical scenario — approving an expense request. Employee fills form; BP checks amount: up to 50,000 goes to department manager, above that adds finance director stage. Each stage has deadline, escalation, comment. Result is recorded; history is saved.
BP Limitations. Designer is visual, but with complex logic the diagram becomes unreadable. Debug is via execution log, which is inconvenient for dozens of branches. No versioning: change process — old version is lost.
Smart Processes — Custom Entities
Smart processes emerged as replacement for deprecated CRM "Lists". Essentially, a constructor for custom entities with pipeline, fields, robots, and access rights — no development needed.
When you need smart processes:
- Standard CRM entities (deals, leads) don't fit semantically — e.g., repair request, complaint, internal order
- Need separate pipeline with own stages, unconnected to sales
- Need binding to deal or contact, but with own processing logic
Smart processes support same robots and triggers as deals. You can bind business processes to them. Essentially — no-code way to create a new module inside Bitrix24.
What to Choose
- Simple linear automation on CRM stages → robots
- Approvals, branching, complex routing → business processes
- New entity with pipeline and automation → smart process + robots/BP
Combination of three tools covers 80–90% of automation tasks without hiring a developer. Remaining 10–20% — integrations with external systems via REST API, custom activity blocks, and server handlers where no-code ends and code begins.