Feishu Drive Tool
Single tool feishu_drive for cloud storage operations across Feishu Drive folders and files.
Workflow
- Extract
folder_tokenfrom a Feishu Drive URL when you are targeting a specific folder. - Start with
listto confirm what the bot can actually access. - Use
infoto inspect a specific file before moving or deleting it. - Apply the minimal file operation needed (
create_folder,move,delete). - Re-list the target folder to verify the result.
From URL https://xxx.feishu.cn/drive/folder/ABC123 -> folder_token = ABC123
Actions Summary
| Action | Description |
|---|---|
list |
List root or folder contents |
info |
Get file metadata by token and type |
create_folder |
Create a folder at root or inside a parent folder |
move |
Move a file into a target folder |
delete |
Delete a file or Drive item by token and type |
File Types
| Type | Description |
|---|---|
doc |
Old format document |
docx |
New format document |
sheet |
Spreadsheet |
bitable |
Multi-dimensional table |
folder |
Folder |
file |
Uploaded file |
mindnote |
Mind map |
shortcut |
Shortcut |
Key Constraints
info,move, anddeleterequire the correcttypefor the target object.infodoes not recursively search Drive; browse withlistfirst when the location is uncertain.- Bots do not have a normal user root folder. Shared folder access is the practical starting point for most bot workflows.
Configuration
channels:
feishu:
tools:
drive: true # default: true
Required permissions:
drive:drive- Full access (create, move, delete)drive:drive:readonly- Read only (list, info)
Known Limitations
- Bots have no root folder: Feishu bots use
tenant_access_tokenand don't have their own "My Space". The root folder concept only exists for user accounts. This means:create_folderwithoutfolder_tokenwill fail (400 error)- Bot can only access files/folders that have been shared with it
- Workaround: User must first create a folder manually and share it with the bot, then bot can create subfolders inside it
Guardrails
- Use local or trusted tools only; avoid untrusted install pipelines.
- Do not paste secrets/tokens into chat output.
- Keep outputs in deterministic local paths for reproducible review.