Feishu

Connect your AI Expert to Feishu (Lark), allowing team members to chat with your Expert directly in their everyday Feishu messages. The Feishu channel supports full conversation capabilities and additionally offers user-level OAuth authorization, enabling your Expert to access users’ personal documents and spreadsheets.

Integration Methods

Feishu offers two integration methods:

QR Code Quick Setup (Recommended)

The fastest way to get started — takes just a few minutes:

Go to “Channel Integration” in Expert Studio and select Feishu
Click “Scan to Connect”
Scan the QR code with a Feishu admin account
Confirm authorization — all configuration is completed automatically
Find the bot in Feishu and start testing

The QR code method automatically creates a Feishu app and configures all required permissions and callback URLs.

Manual Configuration

Choose manual configuration when you need more granular permission control:

Log in to the Feishu Open Platform and create an enterprise custom app
Enable the bot under the “Bot” capability
Configure the event subscription callback URL (available in the Profy integration panel)
Add required permissions (message sending/receiving, contacts read access, etc.)
Enter the App ID and App Secret in the Profy integration panel
Publish the app version and pass the review

Manual configuration is suited for scenarios where you need to limit specific permission scopes, or want to reuse an existing Feishu app.

Message Format

The Feishu channel uses a “multi-bubble” style: text replies arrive as individual bubbles, tool calls announce themselves first (e.g. ”🔍 Searching…”, capped at 3 notices), and the real reply follows as a new bubble.

Parameter	Value	Meaning
Single-message cap	8,000 characters	The longest Feishu accepts in one send
Chunk threshold	8,000 characters	Higher than the 800/2,000 default — Feishu keeps replies in one bubble far longer than DingTalk or WeCom
Card rendering threshold	200 characters	Longer text, or any Markdown/table, renders as an interactive card instead of plain text
Delay between bubbles	0.8 – 2.0 seconds	Mimics human typing rhythm
Status notification cap	3	Beyond that, tools run silently

Because the chunk threshold is raised to 8,000, a Feishu reply that would arrive as four bubbles in WeCom usually arrives as one. If you want progressive output, ask the Expert to report in stages.

Chat Scenarios

One-on-One Chat

Send a message directly to the bot to start a private conversation. Ideal for personal use cases.

Group Chat

@mention the bot in a group to send a message — the Expert will reply within the group. Suitable for team collaboration where other members can follow the conversation.

In group chat, the Expert only responds to messages that @mention it. It won’t reply to every message in the group.

User OAuth Authorization

A unique feature of the Feishu channel — after completing user-level OAuth authorization via the /auth command, your Expert can access your personal Feishu resources.

Authorization Flow

Send the Auth Command

Send /auth in your Feishu conversation with the Expert.

Click the Authorization Link

The Expert will reply with a message containing an authorization link. Click it.

Confirm Authorization

On the Feishu OAuth page, review the authorization scopes (document read access, spreadsheet access, etc.) and click approve.

Authorization Activated

Once authorized, the Expert can access Feishu documents and spreadsheets on your behalf.

Capabilities After Authorization

After completing OAuth, the Expert gains the following additional capabilities:

Capability	Description
Document Read	Read Feishu documents you have access to
Spreadsheet Operations	Query and modify your spreadsheet data
Knowledge Base Search	Search for information in knowledge spaces you have access to

OAuth tokens have an expiration period. When expired, the Expert will prompt you to run the /auth command again. If token refresh fails, the Expert automatically falls back to basic capabilities (without accessing your personal resources), and normal conversation continues unaffected.

Commands

Command	Effect
`/auth`	Start user-level OAuth so the Expert can reach your own documents
`/new`	Start a fresh conversation, dropping the current context
`/reset`	Same as `/new`
`/stop`	Interrupt the reply in progress

Commands are intercepted before the message reaches the Expert, so they never consume credits or a trial turn.

Key numbers

Item	Value
Single-message cap	8,000 characters
Card rendering threshold	200 characters (or any Markdown/table)
Status notification cap	3
Credits are charged to	The account that bound the channel, not the sender
Conversation isolation in groups	Per group × person — two people in the same group hold separate contexts
OAuth fallback on refresh failure	Basic capability (conversation keeps working, personal resources drop out)

Failures and fixes

Symptom	Cause	Fix
The bot never replies	App not published/approved, callback URL wrong, or you forgot to @mention it in a group	Check publication status and the callback URL; in groups always @mention
It replies in a group to messages meant for someone else	The Expert only answers @mentions — a mention you didn’t notice	Nothing to fix; unmentioned messages are ignored
`/auth` returns an error	The creator hasn’t configured Feishu OAuth on this Expert	Not every Expert supports it — ask the creator
It could read your docs yesterday, not today	The OAuth token expired and refresh failed, so it fell back to basic capability	Run `/auth` again
Replies come as one giant bubble	The Feishu chunk threshold is 8,000 characters	Ask it to report in stages, or output to a file
A long reply is truncated	Past the 8,000-character single-message cap	Have the Expert write to a file and send that
Everyone’s usage draws from one balance	IM channels bill the binding account	Use the web app for per-person billing
Slow replies	Model inference plus tool time — same as the web	Expected; search and file work take longer

Channels Overview

Learn about all supported IM platforms

DingTalk Integration

DingTalk channel setup guide

Get Started

Core Concepts

Guides

Platform & Account

Deep Dive

Integration Methods

Message Format

Chat Scenarios

One-on-One Chat

Group Chat

User OAuth Authorization

Authorization Flow

Capabilities After Authorization

Commands

Key numbers

Failures and fixes

Channels Overview

DingTalk Integration

​Integration Methods

​Message Format

​Chat Scenarios

​One-on-One Chat

​Group Chat

​User OAuth Authorization

​Authorization Flow

​Capabilities After Authorization

​Commands

​Key numbers

​Failures and fixes

​Related Pages

Channels Overview

DingTalk Integration

Integration Methods

Message Format

Chat Scenarios

One-on-One Chat

Group Chat

User OAuth Authorization

Authorization Flow

Capabilities After Authorization

Commands

Key numbers

Failures and fixes

Related Pages