1.8 KiB
1.8 KiB
task +update
Prerequisites: Please read
../lark-shared/SKILL.mdto understand authentication, global parameters, and security rules.
Update an existing task in Lark.
Recommended Commands
# Update task summary
lark-cli task +update --task-id "<task_guid>" --summary "New Summary"
# Update multiple tasks' due dates
lark-cli task +update --task-id "<task_guid>,<another_task_guid>" --due "+2d"
# A task applink is accepted directly; the CLI extracts its guid query value
lark-cli task +update --task-id "https://applink.larksuite.com/client/todo/task?guid=<task_guid>" --summary "New Summary"
# Update with JSON data
lark-cli task +update --task-id "<task_guid>" --data '{"description": "New description"}'
Parameters
| Parameter | Required | Description |
|---|---|---|
--task-id <guid-or-applink> |
Yes | Task OpenAPI GUID or a task applink containing guid=. Comma-separated GUIDs/applinks are supported for multiple tasks. Display task IDs such as t104121 / suite_entity_num are rejected. |
--summary <text> |
No | New summary/title for the task. |
--description <text> |
No | New description for the task. |
--due <time> |
No | New due date (supports relative time). |
--data <json> |
No | JSON payload for fields to update. |
Workflow
- Confirm with the user the tasks to update and the fields.
- Execute
lark-cli task +update --task-id "..." ... - Read
data.updated_fieldsanddata.tasks[].confirmedfrom the result and report only the fields confirmed by the server. - Do not routinely call
task tasks getafter the update whenconfirmedalready contains the required state. Query details only if a required field is absent or the user explicitly asks for a full verification.
Caution
This is a Write Operation -- You must confirm the user's intent before executing.