Setup of low-code development on Bitrix24
Business wants to automate processes, but there's no budget for full development, and no in-house programmers either. Bitrix24 offers a set of low-code tools: CRM robots, business processes, smart processes, task automation. The problem is that without proper setup, these tools turn into a chaos of dozens of robots that conflict with each other and work unpredictably.
Smart processes
Smart processes are custom CRM entities with their own stages, fields, and automation. Essentially — a constructor for business objects without writing code.
Typical uses: contract approvals, complaint handling, project management, equipment tracking. Setup:
- CRM → Settings → Smart processes → Create — name, pipeline binding
- Stages — sequence of steps (draft → pending approval → approved → rejected)
- Fields — typed: string, number, date, user binding, binding to another CRM entity
- Access rights — by roles: who sees, who edits, who moves between stages
- Automation — robots and triggers, identical to those working in deals and leads
Limitation: smart processes are available on "Professional" and "Enterprise" plans. On lower plans — only deals and leads.
CRM robots: configuration rules
Robot — action performed automatically on stage change. Built-in actions — dozens: send email, create task, change field, wait N days, webhook.
Rules that save hours of debugging:
- One robot — one action. Don't try to send email, change field, and create task in one robot. A chain of three robots is easier to read and debug.
- Conditions — before action, not inside. Use a conditional robot (condition) before the action, not trying to embed conditions in every robot.
-
Variables. Result of one robot (e.g., created task ID) is passed to the next via
{{ID}}. Document what each robot returns. - Timeouts. "Wait" robot pauses the chain. If the stage already changed after waiting — subsequent robots won't execute. Check this.
Business processes
Business processes (BP) — more powerful than robots. Support branching, loops, parallel branches, custom activities. Configured in visual editor.
Applied for:
- Document approvals with multiple levels (manager → lawyer → director)
- Processes with conditional transitions (if sum > 100,000 — additional approval)
- Automation tied to documents, not CRM stages
BP runs on CRM entities, list items, documents. Smart processes also support them.
What we configure
- Audit current automation: identify conflicting robots and duplicates
- Design smart processes for specific business scenarios
- Configure CRM robot chains with documentation of logic
- Configure business processes with branching and approvals
- Connect external services via webhook robots
- Test scenarios: element progression through all stages with checking each robot