Task Templates: Overview of Methods
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Task templates help to describe a typical workflow in advance and use a unified set of settings for new tasks. A template can save the task title and description, participants, deadlines, project, recurrence, checklist, and other fields.
Quick navigation: all methods
User documentation: How to work with task templates
Getting Started
- Define the fields of the template on the Task Template Fields page or obtain their description using the tasks.template.fields method.
- If the template is to create recurring tasks, configure the
REPLICATEandREPLICATE_PARAMSfields. - Obtain the identifiers of users, groups, and CRM entities if references to these objects are needed in the template.
- Create the template using the tasks.template.add method.
- Retrieve the template using the tasks.template.get method if you need to check the saved values.
- Modify the template using the tasks.template.update method if you need to adjust the parameters.
- Add checklist items using the methods from the Task Template Checklists section if the task consists of recurring steps.
- Delete the template using the tasks.template.delete method if it is no longer needed.
Access Permissions
Permissions for working with task templates depend on the access settings in tasks.
User Documentation
Relationships with Other Objects
Tasks. The template stores the settings for the future task: title, description, deadlines, responsible persons, observers, checklist, and other parameters. Use the methods from the Tasks section to work with tasks.
Users. In the template, you can specify the Creator, main Participant, other Participants, and observers through the fields CREATED_BY, RESPONSIBLE_ID, RESPONSIBLES, ACCOMPLICES, AUDITORS. User identifiers can be obtained using the user.get and user.search methods.
Groups and Projects. To link the template to a group or project, use the GROUP_ID field. This allows you to create tasks in the desired workspace. The identifier of the group or project can be obtained using the sonet_group.get and socialnetwork.api.workgroup.list methods.
CRM. The template can pre-save links to CRM entities. In the UF_CRM_TASK field, specify the identifiers of CRM entities with a prefix, for example, L_15 for a lead or D_27 for a deal. Identifiers of existing entities can be obtained using the crm.item.list method. If the entity needs to be created first, use crm.item.add.
Checklists. If the typical task consists of recurring steps, add them to the template using the methods from the Task Template Checklists subsection.
Overview of Methods
Scope:
taskWho can execute the method: depending on the method
Main Methods
|
Method |
Description |
|
Adds a task template |
|
|
Modifies a task template |
|
|
Retrieves a task template by |
|
|
Deletes a task template |
|
|
Retrieves the description of task template fields |
Task Template Checklists
|
Method |
Description |
|
Adds a checklist item |
|
|
Updates a checklist item |
|
|
Retrieves a checklist item by |
|
|
Retrieves a list of checklist items |
|
|
Deletes a checklist item |
|
|
Moves an item after the specified one |
|
|
Moves an item before the specified one |
|
|
Marks an item as completed |
|
|
Returns an item to an incomplete state |
|
|
Adds an attachment from content |
|
|
Adds attachments from Drive |
|
|
Removes attachments from a checklist item |