Robots in Bitrix24 tasks are automatic actions on the stages of the task Kanban: a task lands in a column — a robot adds an observer, changes the responsible person, posts a comment, or creates a subtask. The mechanics are the same as in CRM, but they are enabled separately and have their own limits. Let's look at where to enable them, what's available, how task robots differ from CRM ones, and how to reach tasks from a deal's business process.
How do you enable robots in tasks?
Robots live in a project's Kanban or in "My Tasks": open the Kanban → the stage's gear icon → "Robots" (in older interfaces, the "Robots" button above the board). Robots are bound to the Kanban stages of a specific project, not to tasks globally: each project has its own set. Availability depends on the plan: on the lower plans there are no task robots. If you don't see the button, check the plan and permissions — only a project administrator can configure robots.
What can the stock task robots do, and where is their limit?
The stock set covers routine within a single task: change the responsible person and observers, push the deadline, post a comment, send a notification, create a subtask, change the stage. The limit kicks in where you need a connection to the outside world: a task robot can't find another task, can't read deal fields, can't calculate a deadline against the production calendar. The second boundary is the trigger: task robots fire only on a Kanban stage change — there are no "N days before the deadline" events in robots; that kind of thing is built through a business process or external automation.
How do you work with tasks from CRM business processes?
A common scenario is the reverse: the process runs on a deal, but it's tasks you need to manage. The stock "Add task" action creates a task but can't find an existing one and change it. Two Roboteka robots close that gap: Find a task by condition searches for a task by responsible person, status, or exact title and returns its ID, while Update a task by ID changes its fields — title, deadline, responsible person, status. The "find → update" pairing lets you, for example, automatically push the deadline of a linked installation task when a deal changes stage, or close the proposal-preparation task once the invoice is paid.
How do you calculate task deadlines sensibly?
"Deadline in 3 days" in the stock robot means calendar days: a task created on Friday burns out on Monday morning. The Date + N working days robot counts the deadline against the Russian production calendar, and Day of the week lets you branch the logic: tasks created on Friday afternoon get a deadline starting Tuesday. Both work in business processes — the calculated date is fed into the "Add task" action or into Update a task.
Everyday pairings
Three schemes you can set up in an evening. Overdue control: a deal process finds the proposal task and, if it isn't closed by the control date, notifies the manager. A department relay: a task in the project Kanban moves to the "Ready for review" stage — the robot changes the responsible person to the tester and adds the author as an observer. Sync with the deal: a deal moves to "Paid" — the process finds the shipping task and bumps it to priority with a new deadline in working days.
In summary
Task robots are good inside the Kanban, but real task automation lives in CRM business processes — from there you can find, update, and link tasks to deals. The missing actions are in the Roboteka catalog: installation is free, and the robots appear in the designer next to the stock ones.