Resources · Make integration

Lark Base Make integrationAutomate Lark Base with Make.

Can Make keep your Lark Base tables filled without anyone typing? The Lark Base Make integration gives you 19 modules, 18 actions and 1 search, for records, tables and files. This page shows how to connect your account, build a first scenario and pick the right module.

Try the Lark Base integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Lark Base Make integration do?

The Lark Base Make integration links your Lark Base account to Make, so a scenario (the automation you build in Make, a chain of modules) can create, read, update and delete records, tables and files in your bases. Each module is one brick of that chain, and none of it needs code.

Requests that log themselves. A message or form answer arrives in another app, and Create a Record writes it as a new row, so support tickets stop living in inboxes.

Tables that stay current. A status changes in your CRM, Get a Record reads the matching row and Update a Record rewrites it. Nobody copies values between tools by hand.

Files that follow the data. Upload a Material sends a file into Lark Base, and Download a Material hands one to the next module, for a contract or a product photo tied to a row.

Know the limits before you start. Lark Base has no trigger module in Make, so your scenario starts from another app or from its own schedule. Make's documentation for this app is also marked as limited, and the modules come without official descriptions, so test each one on a sample table first. The same app may exist on n8n too; our n8n vs Make page lays out the criteria. For a guided start, see Make training, and when a run fails, Make troubleshooting.

Connect

How do you connect Lark Base to Make?

  1. 01

    Add a Lark Base module

    Inside your scenario, click the +, search for Lark Base and pick any of its modules. Then click Create a connection. A connection is your Lark Base account linked to Make once, then reused by every Lark Base module.

  2. 02

    Authorize Make

    Give the connection a name if you like, something that says which workspace it points to. Then follow the window: approve Make on the Lark page that opens, or paste the key Lark gives you if the form asks for one.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now list the objects it reads from your account, which is the quickest sign the connection works. Every other Lark Base module will offer this same connection.

First scenario

Your first scenario with Lark Base

GoalWhen a new request arrives in another app, Make writes it into Lark Base as a new record.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Start with a module of the app where requests arrive, since Lark Base has no trigger of its own.

  2. 02

    Add Create a Record

    Click the + on the right of that first module, search for Lark Base and choose Create a Record. Pick your connection, or click Create a connection if this is your first Lark Base module.

  3. 03

    Map the data

    Choose the base and table from the lists Make shows once the connection exists. Then map each value from the first module, so a bundle (one request) becomes one row.

  4. 04

    Test with Run once

    Click Run once and send a sample request. Open the bubble above each module to read the bundles it received, then check the new row in Lark Base.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, and each module run counts as one operation on your plan. Switch the scenario on.

Modules

What can Lark Base do in Make?

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

Lark Base1

Add a Data to a Table

ActionIn the docs only

Add a Data to a Table pushes fresh data into one of your tables, built from whatever earlier modules collected. Make gives no official description for it, so a first test tells you exactly how the table receives it.

When to use it
survey answers come in from a form tool and should land in the table your research team reads.
Watch out
Create a Record sits next to it in the list; try both on a sample table and keep the one whose result fits.
Lark Base2

Copy a File

ActionIn the docs only

Copy a File hands you a duplicate of an existing Lark file while the original stays untouched. It works like a template button you press from inside a scenario.

When to use it
a deal closes in your CRM and every new client needs a personal copy of the same onboarding file.
Watch out
each copy costs an operation, the unit Make counts on your plan, so filter the bundles before this module rather than copying on every run.
Lark Base3

Create a Bitable

ActionIn the docs only

Here the scenario builds a whole new Bitable, the base object named in these modules, instead of adding to one that already exists. New projects get their own space without anyone clicking through Lark.

When to use it
a project is approved in your planning tool and needs a dedicated place for its tasks and files.
Watch out
run it once per project, not once per bundle, or a busy source will leave you with a pile of empty Bitables.
Lark Base4

Create a Record

ActionIn the docs only

Create a Record writes one new row per bundle, which makes it the module most scenarios end on. Each value you map from earlier modules becomes a cell in that row.

When to use it
a lead fills in your website form and should show up as a row the sales team can work from.
Watch out
Make's doc mentions no duplicate check; if the same lead can arrive twice, look it up with List a Data Table before creating anything.
Lark Base5

Create a name of the entity

ActionIn the docs only

This module sets a name on an entity in Lark Base, a label the rest of the base can then show. Make's documentation gives nothing beyond that module name, so treat it as one to explore.

When to use it
after Create a Bitable, when a new object needs a readable name taken from your source data.
Watch out
run it on a test base first and look at the output in the bubble, since the doc does not say which entities it accepts.
Lark Base6

Delete a Data Table

ActionIn the docs only

Delete a Data Table removes a full table, so every row inside it goes too. It is the cleanup tool for tables a scenario created and no longer needs.

When to use it
a temporary table held imported rows for a campaign, and the campaign is closed in your project tool.
Watch out
plan as if a deleted table cannot come back; add a filter before this module and test it on a copy, never on live data.
Lark Base7

Delete a Field from a Record

ActionIn the docs only

Rather than dropping the whole row, Delete a Field from a Record clears a single field and leaves everything else in place. That keeps the history of a record while removing one value.

When to use it
a customer asks you to erase a phone number but the order row must stay for accounting.
Watch out
plan as if the cleared value cannot come back, so check with Get a Record that you target the right row first.
Lark Base8

Delete a Record

ActionIn the docs only

Delete a Record removes one row from a table for good. Paired with a search, it keeps a table free of entries that no longer matter.

When to use it
an order is cancelled in your shop and its row should disappear from the fulfillment table.
Watch out
treat the delete as final; when List a Data Table feeds this module, every row it returns gets removed, so narrow the search before you switch the scenario on.
Lark Base9

