Resources · Make integration

Feishu Document Make integrationAutomate Feishu Document with Make.

Can Make write and read your Feishu documents for you? Yes: the Feishu Document Make integration offers 13 modules, 12 actions and 1 search, with no trigger. This page is for teams who live in Feishu and want to connect the account, then build a first scenario step by step.

Try the Feishu Document integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Feishu Document Make integration do for you?

The integration lets a Make scenario (the automation you build, a chain of modules) create cloud documents in Feishu, read them as plain text or Markdown, and edit them piece by piece. Each module is one brick of that chain, and your Feishu account is linked once through a connection that every module reuses.

A document drafted for every new request. When another app sends a new record, Create a Cloud Document opens a fresh doc and Create a Text Block writes the details inside. A sales team can get one briefing doc per lead without copying anything by hand.

A Markdown copy of the docs you care about. Search a Cloud Documents finds the documents, then Get a Document Content in MD Format returns their content ready for another tool, such as a knowledge base or a table in the Airtable Make integration.

A status line that stays current. Get a Document Block reads one piece of a document and Update a Block Content rewrites it, so a project page can show the latest figure from your other tools.

What Make does not do here: the app has no trigger, so nothing starts on its own when someone edits a doc in Feishu. The scenario starts from another app or from its schedule. The Make documentation for this app also warns that it was generated with AI from the Feishu docs and may contain mistakes, so check important details with Feishu.

Feishu Document may also be available as an n8n node; the n8n vs Make comparison lays out the criteria. To learn the editor properly, the Make training starts from zero.

Connect

How do you connect Feishu Document to Make?

  1. 01

    Prepare a Feishu app

    Make needs a Feishu developer account and an application that holds API credentials. In the Feishu developer console, click Create App, give it a name and a description, then paste the callback URI Make expects before you copy the Client ID and the Client secret.

  2. 02

    Add a Feishu Document module

    In your scenario, add any Feishu Document module and click Create a connection. The Connection name field is optional, but a clear name helps when you later run several Feishu apps side by side.

  3. 03

    Enter the credentials

    Paste the Client ID and Client secret you copied, or follow the instructions Make shows on screen, then confirm. From then on, every Feishu Document module in your scenarios reuses this connection.

First scenario

Build your first scenario with Feishu Document

GoalWhen a new request lands in another app, Make creates a Feishu cloud document and writes its details in a text block.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that receives your requests, such as a form tool or a CRM, and its trigger.

  2. 02

    Add Create a Cloud Document

    Click the + on the right of the trigger, search for Feishu Document and choose Create a Cloud Document. Link your account with Create a connection, then fill the fields Make shows with data from the trigger, such as the request name.

  3. 03

    Write the text with Create a Text Block

    Add Create a Text Block after the document module. Map the document from the previous module, then drag the fields of the request into the text so each doc carries the right details.

  4. 04

    Test with Run once

    Click Run once and send a test request. Each module shows the bundle it received, one bundle being one item passed along, so you can open Feishu and check that the new document holds the text.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the Feishu Document modules do

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

Feishu Document1

Create a Block

ActionIn the docs only

Adds a new block to an existing Feishu document, so your scenario can extend a page instead of starting a new one. Make works on these documents block by block, as the module names show.

When to use it
a running log page where each new event from another app should land as one more piece of content.
Watch out
when the block is plain text, Create a Text Block is the more direct choice.
Feishu Document2

Create a Cloud Document

ActionIn the docs only

Gives you a brand new document in Feishu, created by the scenario the moment the previous module hands it data. It is the usual first Feishu step of a flow that writes content.

When to use it
one doc per new client, per meeting request or per project, created as soon as the record appears in your other tool.
Watch out
the new document starts empty; chain a block module to fill it.
Feishu Document3

Create a Text Block

ActionIn the docs only

Writes a piece of text into a Feishu document, which is how most scenarios put words on the page after creating it. You map the text from any earlier module.

When to use it
right after Create a Cloud Document, to drop in the summary of a form answer or a ticket.
Watch out
it needs to know which document to write into, so map the document from the module that created or found it.
Feishu Document4

Delete a Block

ActionIn the docs only

Removes one block from a document, which keeps generated pages tidy when a line no longer applies. Pair it with a module that tells you which block to target.

When to use it
clearing an outdated notice or a placeholder once the real content has been written.
Watch out
a deletion made by a scenario does not come back by itself, so test it with Run once on a copy before switching the scenario on.
Feishu Document5

Get a Child Block

ActionIn the docs only

Reads a block that sits inside another block, which lets your scenario reach content nested one level down. You get that piece of the document as data for the next module.

When to use it
a section of a doc where the part you need lives under a parent block, such as a note under a heading.
Watch out
you first need the parent block, often from Get a Document Block.
Feishu Document6

