Setting Up Automatic Task Creation from Bitrix24 CRM
A manager closes a deal, but nobody creates a task to prepare the documents — it stays in someone's head. Automatic task creation from CRM removes this dependency on employee memory.
Mechanisms for Creating Tasks from CRM
In Bitrix24 tasks from CRM are created in three ways:
"Create Task" robot — fires when a deal/lead moves to a stage. The most flexible method: title, description, assignee, deadline, and priority are all configurable. Supports substitution of CRM fields via {=Document.FIELD_NAME}.
Trigger + robot — a combination: an external event moves the deal to a stage, the robot creates a task. For example, client paid the invoice → task to ship the order.
Business process — when a task needs to be created with conditions: different tasks depending on the deal type, creating multiple tasks at once, creating tasks with a checklist.
Configuring the "Create Task" Robot
Path: CRM → [Funnel] → Robots → [Stage] → Add Robot → Create Task.
Key parameters:
Assignee — a fixed user or a value from a deal field. Most common: {=Document.ASSIGNED_BY_ID} (the deal's responsible person). For assigning to another department — a fixed group of users.
Deadline — relative: "N days after task creation". Supports the work calendar — if the "Working days" flag is set, weekends are excluded.
Title and description with CRM field substitution:
Prepare documents for deal #{=Document.ID}: {=Document.TITLE}
Contact: {=Document.CONTACT_ID}
Amount: {=Document.OPPORTUNITY} {=Document.CURRENCY_ID}
Link to deal — the task is automatically linked to the deal it was created from. The task appears in the "Tasks" block on the deal card.
Creating Tasks with a Checklist
The standard robot doesn't support checklists. For tasks with a checklist — use a business process or a custom robot via REST:
$client->call('tasks.task.add', [
'fields' => [
'TITLE' => 'Prepare document package',
'RESPONSIBLE_ID' => $deal['ASSIGNED_BY_ID'],
'DEADLINE' => date('c', strtotime('+3 days')),
'UF_CRM_TASK' => ['D_' . $dealId],
'CHECKLIST' => [
['TITLE' => 'Contract'],
['TITLE' => 'Invoice'],
['TITLE' => 'Act'],
],
],
]);
The UF_CRM_TASK field links the task to a CRM entity. Format: D_ID for deals, L_ID for leads, C_ID for contacts.
Creating Multiple Tasks
When moving to a stage you need to create three tasks simultaneously — for the manager, the lawyer, and the accountant. Solution: three "Create Task" robots on the same stage. Robots execute in parallel.
An alternative for complex scenarios is a BP with a "Parallel Actions" block, where each branch creates its own task.
Tracking Task Completion in CRM
A task is completed — the deal needs to move to the next stage. This is done via a trigger on the task completion event. Path: CRM → Funnel → Triggers → Add → Task Completed.
The trigger tracks a specific task or any task linked to the deal — depending on the configuration.
Setup Time
Setting up automatic task creation for one funnel — 2–4 hours. Includes configuring robots on each required stage, testing field substitution, and verifying task-to-deal binding.