Download a Material

ActionIn the docs only

Download a Material pulls a file stored in Lark Base into your scenario, where the next module can send it, archive it or attach it somewhere else.

When to use it
a signed contract sits on a record and your storage app should keep a copy in the client folder.
Watch out
on the Free plan Make handles files up to 5 MB, so a large scan or video may fail here while small files pass.
Lark Base10

Get a Bitable Metadata Record

ActionIn the docs only

Get a Bitable Metadata Record reads the information that describes a Bitable rather than its rows. You get details about the base itself to reuse in the next modules.

When to use it
a report or message needs to mention the base it came from, with the details Lark keeps about it.
Watch out
the doc lists no output for this module; click Run once and read the bundle before you map anything from it.
Lark Base11

Get a Material for Temporary Download

ActionIn the docs only

Instead of moving the file itself, Get a Material for Temporary Download gives you access to it for a limited time, which suits sharing more than archiving.

When to use it
a teammate should open an attachment from a chat message without the scenario copying the file anywhere.
Watch out
as the name says, the access is temporary; if the file must be kept, use Download a Material and store it elsewhere.
Lark Base12

Get a Record

ActionIn the docs only

Get a Record reads one row you already know, and hands its values to the modules after it. It is the precise lookup, where List a Data Table is the broad one.

When to use it
an email reply references a ticket, and you need the current status of that exact row before answering.
Watch out
the module needs to know which row to read, so map it from an earlier module rather than typing it by hand.
Lark Base13

List a Data Table

SearchIn the docs only

List a Data Table is the only search module of Lark Base in Make: it returns zero, one or several bundles, one per item found, so later modules run once for each.

When to use it
before creating a lead, to see whether that contact already has a row in the table.
Watch out
with zero bundles the next modules have nothing to work on, and with many, each module placed after it spends one operation per bundle.
Lark Base14

Make an API Call

ActionIn the docs only

Make an API Call lets the scenario reach any endpoint of the Lark Base API through the connection you already set up. It covers what the other 18 modules do not.

When to use it
you need an operation that appears in the Lark developer docs but has no ready-made module in Make.
Watch out
here you write the request yourself, so keep the Lark API reference open and test with Run once on a sample table.
Lark Base15

Update a Bitable Metadata

ActionIn the docs only

Update a Bitable Metadata changes the information describing a Bitable, the pendant of Get a Bitable Metadata Record. The rows inside stay untouched.

When to use it
a project moves to a new phase in your planning tool and the base describing it should reflect that.
Watch out
the doc does not say which details can change; read them first with Get a Bitable Metadata Record, then update only what you mapped.
Lark Base16

Update a Data Table Record

ActionIn the docs only

Update a Data Table Record rewrites a row inside a data table with new values from your scenario, keeping the row where it is.

When to use it
a payment is confirmed in your billing app and the matching row in the invoices table should switch to paid.
Watch out
Update a Record looks close; with no official description for either, run both once on a sample row and compare the bundles before choosing.
Lark Base17

Update a Field

ActionIn the docs only

Update a Field works on the structure of a table, not on its content: it changes a field, the column every row shares. It helps when a base must adapt to a new process.

When to use it
a new sales stage is added in your CRM and the matching column in Lark Base should follow.
Watch out
every row sees the change at once, so try it on a copied table before touching the one your team works in.
Lark Base18

Update a Record

ActionIn the docs only

Update a Record changes values on an existing row, so a table mirrors what happens elsewhere without anyone editing it by hand.

When to use it
a shipment gets a tracking number in your logistics app and the order row should show it.
Watch out
the module needs the right row; find it first with List a Data Table or Get a Record, and remember a search with several results updates each of them.
Lark Base19

Upload a Material

ActionIn the docs only

Upload a Material sends a file from your scenario into Lark Base, so documents land next to the data they belong to.

When to use it
a supplier emails a quote as an attachment and it should be stored with the purchase row.
Watch out
the Free plan caps files at 5 MB and 512 MB of data transfer; heavy attachments may need a paid plan or a lighter format.
Need help

Need help automating Lark Base with Make?

A person reads every message.

FAQ

Lark Base and Make: common questions

01Is the Lark Base Make integration free?
Yes, Lark Base is a standard app, so it works on the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between 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, remove the cap on active scenarios and count usage in credits, which are operations, each month. Your Lark subscription is a separate matter.
02What do you need to connect Lark Base to Make?
A Lark account with access to the bases you want to automate, and a Make account. Make's documentation lists no specific prerequisite for this app. You add any Lark Base module, click Create a connection, name it if you want, authorize Make on the Lark page or paste the key Lark provides, then click Save. That single connection is reused by all 19 modules, so you only do it once per account.
03Can a Lark Base change start a Make scenario in real time?
No, not from Lark Base itself: the app has no trigger module in Make, neither scheduled nor instant. You start the scenario another way. Either a trigger from another app opens the flow, such as a new form entry or a new email, or the scenario runs on its own schedule, every 15 minutes by default, with List a Data Table as its first module to read what is in your table at that moment.
04What if a Lark Base module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Lark Base API with the connection you already have, so it covers operations the 18 other modules leave out. Keep in mind that Make marks its Lark Base documentation as limited and gives no official description per module, so run each new call once on a sample table and read the returned bundle before mapping it into the next steps.
05Should you use Make or n8n for Lark Base?
It depends on how you like to build. On Make, Lark Base offers 19 modules, including Make an API Call for anything uncovered, but no trigger, so scenarios start from another app or a schedule. The same app often has an n8n node as well, so compare the actions you actually need on both sides, then choose the editor your team is ready to maintain. Neither answer is right for every case.
Same platform

Other docs you might need on this stack.

Browse all integrations