Resources · Make integration

Lark Drive Make integrationAutomate Lark Drive with Make.

Files that land in the right Lark Drive folder without anyone dragging them there. The Lark Drive Make integration gives you 12 modules: 11 actions and 1 search. This guide connects your account, then walks you through a first scenario that files documents on its own.

Try the Lark Drive integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Lark Drive Make integration do for you?

The Lark Drive Make integration lets a Make scenario (the automation you build, a chain of modules) create folders, upload, copy, move and delete files in your Lark Drive. Each module is one brick of that chain. Lark Drive has no trigger in Make, so another app or a schedule starts the scenario.

A folder for every new client. When a deal closes in your CRM, Create a Folder opens a dedicated space in Lark Drive and Upload a File drops the signed contract inside. Nobody has to remember the naming rule.

Attachments that stop living in inboxes. An email or form app hands over a file, and Lark Drive stores it where the team expects it. If the file already sits in Drive, Move a File to a Folder puts it in its final place, while Copy a File keeps the original untouched for a template you reuse.

A cloud document ready before the meeting. Create a Cloud Document prepares a Lark document from data another app sends, and Search a Cloud Document finds existing ones so the scenario can check what is already there.

The official Make documentation for this app is short: it describes the connection, not the fields of each module. It also flags itself as AI-generated content that may contain mistakes. Test each module with Run once before trusting it with real folders. For anything the 12 modules leave out, Make an API Call reaches the Lark Drive API with the same connection.

Weighing tools first? Read the n8n vs Make comparison and the Make review. To learn scenario building step by step, the Make training starts from zero.

Connect

How do you connect Lark Drive to Make?

  1. 01

    Create an app in the Lark Developer Console

    You need a Lark developer account and an active Lark tenant. Open the Developer Console, click Create App and follow the prompts. Paste https://www.integromat.com/oauth/cb/larksuitedrive as the callback URI.

  2. 02

    Copy the Client ID and Client secret

    Your new Lark app shows a Client ID and a Client secret. Keep both at hand for the next step. These OAuth2 credentials are what lets Make act on your Lark Drive on your behalf.

  3. 03

    Add a Lark Drive module and create the connection

    In your scenario, add any Lark Drive module and click Create a connection. A connection is your Lark account linked to Make once, then reused by every Lark Drive module. Give it a name if you like, paste the credentials and follow the on-screen steps.

First scenario

Your first scenario: a Lark Drive folder per new client

GoalWhen another app hands over a new client file, Make creates a folder in Lark Drive and uploads the file into it.

  1. 01

    Start from the app that holds the file

    On the Scenarios page, create a new scenario and click the +. Pick the module of the app where new client files appear, such as your form tool or your CRM, and connect it.

  2. 02

    Add Create a Folder

    Click the + on the right, search for Lark Drive and choose Create a Folder. Create your connection, then map the client name from the first module so each folder carries it.

  3. 03

    Add Upload a File

    Add Upload a File after the folder module. Map the file coming from the first module, and point the destination to the folder that Create a Folder just returned.

  4. 04

    Test with Run once

    Click Run once and read the bundles each module received. A bundle is one item passed along, here one file. Check in Lark Drive that the folder and file both appeared.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module: a new scenario checks every 15 minutes by default, and the Free plan allows no shorter interval. Then turn the scenario on.

Modules

The 12 Lark Drive modules in Make

Lark Drive gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Lark Drive1

Copy a File

ActionIn the docs only

Duplicates a Lark Drive file so you get a second version to work on while the source stays as it was. Handy for a master contract or a quote template.

When to use it
a new project needs its own copy of a standard document, filled in later by the team.
Watch out
if you want the file to leave its current folder instead, choose Move a File to a Folder.
Lark Drive2

Create a Cloud Document

ActionIn the docs only

Produces a fresh Lark cloud document from your scenario, so a meeting brief or an onboarding page exists before anyone opens Lark. You feed it with data mapped from earlier modules.

When to use it
a new lead or ticket in another app should come with its own working document.
Watch out
the doc does not list the fields of this module, so run it once and inspect the result.
Lark Drive3

Create a Folder

ActionIn the docs only

Opens a new folder in Lark Drive, named with whatever your scenario maps in, a client, a project or an order number. The folder it returns can then receive files from the next module.

When to use it
every new account or case needs the same tidy home in Drive.
Watch out
each run creates a folder, so avoid starting the scenario twice for the same client.
Lark Drive4

Delete a File or Folder

ActionIn the docs only

Removes a file or a whole folder from Lark Drive once your scenario decides it has no reason to stay, for example a draft replaced by its final version.

