Feishu Drive

Feishu Drive is the cloud storage behind Feishu, ByteDance's workplace suite. Agents upload and organize files, export live Feishu documents to PDF or Word, import Office files as native documents, manage collaborators and share links, and read versions and comments.

47 actions OAuth available

Feishu Drive website Platform Documentation Capability data verified 2026-08-13

An upstream flow finishes a supplier quality report as a Word file

Upload File puts the report into the plant team's Drive folder

Create Import Task turns the uploaded file into a live Feishu document

Get Import Task confirms the render succeeded and returns the new document's token

Add Collaborators In Bulk gives the plant and sourcing leads edit access

Add Comment posts the summary and the open questions on the document itself

Before the document is opened to a link a supplier can reach, a person decides how far outside it may travel

What This Integration Enables

Two things about Feishu Drive decide how a workflow should treat it, and neither is a feature.

The first is which tenant you are on. Feishu is the China service on open.feishu.cn; Lark is the international one. The APIs match, the tenants do not, and a Feishu app's credentials will not authenticate against Lark. If your organization runs on Lark, Lark Drive is the connector you want. The second is that a Feishu document is not a file. A document, spreadsheet, Base, or mindnote is a live object, so getting one out means rendering it through an export job and getting an Office file in means running an import. That makes this connector less a drive and more a controlled boundary between the Feishu world and everything outside it.

FlowRunner agents work both directions of that boundary. They file what a flow produces into a real folder, turn an inbound Word file or spreadsheet into a native document people can actually edit, render a document back out as PDF when a partner needs one, manage who is a collaborator as a project opens and closes, and read the comment threads a review left behind. Crossing the boundary outward is exactly where the human-in-the-loop gate belongs, because a link that leaves the organization does not come back.

Without FlowRunner

Reports that live in chat Documents get pasted into a group chat and are unfindable a month later

Exports done by hand Getting a Feishu document out as PDF means somebody opening it and using the menu

Access granted and forgotten People are added to a document for one project and are still on it two years later

With FlowRunner

Filed where people look Output lands in a real Drive folder as a live document, not as an attachment somebody has to save

Exports run as a job Create Export Task, Get Export Task, and Download Exported File make the render a step in a flow

Access reviewed on a schedule List Collaborators reads who still has reach, and Remove Collaborator acts on the answer

Use Case Scenarios

An inbound spec becomes a document the team can work in

A supplier sends a specification as a Word file. The agent calls Upload File to put it in the sourcing folder, then Create Import Task to convert it into a live Feishu document, polling Get Import Task until the job reports success and hands back the new document's token and URL. Add Collaborators In Bulk gives the engineering and quality reviewers edit access in one call, Add Comment states what changed against the previous revision, and the Feishu Group Robot drops the document link into the sourcing group so the review starts where the team already is. Nobody downloaded an attachment, and nobody has a private copy that will drift.
The document a partner needs, rendered rather than copied

A partner outside Feishu asks for the current quality manual. Because Download File only works on real files, the agent calls Create Export Task to render the document as PDF, polls Get Export Task until it reports success, and calls Download Exported File with the token that returned. The rendered PDF goes out to the partner's system, or into Box where the joint program keeps its shared records. The live document stays inside Feishu, still owned by the team that maintains it, and the partner gets a snapshot rather than a standing door.
Closing a project down properly

A program ends. The agent walks the program folder with List Files, and for each document calls Get Sharing Settings to read how far it is currently open and List Collaborators to read who can reach it. It assembles one report: three documents open to anyone with the link, eleven collaborators who have left the program, two documents whose view counts from List View Records suggest they were never used. Remove Collaborator handles the people. The link settings do not get changed by the agent at all, because tightening the wrong document mid-audit is its own kind of outage, and loosening one is worse.

Human-in-Loop Highlight

Update Sharing Settings is the operation that decides whether a document can leave the organization. It is one call, it takes effect the moment it lands, and once a link has traveled there is no way to un-see the file on the other end. Feishu also lets that call govern who may copy, print, and download, so a single agent decision can turn an internal draft into something a supplier can pass on. So the agent gathers and stops. It reads the current settings, the collaborator list, and the view history, then asks the program owner in the sourcing group: "Supplier CN-4417 has requested the Q3 quality manual. It is currently internal only, 14 collaborators, 0 external views. Opening it to link access outside the organization is what they are asking for. Approve external link access, or should I export it as a PDF and send that instead?" The second option is usually the right one, and the agent already knows how to do it. What it does not do is make the choice about the organization's boundary on its own.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

47 actions

Files and Folders

