After loading the workflow, treat the references/、scripts/、templates/、examples/ relative paths in it as being resolved relative to the
workflow.md directory where it is located; when executing scripts, use the resolved actual paths, and do not rely on the current shell directory.
Routing
| Intent | Read file |
|---|---|
| Large-file chunked upload, in-place overwrite upload, streaming/resumable download, URL or wiki-wrapped file download | references/workflows/drive/workflow.md |
Parse the type and title of a URL/bare token (drive inspect),rename a file/folder/document/wiki node (drive update-title) |
references/workflows/drive/workflow.md |
Version history of an uploaded file (type=file) and download by version (drive version-history/version-get) |
references/workflows/drive/workflow.md |
Asynchronous import/export and follow-up query (drive import/export/export-download/task-result), folder move, directory mirror (pull/push/status) |
references/workflows/drive/workflow.md |
Folder browsing and pagination, basic file CRUD, shortcuts, metadata/statistics, quota (file quota), document asset upload/download |
references/workflows/file-media/workflow.md |
Named versions of online documents (file version list/create/get/delete) and rollback of uploaded files (file version revert) |
references/workflows/file-media/workflow.md |
| wiki space, node parsing (obj_token/URL), create/move/copy/delete, cross-move between cloud drive and knowledge base, members, recursive export | references/workflows/wiki/workflow.md |
Comment list, read, reply, edit reply, emoji reaction, resolve and unresolve; create rich text/partial/cell/record/slide comments (drive add-comment) |
references/workflows/comment/workflow.md |
Collaborators, public permissions, sharing password, transfer ownership, permission check, automatic authorization after Bot creation (permission_grant); request permission from the owner (drive apply-permission), security label (drive secure-label) |
references/workflows/perm/workflow.md |
Search documents by folder, knowledge base, or creator (drive search) belongs to the search workflow of feishu-cli-platform .
Execution rules
/wiki/For links or tokens of unknown type, first usedrive inspect --urlto parse; for Bitable links usebitable resolve. Before handing a wiki node to a command that requires a node_token, first exchange it for a node_token (see rule 6).- For basic file operations, prefer file/media; use drive when chunking, resumable transfer, URL/wiki unwrapping, in-place overwrite, version history, mirroring, or asynchronous tasks are needed.
Historical versions of uploaded files (
drive version-history, long numeric version) and named versions of online documents (file version) must not be mixed up. - Delete, move, overwrite,
--delete-local/--delete-remote, transfer ownership, and deleting a knowledge space are high-risk operations: first confirm the target, then include the command's confirmation parameter; in a non-interactive environment, if--yesis not included (or the command-level--force),refuse to execute with exit code 10; this does not mean success.wiki deleteBy default, cascadingly deletes the entire subtree. - Identity: the entire perm group defaults to Bot; for operations on the user's own documents, add
--as user(do not readFEISHU_USER_ACCESS_TOKEN); when Bot reports 1063002/1063004, switch to User; file/wiki write operations default to Bot, and only explicitly recognize--user-access-token; Bot moving or deleting a user's own files will fail; comment read and add/resolve default to User first,comment reply add/update/react/deletedefaults to Bot and must have the same identity as the reply author;drive add-comment/secure-label/apply-permission、file quota、wiki space-createmust be User;drive upload/downloaddefaults to requiring User, and can--as bot。 - When a read-type or mirror command encounters 99991679 (User Token is missing the drive read scope), if the resource is visible to the corresponding user, explicitly
--as bot, otherwise supplement the authorization; when carrying--delete-*is present, a configured but unavailable User Token will fail-closed and will not downgrade to Bot. For asynchronous task follow-up queries, reuse the--as。 - wiki
get/update/move/export/export-tree/deleteaccepts node_token, the obj_token of an already-mounted document, or a URL;move-to-drive、node-copy、nodes --parent、drive update-title --type wiki、perm --doc-type wikionly accepts node_token, firstwiki getto convert it out. - After a file, folder, document, or wiki node is created under the Bot identity, it automatically grants the currently CLI-logged-in user
full_access(JSONpermission_grant); delivering to other people still requiresperm add。
When delete-type or overwrite-type commands return exit code 10, after confirming the target and impact with the user, append the global --yes rerun; do not add it yourself. For identity or scope errors (such as 99991663/99991668/99991672/99991679), read ../feishu-cli-platform/references/workflows/auth/references/identity.md; to determine success or failure, write scripts, or handle confirmation gates, read ../feishu-cli-platform/references/workflows/auth/references/agent-contract.md。