update_subtasks
Modify a task's subtasks by adding, completing, reopening, renaming, or removing them; requires full access.
Instructions
Add, complete, reopen, rename or remove subtasks of a task. Requires full access.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| add | No | new subtask titles, appended | |
| remove | No | subtask ids or titles to delete | |
| rename | No | {id or title: new title} | |
| reopen | No | subtask ids or titles to mark not done | |
| task_id | Yes | ||
| complete | No | subtask ids or titles to mark done |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| done | No | ||
| frog | No | Eat the Frog: 1 frog, 2 baby, 3 monster | |
| note | No | ||
| type | No | task | |
| title | Yes | ||
| labels | No | ||
| parent | Yes | path like 'Work > Client A > Website', or 'Inbox' | |
| do_date | No | Do date: the day it is scheduled for | |
| done_at | No | ||
| due_date | No | Due date: hard deadline | |
| end_date | No | End date: self-imposed target | |
| priority | No | low, mid or high (projects) | |
| subtasks | No | done/total, e.g. '1/3' | |
| tracking | No | time tracking running now | |
| parent_id | No | ||
| recurring | No | ||
| backburner | No | ||
| created_at | No | ||
| depends_on | No | titles of blocking items | |
| importance | No | 3 = P1 red, 2 = P2 orange, 1 = P3 yellow | |
| open_tasks | No | ||
| start_date | No | ||
| updated_at | No | ||
| review_date | No | ||
| subprojects | No | ||
| estimate_min | No | Duration estimate in minutes | |
| note_preview | No | ||
| other_fields | No | fields not modelled by the server | |
| planned_week | No | ||
| subtask_list | No | ||
| daily_section | No | ||
| planned_month | No | ||
| first_scheduled | No | ||
| minutes_tracked | No |