Resources · Make integration

Feishu Base Make integrationAutomate Feishu Base with Make.

Can Make keep your Feishu Base tables up to date on its own? Yes. The Feishu Base Make integration offers 19 action modules for records, fields, tables and files. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Feishu Base integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Feishu Base Make integration let you automate?

The integration links your Feishu Base account to Make so that a scenario, the automation you build in Make, can write, change, copy and delete what lives in your Bitables: records, fields, data tables and attached files. Every step of a scenario is a module, and this app gives you 19 of them, all actions.

Leads logged without copy and paste. A form or CRM receives a contact, and Create a Record adds it as a new row in the sales table. Get a Record checks first whether that person is already there.

A ready-made Base for every new project. Copy a Bitable File duplicates a template, then Update Bitable Metadata renames the copy after the client. The team opens a clean file with the right tables already in place.

Files that travel on their own. Upload a Material stores a PDF or a photo in the Bitable, and Get a Link for Temporary Download of Materials produces a link to share with someone outside Feishu, valid for 24 hours.

What the app does not do in Make: it has no trigger, so Feishu Base cannot start a scenario by itself. The run begins with another app or with a schedule. To see how Make compares with other platforms, read our Make review and the n8n vs Make comparison, and check Make pricing before you plan volume.

Connect

How do you connect Feishu Base to Make?

  1. 01

    Prepare an app in the Feishu developer console

    You need a Feishu developer account and an active tenant. In the developer console, click Create enterprise internal app, give it a name, a description and an icon, then open Credentials and basic information.

  2. 02

    Copy the two credentials

    From that section, copy the Client ID and the Client secret. If Feishu asks for a callback URI, paste https://www.integromat.com/oauth/cb/feishubase so the authorization can come back to Make.

  3. 03

    Create the connection in Make

    Add any Feishu Base module to your scenario and click Create a connection. Naming it in Connection name is optional. Enter the credentials you copied and follow the on-screen steps. That connection, your account linked once, then serves every Feishu Base module.

First scenario

Your first scenario with Feishu Base

GoalWhen a new request comes in through your form tool, Make logs it as a record in Feishu Base and stores its attachment in the same Bitable.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Feishu Base has no trigger, so the first module belongs to the app where your requests arrive.

  2. 02

    Pick the starting module

    Search your form or CRM app by name, choose its trigger and link your account. Each new entry becomes a bundle, one item passed from a module to the next.

  3. 03

    Add Create a Record

    Click the + on the right of the first module, search Feishu Base and pick Create a Record. Connect your account, choose the table Make lists for you, then map each column to the matching answer from the form.

  4. 04

    Store the attachment

    Add Upload a Material after it and map the file received by the first module. On the Free plan Make handles files up to 5 MB, so large videos should stay out of this flow.

  5. 05

    Test with Run once

    Send a test entry through your form, then click Run once. Open the bundles each module received and confirm the row and the file both appear in Feishu Base.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What can each Feishu Base module do?

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

Feishu Base1

Add a Data to a Table

Action

In Make“Adds a data table. Only the name of the data table can be specified. A maximum of 100 data tables can be added.”

Your existing Bitable, the Base file that holds your tables, receives one more data table. You set its name and nothing else, so the columns get added afterwards with other modules.

When to use it
a new client signs and you want a table of its own waiting in the shared Base.
Watch out
the documentation caps this at 100 data tables, and despite the wording, the module does not add a row.
Feishu Base2

Add a [name of the entity]

Action

In Make“Adds a field to a Bitable data table.”

You get a new column in a Bitable data table without opening Feishu. Make displays this module under a placeholder title, but what it adds is a field.

When to use it
the table you just created with Add a Data to a Table needs its first columns, such as a status or an owner.
Watch out
a new field shows up for every row of the table, so agree on its name with the team before the scenario runs.
Feishu Base3

Copy a Bitable File

Action

In Make“Copies a Bitable.”

A template Base you built once turns into a fresh working copy, tables included, which spares you from rebuilding the structure by hand.