When to use it
cleaning up temporary exports after another module has moved their content elsewhere.
Watch out
treat this module as final. Point it at a throwaway file during your Run once test, never at a folder your team uses.
Lark Drive5

Download a File

ActionIn the docs only

Pulls a file out of Lark Drive and hands its content to the following modules, so you can attach it to an email or send it to another storage app.

When to use it
a report saved in Drive has to reach a customer or a partner tool.
Watch out
on the Make Free plan, files are capped at 5 MB, so check the size of heavy videos or archives before you build around them.
Lark Drive6

Get a File

ActionIn the docs only

Fetches one specific Lark Drive file you already know, and makes it available as a bundle for the rest of the scenario to read or pass on.

When to use it
an earlier module gave you the file reference and you now need the file itself.
Watch out
if you only need facts about the file rather than the file, Get a File Metadata is the lighter choice.
Lark Drive7

Get a File Metadata

ActionIn the docs only

Reads the metadata of a Lark Drive file instead of the file content, which gives your scenario details to test in a filter or write into a log sheet.

When to use it
you want to check a file before deciding whether to move, copy or delete it.
Watch out
the Make doc does not say which details come back, so look at the output of a Run once test first.
Lark Drive8

Get a Folder

ActionIn the docs only

Looks up a Lark Drive folder so the scenario knows exactly where it stands before it adds, moves or removes anything inside.

When to use it
a later module needs the reference of an existing folder, say the shared finance space, rather than a new one.
Watch out
to open a folder that does not exist yet, use Create a Folder instead of this module.
Lark Drive9

Make an API Call

ActionIn the docs only

Calls any endpoint of the Lark Drive API from your scenario, reusing the connection you already set up. It covers what the 11 other modules leave out.

When to use it
you need a Drive operation that no listed module offers and you are comfortable reading API documentation.
Watch out
you build the request yourself, so check the Lark API docs for the path and body before you run it.
Lark Drive10

Move a File to a Folder

ActionIn the docs only

Relocates a Lark Drive file into another folder, so an invoice sitting in an inbox folder ends up in its archive without a second copy.

When to use it
a document changes status, from draft to approved, and should change place with it.
Watch out
the file leaves its first folder. Keep Copy a File for cases where both places need it.
Lark Drive11

Search a Cloud Document

SearchIn the docs only

Finds Lark cloud documents that match what you look for, so the scenario can reuse an existing page instead of creating a duplicate.

When to use it
before Create a Cloud Document, to check whether the client already has one.
Watch out
a search returns zero, one or several bundles, and every module after it runs once per bundle, which counts operations on your plan.
Lark Drive12

Upload a File

ActionIn the docs only

Sends a file from another app into Lark Drive, so attachments, exports and signed PDFs stop piling up in inboxes and land in a shared folder.

When to use it
a form, an email or an e-signature tool produces a file the team should find in Drive.
Watch out
map the file content from the previous module, not only its name, and remember the 5 MB file cap on the Free plan.
Need help

Need help automating Lark Drive with Make?

A person reads every message.

FAQ

Lark Drive and Make: common questions

01Is the Lark Drive Make integration free?
Yes, Lark Drive is a standard app in Make, so its modules work on the Free plan. That plan has limits you will feel quickly: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You also need a Lark account on your side, which follows Lark's own pricing.
02What do you need to connect Lark Drive to Make?
You need a Lark developer account and an active Lark tenant. In the Lark Developer Console, create an app, enter the Make callback URI and copy the Client ID and Client secret it shows. Back in Make, add any Lark Drive module, click Create a connection, paste those credentials and finish the on-screen authorization. The connection is then reused by every Lark Drive module in your scenarios. If authorization fails, check the callback URI in your Lark app first.
03Can Lark Drive start a Make scenario by itself?
No, Lark Drive has no trigger module in Make, so it cannot launch a scenario on its own. You start the flow another way. Either place the module of another app first, for example a form or a CRM that watches for new records, or run the scenario on Make's schedule, every 15 minutes by default. The Lark Drive modules then do their work in the steps that follow. Test the result with Run once before switching the scenario on.
04What if a Lark Drive module is missing in Make?
Use Make an API Call. This module reaches any endpoint of the Lark Drive API with the connection you already have, so a Drive operation outside the 12 listed modules is still within reach. You write the request yourself from the Lark API documentation. Keep in mind that the Make doc for this app is marked as AI-generated and may contain mistakes, so test each call with Run once before relying on it.
05Should you use Make or n8n for Lark Drive?
It depends on the tool your team already uses and on what you need to cover. On Make, Lark Drive comes with 12 modules and Make an API Call for anything missing, and runs on the Free plan within its limits. Many apps also have an n8n node, so check whether one exists for Lark Drive and what it offers before choosing. The n8n vs Make comparison linked above lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations