Feishu Bot

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 still saved to 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:

1. Open Agents and select the agent to connect to Feishu.
2. Go to Integrations and click Bind to Feishu.
3. Scan the QR code with Feishu and confirm the authorization.
4. Return to Multica. Once the page shows Connected to Feishu, the Bot is ready.

The QR code is a one-time credential; if it expires, generate a new one. 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.

First use

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

1. Open the link and sign in to Multica.
2. Confirm the workspace account to link.
3. Return to Feishu and send the message again.

Only after binding can Multica confirm 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; when it runs, it draws on the recent context it can read in the current session.

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.

Manage connections

Open Settings → Integrations 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.

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.