create_task
Creates a new task in Planfix. Set name, dates, assignees, priority, custom fields, and more to define the task details.
Instructions
Создать задачу
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "create_task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Task number. For create requests this field is usually omitted. | |
| name | No | Task name. | |
| files | No | Existing Planfix files attached to the task. Each item must contain an existing file id. | |
| object | No | Task object. Specify an existing object by number. | |
| parent | No | Parent task. Specify an existing task by number. | |
| status | No | Task status. Specify an existing task status by id. | |
| overdue | No | Whether the task is marked as overdue. | |
| project | No | Project where the task belongs. Specify an existing project by number. | |
| assigner | No | Task assigner. Specify an existing employee by number. | |
| auditors | No | Task auditors. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92. | |
| dateTime | No | Task creation date and time as TimePoint. | |
| duration | No | Task duration value. The unit is defined by durationUnit. | |
| priority | No | Task priority. Use Urgent for urgent tasks and NotUrgent for regular priority tasks. | |
| template | No | Task template. Specify an existing task template by number. | |
| assignees | No | Task assignees. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92. | |
| isDeleted | No | Whether the task is deleted. | |
| isSummary | No | Whether the task is a summary task. | |
| processId | No | Task process id. | |
| hasEndDate | No | Whether the task has a due date. | |
| description | No | Task description. | |
| endDateTime | No | Task due date and time as TimePoint. | |
| inFavorites | No | Whether the task is in favorites. | |
| counterparty | No | Task counterparty. Specify an existing contact/company by number. | |
| durationType | No | How duration is calculated: CalendarDays for calendar days or WorkerDays for working days. | |
| durationUnit | No | Unit for task duration: Minute, Hour, Day, Week, or Month. | |
| hasStartDate | No | Whether the task has a start date. | |
| isSequential | No | Whether the task is marked as sequential, meaning it participates in a sequential task/subtask chain where the next task is activated after the previous one is completed or becomes inactive. | |
| participants | No | Task participants. Specify employees or contacts in users and groups in groups. Employee/contact identifiers must be prefixed, for example user:5 or contact:92. | |
| startDateTime | No | Task start date and time as TimePoint. | |
| resultChecking | No | Whether the task requires mandatory result checking. | |
| sourceObjectId | No | Unique identifier of the specific object in the third-party application or system. | |
| closeToDeadLine | No | Whether the task is close to its deadline. | |
| customFieldData | No | Custom field values for the task. Each item contains a custom field id in field.id and its value. | |
| delayedTillDate | No | Date and time until which the task is delayed/postponed as TimePoint. | |
| notAcceptedInTime | No | Whether the task was not accepted in time. | |
| sourceDataVersion | No | Version of the object data in the third-party application or system. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| result | Yes |