Get a Document Basic Information

ActionIn the docs only

Returns the general details of a Feishu document rather than its content, a light way to check what a document is before working on it. Nothing in the document changes.

When to use it
a routing step that decides where a document should go before your scenario reads or edits it.
Watch out
for the words themselves, pick one of the content modules instead.
Feishu Document7

Get a Document Block

ActionIn the docs only

Fetches one block of a document, giving your scenario a precise piece of the page to read or to pass on. It is the natural partner of the update and delete modules.

When to use it
reading the status line of a project page before deciding whether it needs rewriting.
Watch out
it targets a single block; to read the whole document at once, the plain text or Markdown modules are simpler.
Feishu Document8

Get a Document Content in MD Format

ActionIn the docs only

Hands you the whole content of a document in Markdown, so headings and emphasis travel with the text into other tools. Many knowledge bases and publishing tools accept this format.

When to use it
copying an approved Feishu page into a wiki, a website draft or an AI step that reads formatted text.
Watch out
when formatting only gets in the way, the plain text module is the lighter option.
Feishu Document9

Get a Document Plain Text Content

ActionIn the docs only

Pulls the text of a document without any formatting, which is the cleanest input for a search, a summary or an email body. Your next module gets the words of the page, nothing else.

When to use it
sending the content of meeting notes to a text analysis step or into a message.
Watch out
titles and emphasis are gone; switch to the Markdown module when the structure matters.
Feishu Document10

Get a Single Block Content

ActionIn the docs only

Reads the content held by one specific block, useful when your scenario only cares about a single value on the page. It avoids pulling a full document for one line.

When to use it
a template where one block holds a figure, a date or a decision that another app needs to know.
Watch out
you must already know which block to read, so keep its reference from an earlier module.
Feishu Document11

Make an API Call

ActionIn the docs only

Calls any endpoint of the Feishu API from your scenario, with the connection you already set up. It covers what the 12 other modules do not.

When to use it
a Feishu document feature you need that no module on this page handles.
Watch out
you write the request yourself from the Feishu API documentation, so this module asks for more care than the others and a test with Run once.
Feishu Document12

Search a Cloud Documents

SearchIn the docs only

Finds Feishu cloud documents for your scenario, the starting point when you do not already know which document to read or edit. As a search, it can return zero, one or several bundles.

When to use it
gathering the documents of a project before exporting them in Markdown.
Watch out
each result runs the next modules once, and each run counts as operations on your plan.
Feishu Document13

Update a Block Content

ActionIn the docs only

Rewrites what a block says, so a document can show fresh information without anyone opening it. The rest of the page stays as it was.

When to use it
a dashboard page in Feishu whose status line follows a deal stage or a ticket status from another app.
Watch out
the old content is replaced, so read it first with Get a Single Block Content if you need to keep a trace.
Need help

Need help automating Feishu Document with Make?

A person reads every message.

FAQ

Feishu Document and Make: common questions

01Is the Feishu Document Make integration free?
Yes, on the Make side. Feishu Document is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes 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 and remove the limit on active scenarios. Every module run counts as an operation on your plan. Your Feishu subscription is a separate matter, covered by Feishu pricing.
02What do you need to connect Feishu Document to Make?
You need an active Feishu developer account and an application with API credentials. In the Feishu developer console, create the app, enter its name and description, add the callback URI https://www.integromat.com/oauth/cb/feishudocument, then copy the Client ID and the Client secret. In Make, add a Feishu Document module, click Create a connection, and paste those two values. The connection is then shared by every Feishu Document module you add later, so you only go through these steps once.
03Does the Feishu Document Make integration react in real time?
No, because the app has no trigger module. A scenario that uses Feishu Document starts in another way: from the trigger of another app, such as a form tool or a CRM, or from the schedule of the first module. A new scenario checks every 15 minutes by default, 15 minutes being the minimum on the Free plan and 1 minute on paid plans. Nothing starts on its own when someone edits a document inside Feishu.
04What if the Feishu Document module you need is missing?
Use Make an API Call. It sends a request to any endpoint of the Feishu API with the connection you already have, so you can reach features the 12 other modules do not cover. Write the request from the Feishu API documentation and test it with Run once before switching the scenario on. Also note that the Make documentation for this app says it was written with AI from the Feishu docs and may contain mistakes, so check important details with Feishu.
05Should you use Make or n8n for Feishu Document?
It depends on your criteria, not on a winner. On Make, Feishu Document offers 13 modules, including Make an API Call, and works from the Free plan, alongside more than 3,000 standard apps. The same app often has an n8n node too, so check that side before you decide. Compare the tools on what your team already uses and how it wants to build and run its automations; the n8n vs Make comparison linked above goes through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations