--- title: "Lark Drive Integration" description: "Lark Drive is the cloud storage behind Lark, ByteDance's workplace suite. Agents upload and organize files, export live Lark documents to PDF or Word, import Office files as native documents, manage collaborators and share links, and read versions and comments." url: https://flowrunner.ai/integrations/larksuitedrive date_modified: 2026-09-04T14:07:24-07:00 --- # Lark Drive [Storage](https://flowrunner.ai/integrations/category/storage) Lark Drive is the cloud storage behind Lark, ByteDance's workplace suite. Agents upload and organize files, export live Lark 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 [Lark Drive website](https://www.larksuite.com/) · [Platform Documentation](https://open.larksuite.com/document/server-docs/docs/drive-v1/introduction) · Capability data verified 2026-08-13 1. A departure record lands from the HR system on somebody's last working day 2. List Files walks the folders they owned, and Get File Metadata reads the owner and last edited time on each 3. List Collaborators reads who else can already reach each document 4. Check Permission confirms the app may act on each file before the flow commits to a plan 5. Create Version saves a snapshot of every active document so today's state stays recoverable 6. Agent posts the proposed new owner for each file to the leaver's manager 7. The manager confirms who inherits each document before Transfer Ownership runs ## What This Integration Enables Lark Drive is the international side of ByteDance's workplace suite, and the first thing to settle is which side you are on. Lark runs on `open.larksuite.com`; Feishu is the China service on `open.feishu.cn`. The APIs are the same and the tenants are not, so a Lark app's credentials will not reach a Feishu workspace. If your organization is on Feishu, [Feishu Drive](https://flowrunner.ai/integrations/feishdrive) is the connector for you. Teams that run both operate two tenants and two connections on purpose, and a workflow has to know which one it is talking to. Past that, the thing that shapes every flow here is that a Lark document is a live object rather than a file. Documents, spreadsheets, Bases, and mindnotes come out through a render job and go in through an import job, which means the connector is best understood as the place where content changes state: an inbound Office file becomes something the team can edit together, and an outbound document becomes a frozen copy a client can keep. Agents handle both conversions, the folder structure around them, the collaborator lists that decide who is inside, and the comment threads a review leaves behind. FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) model reserves one class of operation for a person: the ones with no inverse the agent can call afterwards. ### Without FlowRunner **Ownership discovered at the worst time**: A document's owner turns out to be somebody who left, on the day the document is needed **Documents leave as copies**: Getting a Lark document to a client means downloading a copy that starts aging the moment it is sent **Reviews stall inside comment threads**: Unresolved threads sit on a document nobody currently has open ### With FlowRunner **Ownership handled at departure**: The leaver's files are enumerated, snapshotted, and reassigned as part of the offboarding flow **Documents leave as renders**: An export job produces the client copy while the live document stays the one the team maintains **Reviews chased by an agent**: List Comments finds what is still unresolved, and the agent answers it or raises it to a person ## Use Case Scenarios ### The client deliverable that does not go stale in an inbox A project reaches its reporting milestone. The agent assembles the numbers from the project's records in [Lark Base](https://flowrunner.ai/integrations/larksuitebase), writes them into the live report document, and calls Create Version so the state that went out is a named snapshot the team can return to. Create Export Task renders the report as PDF, Get Export Task is polled until it reports success, and Download Exported File retrieves the rendered copy for the client's channel. The client gets a document with a date on it. The team keeps editing the live one, and next month's export starts from wherever the document actually is rather than from somebody's saved copy. ### The inbound file that stops being an attachment A partner sends a spreadsheet. Instead of it sitting in a chat thread, the agent calls Upload File to place it in the right project folder and Create Import Task to convert it into a native Lark spreadsheet, polling Get Import Task for the token and URL. Add Collaborators In Bulk gives the working group edit access at the roles they should have, Add Comment records where the data came from and what was checked, and the [Lark Group Bot](https://flowrunner.ai/integrations/larksuitegrouprobot) posts the link into the project group. Because the file became a live object, three people can now be in it at once, and the version history starts at import rather than at the first person who remembered to save. ### The review that finishes itself Reviewers leave comments across a set of documents. On a schedule, the agent calls List Comments filtered to unresolved threads and List Comment Replies for the context of each. Where a thread asks a factual question the agent can answer from the project record, it calls Reply To Comment with the answer and the source, then Resolve Comment. Where a thread asks for a decision rather than a fact, it leaves the thread open and reports it as one of the [automation exceptions](https://flowrunner.ai/concepts/automation-exceptions) waiting on a person. Subscribe To File keeps it aware of new activity without polling every document in the space. ## Human-in-Loop Highlight Transfer Ownership is the operation on this connector with no inverse the agent can reach for. Once ownership of a document moves, the app may no longer have standing to move it back, and the setting that removes or demotes the previous owner takes their access with it. Run that across a leaver's folder tree on a bad guess and you have quietly reassigned a year of a team's work to whoever the automation thought was closest. So the offboarding agent does the whole job except the last call. It enumerates every file the leaver owned, reads who already collaborates on each, snapshots the active ones with Create Version, and proposes an inheritor per file from the collaborator list. Then it asks the manager: "Priya's last day is Friday. 34 documents, 9 folders. I have proposed Daniel as owner for the 21 files he already edits, and the operations lead for 11 more. Two have no other collaborator at all: the FY forecast model and the vendor rate card. Confirm the list, or tell me who takes those two?" The agent moves 34 files in one pass after that. It never picks an owner for a document only one person has ever opened. 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 ### Folders and File Objects 8 - **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. Not recursive, and paged. - **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 token and the 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 one document can appear in two places without being copied. ### Getting Bytes In and Out 5 - **Upload File** Uploads a file into a Drive folder from a URL your flow can reach. Single-call upload, capped at 20 MB. - **Download File** Downloads a file from Drive into flow file storage and returns a link to it. Real files only; live 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 fetches them directly instead of routing the bytes through the flow. ### Rendering Documents In and Out 5 - **Create Export Task** Starts rendering a document, spreadsheet, or Base into a downloadable file. The outbound half of the conversion, and how a client copy gets made. - **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 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 Lark document, spreadsheet, or Base. The inbound half of the conversion. - **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. ### Access and Ownership 7 - **List Collaborators** Lists everyone with access to a file or folder, and what each of them can do. - **Add Collaborator** Gives one person, department, group, or chat access to a file or folder at the role you choose. Optionally notifies them in Lark. - **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. - **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. This page's human gate sits here, because the agent cannot call it back. - **Check Permission** Asks whether the app itself may do a particular thing with a file. A guard that makes a flow fail at the start rather than halfway through. ### Link Sharing 5 - **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; the rest are left alone. - **Set Sharing Password** Puts a password on a file's sharing link. Lark 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. ### Readership 2 - **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. ### Snapshots 4 - **Create Version** Saves a named snapshot of a document as it stands. The call an agent makes before it edits anything, and before a copy goes to a client. - **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. ### Comment Threads 8 - **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. - **Update Comment Reply** Rewrites the text of a reply that was already posted. - **Delete Comment Reply** Removes a reply from a comment thread. ### Document Subscriptions 3 - **Subscribe To File** Subscribes the app to comment activity on a document, so Lark'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 Lark Drive? FlowRunner agents can run List Files, Get File Metadata, and Create Folder in Lark Drive, plus 44 more actions. ### Does connecting Lark Drive to FlowRunner require OAuth? Yes. Lark Drive connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Lark Drive trigger a FlowRunner workflow automatically? Lark Drive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Lark Drive?** This integration exposes Lark Drive to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/larksuitedrive. Site index: https://flowrunner.ai/llms.txt