When to use it
every new customer gets the same onboarding Base, copied from a master file as soon as the deal closes in your CRM.
Watch out
keep the master file clean, because each copy starts from whatever it contains at that moment.
Feishu Base4

Create a API Call

Action

In Make“Performs an arbitrary authorized API call.”

When no ready-made module covers your need, this one sends an authorized request of your choice to Feishu Base, reusing the connection you already set up.

When to use it
Feishu offers an operation in its API that has no dedicated module in the list.
Watch out
you write the request yourself, so keep Feishu's API reference open while you build it and test it with Run once.
Feishu Base5

Create a Bitable

Action

In Make“Creates a Bitable with a blank data table.”

Starting from nothing, this module produces a brand-new Bitable with one blank data table inside, ready for fields and records.

When to use it
you prefer an empty file over a copy, for example when each event or campaign gets a tracking Base built by the scenario.
Watch out
the file arrives bare, so chain Add a [name of the entity] right after it, or pick Copy a Bitable File if a template already exists.
Feishu Base6

Create a Record

Action

In Make“Adds a record to a Bitable data table.”

Most Feishu Base scenarios end here: a new row, called a record, lands in a Bitable data table, filled with data mapped from earlier modules.

When to use it
a lead fills in a form, a support ticket opens or an order arrives in another tool, and the team wants it logged in Feishu Base.
Watch out
each record written costs one operation, so a scenario fed a long list spends one per row.
Feishu Base7

Delete a Data Table

Action

In Make“Deletes multiple data tables. If there is only one data table left in the Bitable, it is not allowed to be deleted.”

Old tables vanish from a Bitable, and this module can remove several of them in one pass even though its name is singular.

When to use it
a project closes and its temporary tables should leave the shared Base.
Watch out
Feishu refuses to delete the last table left in a Bitable Test on a copy first.
Feishu Base8

Delete a Field from a Record

Action

In Make“Deletes a field in a Bitable data table.”

A column disappears from a Bitable data table. The title mentions a record, yet the documentation describes a field removed from the table itself, so every row loses it.

When to use it
a helper column used during an import has served its purpose.
Watch out
the values stored in that column go with it; read them with Get a Record first if anyone might need them later.
Feishu Base9

Delete a Record

Action

In Make“Deletes a record in a Bitable data table.”

One row is erased from a data table, which keeps a Base tidy when the item it describes disappears from another tool.

When to use it
a customer cancels in your billing app and the matching line in Feishu Base should go as well.
Watch out
the module has to know which record to remove, so place Get a Record before it and try the flow on test data.
Feishu Base10

Download a Material

Action

In Make“Downloads materials from a Bitable.”

A file the team attached in a Bitable, an image, a video or a document, comes into your scenario so the next module can send it somewhere else.

When to use it
signed contracts collected in Feishu Base must also land in your accounting tool or on a shared drive.
Watch out
the Free plan limits files to 5 MB, so for heavy videos a link from Get a Link for Temporary Download of Materials may suit better.
Feishu Base11

Get a Bitable Metadata

Action

In Make“Retrieves metadata information of a specified Bitable.”

Rather than rows, this module reads the information Feishu keeps about a Bitable itself, the details that describe the file.

When to use it
before a scenario renames a file with Update Bitable Metadata, check what it is called today.
Watch out
Make's documentation does not spell out which details come back, so click Run once and read the output before mapping anything.
Feishu Base13

Get a Record

Action

In Make“Queries existing records in a data table.”

Existing rows of a data table come back to your scenario, so the modules after it can read, update or delete them.

When to use it
an email address arrives from a form and you want to know whether that contact already sits in the Base before creating a duplicate.
Watch out
the documentation says it queries records, plural, so test what it returns when nothing or several rows match.
Feishu Base14

List a Data Table

Action

In Make“Lists all data tables in a Bitable.”

You get the full list of data tables inside a Bitable, handy when a scenario has to find the right table among many.

