This connection lets people message a Rudder Agent from Feishu or Lark. The conversation and its Agent Runs remain visible in Rudder.

What you will connect

One Agent to one Feishu CN or Lark Global bot. A text message will reach the Agent, and its reply will return to the same provider conversation.

Before you start

You need:
  • a working Rudder Agent
  • permission to authorize or create an app in the Feishu or Lark workspace
  • an active Rudder organization membership for the person doing setup

Connect and test

  1. Open the Agent, then open Integrations.
  2. Choose Connect Feishu / Lark.
  3. Select Feishu CN or Lark Global to match the workspace you use.
  4. Rudder opens the provider authorization page with a suggested bot name. Review the requested message, reaction, command, and event permissions.
  5. Authorize the app and return to Rudder. Wait until the integration shows as active.
  6. Send the bot a plain-text test request. In a group chat, address the bot explicitly.
  7. Open Messenger and find the conversation with the Feishu source badge.
  8. Open its Agent Run and confirm that the source is Feishu.
Use /new when the next message should start a fresh Rudder conversation. Use /stop to stop an active reply.

Check the result

The sender’s message and Agent reply should be visible in Feishu or Lark. Rudder Messenger should show the same exchange and a linked Agent Run.

Common problems

  • Setup stayed pending after Rudder restarted: start a new setup; unfinished authorization does not survive a restart.
  • The wrong provider page opened: restart setup and choose the correct region.
  • The bot asks the sender to bind an identity: connect that Feishu identity to an active Rudder member, then resend.
  • A group message is ignored: address the bot directly.
  • A reply fails: open the provider conversation and Agent Run to find the error.
Provider-backed conversations are read-only in Rudder. Fork one when you want to continue locally without sending later replies back to Feishu.