Skip to main content
This connects an expert to Feishu (Lark) so your team can use it in the chat window they already live in, and so it can read and write your Feishu documents and Bitables. The thing that usually blocks people isn’t configuration — it’s that there are two separate authorizations. Onboarding lets the bot send and receive messages; /auth is what lets it touch your documents. Many people finish onboarding, assume they’re done, hit a permission error when reading a doc, and then spend an hour re-checking the onboarding config — which was fine all along. This guide draws that line clearly.

​
What you’ll get

  • A working bot in Feishu, usable in both direct messages and groups
  • After authorization, the ability to read and write Feishu docs, Bitables, and wikis that you have access to
  • The ability to create a scheduled task from a Feishu message, with results delivered back to the same conversation

​
The key distinction: two authorizations

User authorization is per person. Everything working for you says nothing about your colleagues — each of them must run /auth themselves. This is the single most common “but it works for me” confusion.

​
Part 1: Onboarding

1

Open channel setup

In the expert’s Studio, go to channel setup and pick Feishu.
2

Scan the code

Scan with a Feishu admin account. Regular member accounts can’t complete this — that’s the first sticking point.
3

Confirm authorization

Confirming creates the Feishu app and configures permissions and callbacks automatically.
4

Find the bot in Feishu

Search for the bot by name and send “hello” to test.

​
Option B: Manual configuration

Use this when you need tight permission scoping, or want to reuse an existing Feishu app:
1

Create a custom app

On the Feishu Open Platform.
2

Enable the bot capability

Under the “Bot” capability.
3

Configure event subscription

Copy the callback URL from Profy’s channel panel. A wrong callback URL is the number one cause of “the bot doesn’t reply” — hit verify on the Feishu side after saving.
4

Add permissions

Message send/receive at minimum; add contacts, docs, and Bitable scopes if you need them.
5

Fill in credentials

Put the App ID and App Secret into Profy’s channel panel.
6

Publish and wait for review

Custom apps must publish a version and pass review. The bot won’t respond until it does — that’s the second sticking point, and it looks exactly like a misconfiguration.

​
Verify onboarding

Send “hello” to the bot in Feishu. A reply means onboarding worked. If nothing comes back, check in this order: is the app published and approved → is the callback URL correct → in a group, did you @ the bot.

​
Part 2: User authorization

​
Run /auth

1

Send the command

Send /auth in your Feishu conversation with the bot.
2

Open the link

The bot replies with an authorization link.
3

Confirm the scope

Approve the requested scopes on the Feishu OAuth page.
4

Back to the conversation

Authorization is live; you can now have it read documents.

​
Verify authorization

Find a Feishu doc you have access to and send the link:
Getting the content back means authorization worked. A permission error means it never took effect or has expired — run /auth again.
After authorization the expert’s reach equals your own — it cannot see documents you can’t see. Authorizing it does not grant access beyond your own permissions.

​
Part 3: What it can do

Three capability groups become available. Note these tools exist only in Feishu conversations — they don’t appear when you talk to the same expert on the web.

​
Documents

Overwrite is clear-then-write, not a smart merge. Telling it to “update section three” of a document someone maintains can leave you with a document containing only section three. To change part of a document, explicitly say “append at the end,” or have it read the doc, agree the new full text with you, and only then write.

​
Bitables

Querying and modifying records is supported, along with structural operations. The typical use is writing conversation output straight into a table:
Include the “read the header first” instruction. When field names don’t match, the default behavior may be to skip that column, leaving you with a batch of records missing fields.

​
Creating scheduled tasks from Feishu

An easily missed capability: you can create Profy scheduled tasks (not Feishu calendar events) right from chat:
The task records Feishu as its source, so results are pushed back into that Feishu conversation. The task itself is visible and manageable on Profy’s web console. Recurrence is still limited to no-repeat / daily / weekly / monthly — see Daily briefing.

​
Behavior in groups

  • The bot only responds when @-mentioned; it doesn’t chime in on every message
  • Each member’s /auth is independent — A being authorized says nothing about B
  • Replies arrive as multiple bubbles, with status notices while tools run
  • Long replies are split automatically

​
Boundaries and failure modes

Feishu channel

Full channel configuration reference

Feishu tools

Every action and parameter of the three tools

Knowledge connectors

Another path to Feishu content

Channels overview

Other IM platforms