When to use it
you want an inventory of what a shared Base contains before cleaning it up with Delete a Data Table.
Watch out
run it once with Run once and look at how the tables come back before you map them into the next module.
Feishu Base15

Update a Data Table Record

Action

In Make“Updates a field in a Bitable data table.”

According to the documentation, this module changes a field in a Bitable data table, even though its title talks about a record.

When to use it
a column has to be adjusted as part of an automated clean-up of the Base.
Watch out
since the title and the description disagree, try it on a copy of the Base and compare the effect with Update a Record before going live.
Feishu Base16

Update a Field

Action

In Make“Update a Bitable Metadata”

Going by its name, this module edits an existing field of a data table, while the directory text attached to it speaks of Bitable metadata instead.

When to use it
a column needs a new label after the team changes its vocabulary, and you want the scenario to apply it.
Watch out
test it with Run once on a copy; to rename the file itself, Update Bitable Metadata is the documented choice.
Feishu Base17

Update a Record

Action

In Make“Updates a record in a Bitable data table.”

An existing row gets rewritten, so a status, an amount or a date in Feishu Base follows what happens in your other tools.

When to use it
an invoice is paid in your billing app and the matching record should switch to paid.
Watch out
an action works on one item at a time, so find the right row first with Get a Record and map it into this module.
Feishu Base18

Update Bitable Metadata

Action

In Make“Updates the metadata of a Bitable, including the name of the Bitable and whether to enable advanced permissions.”

Renaming a Bitable and switching its advanced permissions on or off both happen here, among the settings the documentation mentions for the file.

When to use it
a project Base copied from a template should carry the client's name, and access should tighten once work starts.
Watch out
changing advanced permissions affects who sees what, so check the file in Feishu after the first test.
Feishu Base19

Upload a Material

Action

In Make“Uploads materials such as files, images, and videos to a specified Bitable.”

Files, images and videos from your scenario end up in the Bitable you choose, next to the data the team already works with.

When to use it
photos from a site visit or PDFs received by email belong in the project Base.
Watch out
the file must reach this module as a bundle from an earlier step, and on the Free plan Make caps files at 5 MB.
Need help

Need help automating Feishu Base with Make?

A person reads every message.

FAQ

Feishu Base and Make: frequent questions

01Is the Feishu Base Make integration free?
Yes, on the Make side. Feishu Base is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at most, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios, with usage counted in operations each month. Your Feishu Base subscription is a separate matter: check the Feishu Base pricing page for that side.
02What do you need to connect Feishu Base to Make?
A Feishu developer account, an active Feishu tenant and an account on Feishu Base. In the developer console you create an enterprise internal app, then copy its Client ID and Client secret from the Credentials and basic information section. If Feishu asks for a callback URI, you enter the Make address given in the documentation. Back in Make, you click Create a connection on any Feishu Base module, paste the credentials and follow the on-screen steps. The connection then works for all 19 modules.
03Can Feishu Base start a Make scenario in real time?
No. The Feishu Base app in Make has no trigger module, neither scheduled nor instant, so a change in a table cannot launch a scenario by itself. You start the scenario another way: with the trigger of another app, such as a form or a CRM, or with a schedule on the first module. A new scenario runs every 15 minutes by default, down to 1 minute on paid plans. The Feishu Base modules then act as steps inside that flow.
04What if a Feishu Base module is missing in Make?
Look at Create a API Call first. It sends an authorized request of your choice to Feishu Base through your existing connection, so an operation without a dedicated module can still be reached, provided you write the request from Feishu's API reference. Note that Make's documentation for this app warns it was generated with AI and may contain mistakes, so verify important details with Feishu. If the need goes beyond that, the team can help you design the scenario through the contact form below.
05Should you pick Make or n8n for Feishu Base?
It depends on the tool your team already uses. On Make, Feishu Base comes with 19 action modules for records, fields, tables and files, no trigger, and it is available from the Free plan. Before choosing n8n instead, check whether it offers a node for Feishu Base and which operations that node covers, then compare them with the list on this page. The n8n vs Make comparison linked above sets out the general criteria between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations