Resources · Make integration

Lark Document Make integrationAutomate Lark Document with Make.

Turn events from your other tools into Lark documents without copying a line by hand. The Lark Document Make integration gives you 12 modules: 11 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Try the Lark Document integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Lark Document Make integration?

The Lark Document Make integration lets a scenario, the automation you build in Make, create, find, read and edit cloud documents in Lark. Each step of a scenario is a module, one brick that does one job. Here all 12 modules are actions or searches, so another app or a schedule starts the flow.

A document per new request. A support ticket or a form answer lands in another app, Create a Cloud Document opens a fresh document and Create a Text Block writes the details into it. Nobody retypes anything.

Content that feeds other tools. Get a Document Content in MD Format hands the text of a document to the next module, for example to post it in a chat channel or store it in a spreadsheet. Search a Cloud Document finds the right file first when you only know its name.

Targeted edits. Get a Child Block and Get a Block Content let you locate one piece of a document, then Update a Block Content or Delete a Block changes only that piece.

Make itself warns that its documentation for this app is limited, because little public information about Lark Document exists. Expect to test each module with Run once before you trust it. When a listed module falls short, Make an API Call reaches the rest of the API with the same connection. If you also use n8n, see n8n vs Make; to learn the editor step by step, the Make training is the next stop, and Make pricing explains how operations are counted.

Connect

How do you connect Lark Document to Make?

  1. 01

    Add a Lark Document module

    In your scenario, add any Lark Document module, then click Create a connection. A connection is your Lark account linked to Make once and reused by every Lark Document module afterwards.

  2. 02

    Name it if you like

    Give the connection a name that tells you which account it points to, such as the team or workspace. It is optional, but it helps later when several people share the same Make organization.

  3. 03

    Authorize and save

    Approve access on the Lark page that opens, or paste the key Lark gives you if Make asks for one. Click Save, and the module can now list what your account is allowed to read.

First scenario

Your first scenario: open a Lark document for each new request

GoalWhen a new request arrives in another app, Make creates a Lark document and writes its details inside.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, such as your form tool, and choose its module for new entries.

  2. 02

    Create the document

    Click the + on the right of that first module, search Lark Document and add Create a Cloud Document. Click Create a connection and fill the fields Make shows you.

  3. 03

    Write the details

    Add Create a Text Block after it. Map the document returned by the previous module, then map the answers of the request into the text so every document starts filled.

  4. 04

    Test with Run once

    Send a test request, then click Run once. Each module shows the bundles it received, one bundle being one item passed along. Open the new document in Lark to check it.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Modules

What each Lark Document module does

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

Lark Document1

Create a Block

ActionIn the docs only

This module adds a new block to an existing Lark document, so a scenario can grow a page piece by piece instead of rewriting it.

When to use it
pick it for a block that is not plain text; for a simple paragraph, Create a Text Block is the more direct choice.
Watch out
Make publishes no field list for it, so run it once and check where the block lands.
Lark Document2

Create a Cloud Document

ActionIn the docs only

You get a brand new cloud document in Lark, ready for the next modules to fill. It is usually the first Lark step of a scenario that produces documents.

When to use it
a new client, ticket or project appears in another app and deserves its own page.
Watch out
map the document it returns into the following modules, otherwise they will not know which file to write into.
Lark Document3

Create a Text Block

ActionIn the docs only

Writes text into a Lark document as a new block, which is how data from a form, a CRM or an email ends up readable on the page.

When to use it
right after Create a Cloud Document, to put the details of the request inside the file you just created.
Watch out
each run adds a block; if the scenario processes the same item twice, the text appears twice.
Lark Document4

Delete a Block

ActionIn the docs only

Removes one block from a document and leaves the rest untouched, handy for clearing an outdated section automatically.

When to use it
a status block or a temporary note must disappear once a deal closes or a task is done.
Watch out
treat the deletion as final, and locate the right block first with Get a Child Block, testing on a copy of the document.
Lark Document5

Get a Block Content

ActionIn the docs only

Reads what one block contains, so the value can travel to another module, another app or a filter in the same scenario.

When to use it
you already know which block holds a figure or a status and only need that part, not the whole document.
Watch out
it reads a single block; for the full text of a page, Get a Document Content in MD Format fits better.
Lark Document6

Get a Child Block

ActionIn the docs only

Returns a block that sits under another one, which gives you the reference you need to read, update or remove a precise part of a page.

When to use it
before Update a Block Content or Delete a Block, when the scenario must find its target inside a structured document.
Watch out
read its output with Run once before mapping it, since the documentation stays silent on what it sends back.
Lark Document7

Get a Document

ActionIn the docs only

Fetches one Lark document by reference so the following modules can work on it without searching again.

When to use it
another app already stores the document reference, for instance on a client record, and the scenario needs that exact file.
Watch out
when all you have is a title, run Search a Cloud Document first, because this module needs to know which document you mean.
Lark Document8

Get a Document Basic Information

ActionIn the docs only

Gives the scenario the main details about a document without pulling its whole content, a light way to check a file before acting on it.

When to use it
you want to log or display which document was touched, or route the flow with a filter based on those details.
Watch out
Make does not list the details returned, so inspect the bundle after Run once before mapping anything.
Lark Document9

Get a Document Content in MD Format

ActionIn the docs only

Hands you the text of a whole document in Markdown, a plain format with light formatting that most tools can read or display.

When to use it
a published procedure or meeting note should be copied into a chat message, a knowledge base or another document.
Watch out
a long document produces a long bundle; check that the next app accepts that amount of text.
Lark Document10

Make an API Call

ActionIn the docs only

Opens the rest of the Lark Document API to your scenario, reusing the connection you already created, for anything the other 11 modules do not offer.

When to use it
you need an operation that no listed module covers and you know which endpoint of the API handles it.
Watch out
you write the request yourself, so keep the Lark API reference open while you set it up.
Lark Document11

Search a Cloud Document

SearchIn the docs only

Looks for cloud documents in Lark and returns what it finds, so the scenario can work on files you did not create in the same run.

When to use it
you only know a document by its name, and the next module needs the file itself.
Watch out
a search can return zero, one or several bundles; the next modules then run once per bundle, so narrow the search or add a filter.
Lark Document12

Update a Block Content

ActionIn the docs only

Replaces what a block says with new content, so a live document stays current without anyone editing it by hand.

When to use it
a status, a total or a date on a shared page must follow what changes in your CRM or project tool.
Watch out
the old content is overwritten; target the block with Get a Child Block and confirm it with Run once first.
Need help

Need help automating Lark Document with Make?

A person reads every message.

FAQ

Questions about the Lark Document Make integration

01Is the Lark Document Make integration free?
Yes, Lark Document is a standard app, so it works on the Make Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in credits, meaning operations, per month. Your Lark subscription is a separate matter.
02What do you need to connect Lark Document to Make?
A Lark account and a Make account are enough to start, since the documentation lists no other prerequisite. Add any Lark Document module, click Create a connection, give it a name if you want, then approve access on the Lark page or paste the key Lark provides, and click Save. The connection is created once and every Lark Document module in your scenarios reuses it. Make notes that its documentation for this app is limited, so test the connection with Run once.
03Can a Lark Document scenario start on its own?
Not from Lark Document itself: the app has no trigger module in Make, only 11 actions and 1 search. The scenario therefore starts elsewhere. Either another app launches it, such as a form tool or a CRM whose trigger watches for new items, or you rely on the schedule of the first module, every 15 minutes by default. On the Free plan the interval cannot go below 15 minutes; paid plans allow 1 minute. The Lark modules then run on each bundle that arrives.
04What if a Lark Document module is missing in Make?
Use Make an API Call. It calls any endpoint of the Lark Document API from your scenario with the same connection, so an operation missing from the 12 listed modules is still within reach. You will need to build the request yourself, with the Lark API reference at hand. Keep in mind that Make describes its own documentation for this app as limited, which is one more reason to check every new module with Run once before activating the scenario.
05Should you use Make or n8n for Lark Document?
It depends on the tool your team already works in. On Make, Lark Document offers 12 modules, all actions or searches, plus Make an API Call for the rest of the API, and it runs on the Free plan. The same app often has an n8n node too, so the right choice is usually the platform where your other automations already live. Compare the modules each side offers for the exact documents and blocks you need to handle before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations