Feishu Bot
Once you connect the Feishu Bot, Aureink enters your Feishu/Lark as a bot and replies to messages automatically in direct chats and groups. Feishu is an open-platform channel: you need to create an app on the open platform and obtain credentials, and Aureink offers one-tap app creation by QR code to simplify this step.
1 · Overview
Connection method: scan to create an app (credentials needed). Compared with QR-code channels, Feishu adds the “create an app, get credentials” step, but it lets you bind a default Agent and set a group permission policy, making it a better fit for team collaboration.
2 · Before you connect
- A Feishu / Lark account with app-creation rights — you need to be able to create an app on the open platform (within a company this usually requires admin rights).
- Determine the region — be clear whether your organization uses Feishu or Lark, as the two have different entry points.
- Keep the client running — the Aureink desktop client must be online for the bot to keep sending and receiving messages.
3 · Choose the region and scan to create an app
- Open Settings → Channels and click Connect on the Feishu Bot card.
- Choose the region — select Feishu or Lark based on your organization.
- One-tap app creation by QR code — scan the page’s QR code with Feishu/Lark and follow the guide to create the corresponding app on the open platform in one tap.
- Obtain credentials and keep them safe — after the app is created, Aureink obtains the app’s connection credentials; these credentials are equivalent to the bot’s identity, so keep them safe and never leak them. To refresh them, go back to the app credentials page on the open platform.
〔Figure: the Feishu connection page showing the region selector and the QR code for creating an app〕
4 · Set a default Agent and connect
- Set a default Agent — bind a default Agent to this channel, and the bot will greet messages with that Agent’s persona and capability scope.
- Establish the connection — once the credentials are in place, return to Aureink to complete the connection.
〔Figure: the Feishu channel’s default Agent selector and connect button〕
5 · Verify the connection
To tell whether it’s connected, check two things:
- Status shows “Connected” — the channel card’s status changes to “Connected.”
- @ the bot in a group and test the reply — pull the bot into a test group, @ it with a line, and see whether it replies as expected.
Only when both hold is it truly connected.
6 · Group usage permission policy
You can control who the bot responds to in a group. Different groups are context-isolated from each other and never bleed together:
| Policy | Description |
|---|---|
| All group members | Anyone in the group can trigger the bot |
| Selected members only | Only members on the list can use it |
| Exclude a few members | Members on the list can’t use it; everyone else can |
| Admins only | Only group admins can use it |
| Do not respond in groups | No response in that group |
〔Figure: the group permission policy panel, highlighting the five policies〕
7 · Important notes
Important notes
- Credential security — app credentials are equivalent to the bot’s identity; keep them safe and never leak them, and refresh them promptly on the open platform if leaked.
- Permission boundaries — the bot speaks on your behalf in groups, so it’s best to validate with a small-scope policy (such as Selected members only) before opening it up.
- Messages can’t be unsent — a message that has been sent cannot be recalled.
- Quota usage — group auto-replies are fairly frequent and continuously consume usage quota.
Last updated · July 2026 ｜ Next: WeCom →