Robots in Bitrix24 (Alaio) 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 from anything but a flat number of days. 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. Deadlines are counted in calendar days everywhere here, so the fix is to compute the date yourself before the task is created. The Nearest date by condition robot returns the nearest working day from a given date — or the next Monday, or the last day of the month — in two formats, 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 on the nearest working day.
How to link a task to a deal, contact or company?
Linking a task to CRM is built in, and there are three ways to do it. By hand — in the task form, in the CRM block: add a deal, lead, contact or company there, and one task can be linked to several records. From the card — a task created from a deal's timeline is linked to that deal right away. From a workflow — the Task action in a deal workflow creates a task linked to the current record. A linked task appears in the card's timeline as an activity, and the sales rep sees its status without opening the tasks section.
It gets harder when the task already exists and the link has to be added, changed or removed automatically. Two robots handle that. Task CRM binding (by ID) works from any workflow: pass the task ID, the record type and the record ID, and choose a mode — add a link, replace (previous links of the same type are removed) or remove. Current task CRM binding does the same from the task's own automation, where no task ID is needed. In both cases the robot writes the link in the format Bitrix24 understands: D_10 for a deal, C_7 for a contact, CO_5 for a company, L_4 for a lead.
To see all tasks for a client right on the card instead of scrolling the timeline, use the Tasks on the record field: how many tasks are open, overdue and completed, and the task list one click away.
How to change the responsible person in linked tasks when the deal changes hands?
Out of the box, changing the responsible person on a deal does not touch its tasks: they stay with the previous employee. A workflow on the deal that starts when the deal changes closes this gap. The Find task by condition robot searches tasks by their CRM link — enter D_ plus the current deal ID, for example D_{=Document:ID}, and filter by status if you need open tasks only. It returns the list of found task IDs, up to 50 per call. Then loop over that list with an iterator and call Update task by ID inside it with the fields {"RESPONSIBLE_ID": …}. That value must be a numeric employee ID: a user field from the document can be inserted into text as user_5, and the task will not accept it. It is safer to read it with the Get field value from a related entity robot — it returns the current deal's ASSIGNED_BY_ID as a number. The same approach moves the deadline or changes observers on all of a client's tasks at once.
If you need to hand over not only tasks but also related deals, contacts and companies — when a sales rep leaves, for example — the steps are in employee offboarding in Bitrix24.
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.