List Files Lists what is inside a Drive folder: files, documents, spreadsheets, Bases, mindnotes, subfolders, and shortcuts. Leave the folder empty to list the root of the app's own space. This does not recurse, and returns one page at a time with a token for the next.
Get File Metadata Looks up the title, owner, type, created and last edited time of up to 200 files in one call. Each entry needs both the file token and its type, since Drive stores the two together.
Create Folder Creates a folder inside another folder. Leave the parent empty to create it at the root of the space.
Copy File Copies a file, document, spreadsheet, Base, or mindnote into a folder under a new name. Folders cannot be copied.
Move File Moves a file or folder into another folder. Moving a folder moves everything inside it, and Drive runs that asynchronously, returning a task ID.
Delete File Moves a file or folder to the trash. Deleting a folder takes everything inside it, and Drive runs that asynchronously, returning a task ID.
Check Async Task Checks whether an asynchronous move or delete has finished. Pass the task ID that Move File or Delete File returned.
Create Shortcut Creates a shortcut in a folder that points at a file elsewhere, so the same document can appear in two places without being copied.

Uploads and Downloads

Upload File Uploads a file into a Drive folder from a URL your flow can reach. This is the single-call upload, capped at 20 MB.
Download File Downloads a file from Drive into flow file storage and returns a link to it. This works on real files only; documents need an export first.
Upload Media Uploads an image or attachment to be embedded inside a document, spreadsheet, or Base rather than stored as a file in a folder. Returns a media token.
Download Media Downloads an image or attachment embedded in a document into flow file storage and returns a link to it.
Get Temporary Media Links Returns short-lived download links for up to 5 media tokens at once, so a downstream step can fetch them directly instead of routing the bytes through the flow.

Export and Import

Create Export Task Starts rendering a document, spreadsheet, or Base into a downloadable file. This is how a Feishu document leaves as Word or PDF.
Get Export Task Checks how an export is going. Once the job reports success, the response carries the token of the rendered file.
Download Exported File Downloads the file an export produced into flow file storage. Use the file token from Get Export Task, not the token of the original document.
Create Import Task Turns a file already uploaded to Drive into a live Feishu document, spreadsheet, or Base. The inbound half of the boundary.
Get Import Task Checks how an import is going. Once the job reports success, the response carries the token and the URL of the new document.

Collaborators and Permission

List Collaborators Lists everyone with access to a file or folder, and what each of them can do. The read behind every access review.
Add Collaborator Gives one person, department, group, or chat access to a file or folder at the role you choose. Optionally notifies them in Feishu.
Add Collaborators In Bulk Gives several people access to the same file in one call, each with their own role.
Update Collaborator Changes what an existing collaborator may do with a file or folder.
Remove Collaborator Takes away someone's access to a file or folder. The operation that actually closes a project down.
Transfer Ownership Makes someone else the owner of a file or folder. By default the previous owner keeps access; you can have them removed or demoted instead.
Check Permission Asks whether the app itself may do a particular thing with a file. Used as a guard so a flow fails at the start rather than halfway through.

Link Sharing

Get Sharing Settings Reads how a file is shared: who can open the link, who may copy, print, or download it, who may comment, and whether it can leave the organization.
Update Sharing Settings Changes how a file is shared. Only the settings you supply are changed. This is the operation that opens a document to a link, and this page's human gate sits on it.
Set Sharing Password Puts a password on a file's sharing link. Feishu generates the password and returns it; you do not choose it.
Refresh Sharing Password Replaces a file's sharing link password with a newly generated one, which invalidates the old one.
Remove Sharing Password Takes the password off a file's sharing link, so anyone the link reaches can open it without one.

Activity

Get File Statistics Reads how much a document has been looked at: total views, unique viewers, and the same counts since the counter was last reset.
List View Records Lists who has opened a document and when. Available for documents, spreadsheets, and Bases.

Versions

Create Version Saves a named snapshot of a document as it stands, so it can be returned to later. Worth calling before an agent edits anything.
List Versions Lists the saved snapshots of a document, newest first.
Get Version Reads one saved snapshot of a document, including who created it and when.
Delete Version Removes a saved snapshot from a document's version history. The document itself is untouched.

Comments

List Comments Lists the comments on a document, with their replies. Filter to whole-document comments or to the ones still unresolved.
Get Comment Reads one comment and its replies.
Add Comment Adds a comment on a document as a whole. The text becomes the first reply in the new thread.
Resolve Comment Marks a comment resolved, or reopens one that was resolved.
List Comment Replies Lists the replies in one comment thread.
Reply To Comment Adds a reply to an existing comment thread. Used when an agent has the answer a reviewer asked for.
Update Comment Reply Rewrites the text of a reply that was already posted.
Delete Comment Reply Removes a reply from a comment thread.

Subscriptions

Subscribe To File Subscribes the app to comment activity on a document, so Feishu's Docs Assistant pushes updates about it. Returns a subscription ID.
Get File Subscription Reads whether a subscription on a document is currently active.
Update File Subscription Turns a document subscription on or off without deleting it.

Frequently Asked Questions

What can FlowRunner do with Feishu Drive?

FlowRunner agents can run List Files, Get File Metadata, and Create Folder in Feishu Drive, plus 44 more actions.

Does connecting Feishu Drive to FlowRunner require OAuth?

Yes. Feishu Drive connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Feishu Drive trigger a FlowRunner workflow automatically?

Feishu Drive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Feishu Drive

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us