lark-approval

First run lark-cli approval tasks query with topic 1 to get the instance_code and task_id of the pending task, then run lark-cli approval tasks approve with both values plus an optional comment and the --yes flag to confirm the write operation.

Follow the fixed chain: search launchable definitions with approvals search, read the definition with approvals get to learn form controls and node requirements, then call instances create with the assembled form JSON and any required node_approver_list entries.

lark-approval handles approval documents, instances, and approval to-dos such as approve, reject, transfer, and rollback. Non-approval tasks and general to-dos belong to lark-task; approval-related items should never be routed there.

Error 1395001 means the task state changed or the write precondition failed, often because someone else already processed the task. Stop retrying, optionally run one status query with tasks query or instances get, then report the conclusion to the user.

No. Creating approval definitions must be done in the Feishu client or admin console, and third-party definitions (is_external=true) cannot use instances create; the skill returns the create_link so the user initiates through the external link.

Unsupported controls include text, mutableGroup, account, serialNumber, tripGroup, and several HR control groups such as onboarding, regularation, remedy, job adjust, and offboarding groups. Definitions containing these cannot be fully submitted through the API.