Task Template Fields

REPLICATE_PARAMS Parameter

Choose a tool for developing with an AI agent:

use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

This page describes the fields of a task template object. For an overview of template methods, see Task Templates.

The fields in the table are used in requests to tasks.template.add and tasks.template.update, and are returned in responses from template methods. To retrieve the current field metadata for a specific account, use tasks.template.fields.

Choose the source according to your task:

Task Template Fields — to understand field purposes and allowed values
tasks.template.fields — to retrieve field metadata for a specific account
tasks.template.get — to retrieve saved template values by identifier
tasks.template.add and tasks.template.update — to pass fields when creating or updating a template

The field type in the table describes the REST API data format. The set and types of UF_* custom fields depend on the settings of a specific account.

Access to tasks is required to work with templates. Available actions and some field values depend on the user's permissions and account settings.

Name `type`	Description
ID `integer`	Template identifier. In tasks.template.add, the input field `ID` is ignored and removed before saving
PARENT_ID `integer`	Parent task identifier. Default is `0`
TITLE `string`	Template title
DESCRIPTION `string`	Template description
PRIORITY `enum`	Priority
GROUP_ID `integer`	Project identifier. Default is `0`
STAGE_ID `integer`	Stage identifier. Default is `0`
CREATED_BY `integer`	Creator identifier
RESPONSIBLE_ID `integer`	Responsible person identifier
DEPENDS_ON `array`	Array of template identifiers that the current template depends on. In the response from tasks.template.fields, this field is described as `integer`, but in examples and when passed to tasks.template.add and tasks.template.update, an array is used
RESPONSIBLES `array`	List of responsible persons
ACCOMPLICES `array`	List of participants
AUDITORS `array`	List of auditors
STATUS `enum`	Status
MULTITASK `enum`	Multitasking indicator. Possible values: `Y` — yes `N` — no Default is `N`
REPLICATE `enum`	Recurring task indicator. Possible values: `Y` — yes `N` — no Default is `N`
SITE_ID `string`	Site identifier
TASK_CONTROL `enum`	Accept work. Possible values: `Y` — yes `N` — no Default is `N`
ADD_IN_REPORT `enum`	Add to report. Possible values: `Y` — yes `N` — no Default is `N`
XML_ID `string`	External identifier. Default is `null`
DEADLINE_AFTER `datetime`	Deadline after. Default is `null`
START_DATE_PLAN_AFTER `datetime`	Planned start after. Default is `null`
END_DATE_PLAN_AFTER `datetime`	Planned completion after. Default is `null`
TPARAM_TYPE `enum`	For new users. Default is `0`
TPARAM_REPLICATION_COUNT `integer`	Number of created tasks. Default is `0`
REPLICATE_PARAMS `object`	Template replication parameters (detailed description)
BASE_TEMPLATE_ID `integer`	Parent template identifier. Default is `null`
TEMPLATE_CHILDREN_COUNT `integer`	Number of child templates. Default is `null`
UF_ fields* `object`	Custom fields of the object

To obtain a complete list of custom fields for a specific account, use the tasks.template.fields method.

REPLICATE_PARAMS Parameter

General Replication Parameters

Name `type`	Description
PERIOD `string`	Type of repetition. Possible values: `daily`, `weekly`, `monthly`, `yearly`
START_DATE `datetime`	Start date and time of repetition in the format `31.12.2026 14:00:00`
TIME `string`	Start time in the format `HH:MI`. Default is `05:00`
REPEAT_TILL `string`	Repetition end mode. Possible values: `endless` — repetition without date and count limits `times` — repetition limited by the number of runs in `TIMES` `date` — repetition until the date specified in `END_DATE`
TIMES `integer`	Number of repetitions. Used when `REPEAT_TILL = times`
END_DATE `datetime`	End date of repetition in the format `31.12.2026 14:00:00`. Used when `REPEAT_TILL = date`
NEXT_EXECUTION_TIME `datetime`	Date and time of the next execution
DEADLINE_OFFSET `integer`	Deadline offset relative to the start time

Parameters for Daily Repetition `PERIOD = daily`

