Feishu Drive Make integrationAutomate Feishu Drive with Make.
Can Make keep your Feishu Drive files in order without you touching them? The Feishu Drive Make integration gives you 12 modules: 11 actions and 1 search, for files, folders and cloud documents. This guide shows how to connect your account and build a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Feishu Drive Make integration do for you?
The Feishu Drive Make integration lets a Make scenario (the automation you build, a chain of modules) create folders, upload, copy, move and delete files, and search cloud documents in your Feishu Drive, with no code. Each module is one brick of that chain, and your account is linked once through a connection.
A client folder that builds itself. When a deal closes in your CRM or a form comes in, Create a Folder opens a folder for that client and Upload a File drops the first documents inside. Nobody has to remember the naming or the location.
Files that move to the right place. Pair Get a File Metadata with Move a File or Copy a File to read a file's details, then route it to an archive or share a copy with another team.
Documents ready before the meeting. Create a Cloud Document starts a document from data another app sends, and Search a Cloud Document finds the ones that already exist so you don't duplicate them.
Know the limits before you start. Feishu Drive has no trigger module, so a scenario starts from another app or from Make's schedule. Make's own documentation for this app is short, and it says so openly. When a listed module falls short, Make an API Call reaches other endpoints with the same connection. If you also weigh n8n, read our n8n vs Make comparison, and check Make pricing before you scale. For a guided start, the Make training walks through your first builds.
How do you connect Feishu Drive to Make?
- 01
Add a Feishu Drive module
In your scenario, click the +, search for Feishu Drive and pick any module, for example Create a Folder. In the module panel, click Create a connection. The connection is your Feishu Drive account linked to Make once, then reused by every module of the app.
- 02
Name the connection
Give the connection a name you will recognize later, such as the workspace or the team it belongs to. This step is optional, but it helps when several people or several accounts share the same Make organization.
- 03
Authorize Make and save
Make opens the Feishu page where you approve access, or asks for the key Feishu gives you. Confirm, then click Save. Back in the module, Make can now list the folders and files your account can read.
Your first scenario with Feishu Drive
GoalWhen another app hands over a new file, Make creates a folder in Feishu Drive and uploads the file into it.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. Since Feishu Drive has no trigger, pick the module of the app where files show up first, such as your form tool or your inbox.
- 02
Add Create a Folder
Click the + on the right of that first module, search for Feishu Drive and choose Create a Folder. Select your connection, then map the folder name from the data the first module received.
- 03
Add Upload a File
Add Upload a File after the folder module. Map the file coming from the first app, and point the destination to the folder that Create a Folder just returned, so each file lands in its own place.
- 04
Test with Run once
Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received (a bundle is one item, here one file), then check Feishu Drive for the new folder.
- 05
Schedule and switch on
On the first module, open Scheduling: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust if needed, then switch the scenario on.
What each Feishu Drive module does
Feishu Drive gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Copy a File
ActionIn the docs onlyYou get a second version of a file in another place while the original stays exactly where it was. That suits a template you duplicate for each new project, or a report you share with a team without giving up your own version.
Create a Cloud Document
ActionIn the docs onlyThis one hands you a fresh Feishu cloud document, started by the scenario instead of by a person. Data from another app, like a client name or a ticket subject, can feed it, so the document is waiting before anyone opens it.
Create a Folder
ActionIn the docs onlyA new folder appears in your Feishu Drive, named from the data the scenario carries. It is usually the first Feishu Drive brick of a flow, because the modules after it can drop files straight into the folder it returns.
Delete a File or Folder
ActionIn the docs onlyClutter disappears without a manual cleanup: the module removes the file or folder you point it to. It pairs well with a filter placed before it, so only the items that match your rule ever reach it.
Download a File
ActionIn the docs onlyThe file's content becomes available to the rest of your scenario, so another app can receive it as an attachment or a stored copy. It is the step to add whenever the next app needs the file's content rather than its location.
Get a File
ActionIn the docs onlyYou retrieve one specific file so the next modules can work on it. Reach for it when you already know which file you want, for instance because an earlier module or another app gave you its identifier.
Get a File Metadata
ActionIn the docs onlyInstead of the file itself, you get its details, which is enough to make a decision further down the scenario. Reading details is lighter than moving the full content around when all you need is to know what the file is.
Get a Folder Metadata
ActionIn the docs onlyThe scenario learns about a folder before it acts on it. That check helps when a flow depends on a folder that someone may have renamed or reorganized since the scenario was built.
Make an API Call
ActionIn the docs onlyAny endpoint of the Feishu Drive API becomes reachable from your scenario, with the connection you already set up. It is the way out when none of the eleven other modules covers what you need.
Move a File
ActionIn the docs onlyA file changes folder without leaving a copy behind, which keeps your drive tidy as work moves forward. Think of it as the step that files a document once its status has changed somewhere else.
Search a Cloud Document
SearchIn the docs onlyYou find the cloud documents that already exist before creating or updating anything. As a search, it can return zero, one or several results, and each result travels to the next module as its own bundle.
Upload a File
ActionIn the docs onlyA file coming from another app lands in your Feishu Drive, ready for the team. Attachments, form uploads and generated exports all fit, as long as an earlier module passes the actual file along.
Need help automating Feishu Drive with Make?
A person reads every message.
