Multica Docs

Feishu Bot

Connect an agent to Feishu and hand it work directly from a DM or a group chat.

Connect a Multica agent as a Feishu Bot and team members can DM it in Feishu, @-mention it in a group, or use /issue to create issues. Conversations and run records are saved in the Multica workspace.

Each Bot maps to exactly one agent. To use several agents in Feishu, connect a Bot for each of them.

Connect a Bot

The agent's owner and workspace owners and admins can start a connection:

Open Agents and select the agent to connect to Feishu.

Go to Integrations and click Bind to Feishu.

Scan the QR code with Feishu and confirm the authorization. The QR code works only once; if it expires, generate a new one.

Return to Multica. Once the page shows Connected to Feishu, the Bot is ready.

An agent that is already connected no longer shows the scan entry point; to rename the Bot or adjust its permissions, click Manage in Feishu.

New connections are currently open only for mainland-China Feishu. Existing international Lark connections keep working and can still be managed.

First use

The first time a member messages the Bot, they receive an account binding link:

Open the link and sign in to Multica.

Confirm the workspace account to link.

Return to Feishu and send the message again.

This binding is how Multica knows which workspace member a message comes from. Non-members cannot use the Bot.

Hand work to the agent in Feishu

Direct messages

Message the Bot directly. Consecutive messages stay in the same Multica conversation, and the agent's replies go back to that conversation.

Group chats

Add the Bot to the group first, then @Bot and describe what you need. The Bot only responds to messages that explicitly @-mention it, and each run includes the group's most recent messages as context.

Create an issue

Send:

/issue Fix the redirect after login
Safari stays on the login page after a successful sign-in.

The first line becomes the title and the rest becomes the description. Sending /issue alone creates nothing; the Bot replies with the required format instead.

Images and files from the agent

When file delivery is enabled, text and supported images attached to an agent’s reply appear together in one Feishu message. Images update that message as they finish uploading; files arrive separately in the same conversation. An image-only reply can use an image message. Supported images are limited to 10 MB; unsupported, larger, or explicitly rejected images are sent as files, up to 30 MB. This requires object storage and the application’s resource upload permission. If delivery fails or cannot be confirmed, the attachments remain available on the reply in Multica. Check the conversation before requesting a resend.

Manage connections

Open Settings → Messaging → Lark to view the Bots connected in the workspace. Workspace owners and admins can disconnect them here; an agent's owner can also manage their own Bot from that agent's Integrations page.

After disconnecting, the Bot stops receiving new messages. Existing conversations and audit records are not deleted.

Self-hosting setup

Multica Cloud needs no extra configuration. A self-hosted deployment must first set a key used to encrypt Bot credentials:

MULTICA_LARK_SECRET_KEY=<base64-encoded 32-byte key>

Generate one like this:

openssl rand -base64 32

Restart the API server, then connect the Bot from the agent's Integrations page. Keep this key long-term: if it is rotated or lost, existing credentials can no longer be decrypted and the Bot must be reconnected.

MULTICA_LARK_HTTP_BASE_URL and MULTICA_LARK_CALLBACK_BASE_URL exist only for special deployments such as proxies and testing; leave them unset in normal operation.

Troubleshooting

  • No bind button: confirm the current account is the agent's owner or a workspace owner or admin, and check that the self-hosting key is configured.
  • QR code expired: close the dialog and start the connection again.
  • The Bot asks for account binding: open the binding link and sign in with the Multica account for that workspace.
  • The Bot doesn't run: check whether the agent is archived and whether the runtime it uses is online.
  • The Bot never replies at all: the app must push events over a long connection; Multica has no webhook endpoint. In the Feishu/Lark developer console, open Events & Callbacks → Event Configuration and confirm that the subscription method is the long connection rather than a request URL, that im.message.receive_v1 is subscribed, and that the app version carrying that configuration is published (and approved, where the tenant reviews releases). An app set to a request URL still binds, still shows Connected, and silently receives nothing.

Next steps

  • Chat integrations — platform comparison, session isolation, and account binding mechanics.
  • Chat — the conversation and execution model behind the Bot.
  • Issues — the unit of work /issue creates.

Chat integrations

Connect Multica agents to Feishu, Lark, Slack, DingTalk, WeCom, or Telegram and use them from the chat tools your team already uses.

Slack Bot

Create a Slack Bot for an agent and use it in DMs, channels, and the /issue, /new, and /clear commands.

On this page

Connect a BotFirst useHand work to the agent in FeishuDirect messagesGroup chatsCreate an issueImages and files from the agentManage connectionsSelf-hosting setupTroubleshootingNext steps