Bitrix24 CRM Automation Robots: Setup & Debugging
A manager forgot to send a quote, didn't call the day after the meeting, or failed to create a task for document preparation. Familiar? At TrueTech, we encounter such funnel leaks daily. Properly configured CRM robots are the only way to guarantee these actions without human intervention — but only when the configuration matches the real business process, not a template.
In one project, the client lost up to 40% of leads because managers forgot to call back. After implementing robots on the "New Lead" and "Qualification" stages with delays of 2 hours and 1 day, missed contacts dropped threefold. Robots work more accurately than humans — they don't forget, procrastinate, or confuse fields.
How Robots Work Technically
CRM robots are instances of \Bitrix\Bizproc\Automation\Robot, launched by the business process engine (bizproc). They are attached to a specific funnel stage and trigger when an entity (deal, lead, smart process) moves to that stage.
Storage: robot configurations are in the b_bizproc_workflow_template table, running process instances in b_bizproc_workflow. When a stage transition occurs, a workflow instance is created and robot actions execute sequentially or with a delay.
It's important to understand: a robot is not a trigger but a separate asynchronous process. If the server is overloaded or the agent \Bitrix\Main\Application::runModuleAgents doesn't run, robots queue and execute late. More details in Bitrix24 robot documentation.
Why Bitrix24 Robots Don't Trigger?
The most common failures are incorrectly set execution conditions and ignoring delays. For example, an email sending robot runs but doesn't verify the recipient's address — the email goes into the void. Or a condition with a high amount applies to the "Amount" field without considering currency — the robot won't trigger for deals in other currencies.
Another issue is agent overload. When many agents run on the portal (1C synchronization, mass mailing), robot execution can be delayed by hours. We solve this by setting agent priorities and optimizing the queue.
Types of Robots and When to Use Them
| Robot | Purpose | Typical Mistake | Performance |
|---|---|---|---|
CrmSendEmailRobot |
Send email | Using technical address instead of corporate | Executes in 1–2 sec |
CrmAddTaskRobot |
Create task | Task not linked to deal, context lost | Creates task instantly |
CrmUpdateFieldRobot |
Update fields | Condition doesn't cover all required values | Works without delay |
RestActivityRobot |
Call webhook | Authentication error or incorrect data format | Depends on external server |
Comparison: robots are on average 5x faster than manual execution of the same actions — automation eliminates time for deliberation and context switching.
How We Set Up Automation for Your Business Process
Our approach is not to copy standard scenarios but to design robots for your specific funnel stages. First, audit current processes: which actions managers perform manually, where delays occur, which fields are filled incorrectly. Based on the audit, we create a robot scheme with conditions, delays, and chains.
Second, configuration in Bitrix24. We use all robot types: CrmSendEmailRobot, CrmAddTaskRobot, CrmUpdateFieldRobot, RestActivityRobot, as well as complex scenarios with conditions and delays. Each robot is tested on test entities with all possible outcomes verified.
Third, team training and documentation handoff. We prepare automation diagrams and describe each chain so you can make changes yourself.
Step-by-Step Robot Setup in 10 Minutes
- Go to CRM → Settings → Automation → Robots.
- Select a funnel stage (e.g., "New Lead").
- Click "Add Robot" and choose a type (e.g.,
CrmAddTaskRobot). - Set the task name, responsible person, and deadline. Use entity fields:
{=Document:ASSIGNED_BY_ID}. - Set a delay if needed (e.g., 2 hours).
- Save and test on a test deal.
What's Included in Robot Setup
- Audit of current CRM and sales funnel
- Designing robot scheme with conditions and delays
- Configuring robots in the admin panel
- Testing each transition on test entities
- Training responsible employees
- Documentation of automation scheme
- Guarantee of correct operation — if a robot fails, we fix it at no extra charge
Typical Funnel Automation Scheme
Example for a SaaS product sales funnel:
- Stage "New Lead": robot "Notify responsible" + task "Call within 2 hours"
- Stage "Qualification": delay 1 day → email with presentation
- Stage "Quote Sent": delay 2 days → task "Follow up on quote decision"
- Stage "Won": thank-you email + webhook to account activation system
Total 6–8 robots, setup takes 3–4 hours including testing each transition.
Debugging Robots
If a robot didn't execute, check CRM → Automation → Log. There you see each run, status, and error. The second tool is Settings → Tools → Agent Queue, where you can forcibly run a stuck agent.
Timelines and Cost
Timeline depends on funnel complexity: from 2 to 5 working days for a typical project. Cost is calculated individually after audit. Request a consultation — we'll assess your funnel and propose an optimal scheme.
Why Choose Us?
Over 5 years of experience in Bitrix24 setup, more than 50 successful CRM automation projects. With robot implementation, lost deals drop by 25%, and lead processing time decreases by 40%. We guarantee stable robot operation and provide you with documentation. Contact us — we'll solve any issue.