Lark Task Management

1. API Basic Information

https://open.feishu.cn/open-apis/task/v2

Authorization: Bearer {tenant_access_token}

application/json

2. Task Operations

1. Create Task

POST /open-apis/task/v2/tasks

{
  "summary": "任务标题",
  "description": "任务详细描述",
  "due": {
    "timestamp": "1770508800",
    "is_all_day": false
  },
  "members": [
    { "id": "ou_xxx", "role": "assignee" }
  ],
  "origin": {
    "platform_i18n_name": "{\"zh_cn\": \"AI Agent\"}"
  }
}

• Must assign an assignee, otherwise there will be no reminder on mobile and users won't see the task

• due.timestamp

  is a 13-digit millisecond string (e.g., "1770508800000"). Note: If you pass a 10-digit second-level timestamp, the task due date will be set to 1970.

• origin

  marks the task source for easy traceability

2. Complete Task

POST /open-apis/task/v2/tasks/:task_id/complete

3. Update Task

PATCH /open-apis/task/v2/tasks/:task_id

{
  "task": {
    "summary": "更新后的标题"
  },
  "update_fields": ["summary"]
}

update_fields

3. Task Comments

4. Add Task Comment

POST /open-apis/task/v2/tasks/:task_id/comments

{ "content": "已完成审计，结果正常" }

4. Task Attachments

5. Attach Task Files

POST /open-apis/task/v2/tasks/:task_id/attachments

{ "file_token": "..." }

file_token

feishu-drive

5. Best Practices

1. Must Assign Assignee: Always specify an assignee when creating a task, otherwise it's equivalent to not creating it
2. Mark Source: Use the

   origin

   field to mark tasks created by AI Agent, making it easy to distinguish between manual and automated tasks
3. Closed-Loop Management: Call the complete API to close the task after the automated process is completed
4. Comment for Traceability: Record key execution nodes via comments to form an audit trail
5. Attachment Association: Attach deliverables such as reports and design drafts to tasks as attachments