Lark and Feishu AI bots: group topics, permissions and Credits

This connection uses your own Lark or Feishu application bot with message events and the permissions required for its features. A custom group Webhook bot is not sufficient. You can create an app by QR code or connect an existing one. Do not connect the same app to another bot service at the same time.

The administrator connects their Sparkles account; approved members do not need a separate Credits balance. For a personal assistant, see the Telegram guide.

1. Sign in to Sparkles, choose Connect chat apps in the sidebar and select Lark / Feishu, or open account settings.
2. Select the platform and follow the QR-code flow. The administrator must review and confirm permissions. For an existing app, enter its App ID and App Secret in the dedicated fields, enable its bot, configure message events through a long connection and publish the changes in the developer console.
3. Complete the administrator’s private-chat pairing as instructed: message the QR-created bot, or send the one-time binding command shown for an existing application. Private chat is administrator-only by default.
4. Add the bot to a group, mention it once and refresh the group list in Sparkles. New groups are disabled by default.
5. Enable the group and choose its trigger and permitted members. Starting with mentions and a few named members makes the first workflow easier to follow.

Streaming cards and interactive buttons require the corresponding permissions and callback configuration. Selecting “all messages” in Sparkles does not itself grant platform permission to read them.

The trigger answers when the bot responds: only when mentioned, or to all eligible messages. The member setting answers who may use it: the administrator, selected members or everyone in the group. The group’s enable switch is a separate control.

A selected member still needs to mention the bot in mention-only mode. Before enabling all-message mode, explain the scope and who pays for requests.

Approved members interacting in the same topic use that topic’s context. Different topics, groups and private conversations remain separate. Reply to the original topic to revise its poster; start another topic for unrelated work. Trigger and membership rules still apply.

This is a sample request, not a recorded team exchange. In mention-only mode, first select the bot from the Lark / Feishu @ menu, then send the text below. Pasting the words “@bot” does not create an actual mention.

This topic is for our weekend coffee-event poster.
First organize the audience, headline and three required details. Do not generate an image yet.
List any missing information together, then wait for us to confirm before discussing visuals.

Other approved members can reply in that same topic with dates or headline changes. Keep unrelated projects out of it: shared context works best when the topic has a clear purpose.

In a group, /new creates a separate topic, even when issued inside an older one. /sessions lists this group’s previous topics and opens the selected topic; it does not replace the current topic’s context. Navigation can require additional message-reading permissions.

In private chat, /new creates a new session in the same chat, while /sessions returns to that sender’s own previous sessions. Submitted tasks remain with their original session; pending attachments do not move when you switch.

Administrators use /setting or /settings to choose a reply model, supported reasoning level and language for future tasks. A member’s /stop requests cancellation of their own most recent task in the current conversation scope.

Replies arrive as Markdown cards by processing stage. With CardKit permission, text can stream with a typing effect; otherwise ordinary cards are updated. Question cards can be answered by their original requester.

Text, images, regular files and video attachments are supported, with up to 6 attachments per request. Pending files are held separately for each member. Tool and platform size and format limits still apply.

Image results include a preview and a separate original-file attachment. Download the latter for original quality. Oversized results are not silently reduced in quality; the administrator can inspect them in the web app. Processing reactions require the appropriate permission, and completion is marked only after the task and result delivery succeed.

Requests use the binding administrator’s Credits and model access. Member access does not make generation free or grant full access to the administrator’s web workspace. /credits reveals the balance only in the administrator’s private chat.

The administrator can inspect their channel conversations on the web, including channel private chats. A member’s session directory does not expose other members’ private chats or other groups, but this does not hide those conversations from the administrator. Explain this to your team.

Private web links still require an authorized account. Posting a canvas link does not share that project with the whole group. See the chat-to-canvas workflow.

Try one group, one focused topic and a few approved members: clarify a brief, confirm a direction, generate and inspect the downloaded result. If the bot is silent, check group enablement, membership, mentions and published app permissions. If delivery fails, check the existing web result before requesting another generation.