Connect Feishu
Use a custom enterprise application with Bot capability. A group’s custom webhook Bot cannot replace the two-way connection required here.
Configure the Feishu app
Section titled “Configure the Feishu app”Create the application on the Feishu Open Platform, enable Bot capability, and obtain its App ID and App Secret.
Choose long-connection event delivery and subscribe to im.message.receive_v1. Astral establishes the connection; no public webhook is required.
Grant and publish permissions for the features you need:
| Purpose | Permission |
|---|---|
| Receive private messages | im:message.p2p_msg:readonly |
| Receive group mentions | im:message.group_at_msg:readonly |
| Receive ordinary group messages | im:message.group_msg, subject to approval |
| Send as the Bot | im:message:send_as_bot |
| Upload and read attachments | im:resource |
| Read chat information | im:chat:readonly |
Publish the app, include the intended users in its availability scope, and add the Bot to the group. Permission changes must also complete the platform’s publication process.
Connect in Astral
Section titled “Connect in Astral”- Open Settings → Bots → your Bot → Connect a platform → Feishu.
- Enter App ID and App Secret and connect. Normally retain the default server address.
- Send a message in the target private chat or group so Astral can discover it.
- Authorize it under Connected chats and bind a new or existing unbound session.
Feishu Chat IDs use oc_…. Threads currently belong to the parent chat rather than separate topic authorization.
Replies and files
Section titled “Replies and files”Private messages, mentions, and replies to the Bot can trigger tasks directly. Receiving ordinary group context requires the corresponding permission.
Text, images, files, and supported message resources are available. File and explanatory text sends are separate; successful text does not prove successful file delivery.
If no messages arrive
Section titled “If no messages arrive”Check publication, user availability, group membership, long-connection subscription, and effective permissions, then Astral’s chat authorization.
Missing chat-information permission may leave only a Chat ID visible. A successful connection does not authorize every message, file, or management operation.