Name `type`	Description
EVERY_DAY `integer`	Repetition interval in days. Value from `1`
WORKDAY_ONLY `string`	Consider only working days. Possible values: `Y`, `N`
DAILY_MONTH_INTERVAL `integer`	Additional interval for daily repetition. Value from `0`

Parameters for Weekly Repetition `PERIOD = weekly`

Name
type

Description

EVERY_WEEK
integer

Repetition interval in weeks.

Value from 1

WEEK_DAYS
array

Days of the week for execution.

Possible values for array elements: 1..7.

1 — Monday, 2 — Tuesday, 3 — Wednesday, 4 — Thursday, 5 — Friday, 6 — Saturday, 7 — Sunday

Parameters for Monthly Repetition `PERIOD = monthly`

Name `type`	Description
MONTHLY_TYPE `integer`	Type of monthly repetition. Possible values: `1` — by day of the month `2` — by day of the week
MONTHLY_DAY_NUM `integer`	Day of the month. Used when `MONTHLY_TYPE = 1`, value from `1`
MONTHLY_MONTH_NUM_1 `integer`	Month interval for the "by day of the month" scheme. Used when `MONTHLY_TYPE = 1`, value from `1`
MONTHLY_WEEK_DAY_NUM `integer`	Week number in the month. Used when `MONTHLY_TYPE = 2`, possible values: `0..4`. `0` — first week, `1` — second, `2` — third, `3` — fourth, `4` — last
MONTHLY_WEEK_DAY `integer`	Day of the week in the "by day of the week" scheme. Used when `MONTHLY_TYPE = 2`, possible values: `0..6`. `0` — Monday, `1` — Tuesday, `2` — Wednesday, `3` — Thursday, `4` — Friday, `5` — Saturday, `6` — Sunday
MONTHLY_MONTH_NUM_2 `integer`	Month interval for the "by day of the week" scheme. Used when `MONTHLY_TYPE = 2`, value from `1`

Parameters for Yearly Repetition `PERIOD = yearly`

Name `type`	Description
YEARLY_TYPE `integer`	Type of yearly repetition. Possible values: `1` — by day of the month `2` — by day of the week
YEARLY_DAY_NUM `integer`	Day of the month. Used when `YEARLY_TYPE = 1`, value from `1`
YEARLY_MONTH_1 `integer`	Month for the "by day of the month" scheme. Used when `YEARLY_TYPE = 1`, possible values: `0..11`. `0` — January, `1` — February, `2` — March, `3` — April, `4` — May, `5` — June, `6` — July, `7` — August, `8` — September, `9` — October, `10` — November, `11` — December
YEARLY_WEEK_DAY_NUM `integer`	Week number in the month. Used when `YEARLY_TYPE = 2`, possible values: `0..4`. `0` — first week, `1` — second, `2` — third, `3` — fourth, `4` — last
YEARLY_WEEK_DAY `integer`	Day of the week in the "by day of the week" scheme. Used when `YEARLY_TYPE = 2`, possible values: `0..6`. `0` — Monday, `1` — Tuesday, `2` — Wednesday, `3` — Thursday, `4` — Friday, `5` — Saturday, `6` — Sunday
YEARLY_MONTH_2 `integer`	Month for the "by day of the week" scheme. Used when `YEARLY_TYPE = 2`, possible values: `0..11`. `0` — January, `1` — February, `2` — March, `3` — April, `4` — May, `5` — June, `6` — July, `7` — August, `8` — September, `9` — October, `10` — November, `11` — December

Was the article helpful?

Overview of Methods

Add Task Template

Task Template Fields

REPLICATE_PARAMS ParameterREPLICATE_PARAMS Parameter

General Replication ParametersGeneral Replication Parameters

Parameters for Daily Repetition Parameters for Daily Repetition PERIOD = daily

Parameters for Weekly Repetition Parameters for Weekly Repetition PERIOD = weekly

Parameters for Monthly Repetition Parameters for Monthly Repetition PERIOD = monthly

Parameters for Yearly Repetition Parameters for Yearly Repetition PERIOD = yearly