​
Completed state

At the end of this guide, one Rudder Agent has an active Feishu or Lark integration. A plain text message reaches a provider-bound Messenger conversation, the Agent replies, and the source conversation and Agent Run show Feishu source evidence.

​
Prerequisites

Prepare a working Agent and permission to authorize or create an app in the target Feishu CN or Lark Global workspace. You also need to be a member of the Rudder organization if you expect setup to bind your provider identity automatically. The example connects the release writer to a team release chat. One integration belongs to one organization and one Agent.

​
Connect the release writer

  1. Open the release writer’s Agent detail, then open Integrations.
  2. Start the Feishu setup and choose Feishu CN or Lark Global for the workspace you actually use.
  3. Rudder opens the provider’s app authorization page with a safe suggested bot name. Review the requested bot, message, reaction, command, and receive-event permissions, then authorize the app.
  4. Return to Rudder. The setup page checks until credentials are stored as an organization secret and the Agent integration is active.
  5. Send the bot a plain text request in the release chat. In a group, address the bot explicitly.
  6. Open Messenger and find the conversation with the Feishu source badge. Open its Agent Run and confirm Source: Feishu.
  7. Use /new if you want the next message to begin a fresh bound Rudder conversation. Use /stop while a reply is active when you need to stop it.
Daily rollover is enabled by default with a 24-hour window. It happens only when the next inbound message arrives after the window. Quiet chats do not create empty sessions in the background.

​
Success signal

The sender’s message and the Agent reply remain visible in Feishu or Lark. The same exchange is auditable in a provider-bound Rudder conversation, and the originating Run carries Feishu source metadata. A rich Markdown card may fall back to plain text only when the provider explicitly rejects the card payload.

​
Recovery

If authorization remains pending after Rudder restarts, start a new setup session because unfinished setup is not preserved across a restart. If the wrong provider page opens, restart and select the correct region. If a sender receives binding instructions, bind that Feishu identity to an active Rudder member and resend. If a group message is ignored, address the bot. If the reply fails, inspect the provider-bound conversation, outbound status, and Agent Run. Continue the same context locally only by forking the Feishu conversation; the source conversation is read-only in Rudder, and the fork no longer sends messages back to Feishu.