> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Lark and Feishu

> Answer Lark or Feishu direct messages and group @mentions

Lark (international) and Feishu (China) let the assistant answer a direct message and an @mention in a group. Pick the domain that matches the console where you created the app.

## When to use it

Use Lark when the company chats on larksuite.com, and Feishu when the company chats on feishu.cn. One Famulor connection uses one app and one domain.

## What the assistant hears

The assistant hears the event **im.message.receive\_v1**: direct messages, and group messages that mention the bot. Publish an app version and grant the scopes for those conversations before the first message.

## Where the keys come from

The linked provider guide shows the screens for these clicks. Follow the clicks below together with those pictures.

The App ID, App Secret and Verification Token already exist on the app, before you have the Famulor URL. International apps are created at [open.larksuite.com/app](https://open.larksuite.com/app). China apps are created at [open.feishu.cn/app](https://open.feishu.cn/app). The receive-message event is documented at [Receive message](https://open.larksuite.com/document/server-docs/im-v1/message/events/receive).

## Create it at the provider

1. Open the Lark or Feishu developer console and sign in.
2. Create a **custom app**. Copy the **App ID** (it starts with `cli_`) and the **App Secret**.
3. Open event subscriptions. Copy the **Verification Token**. Reset it there if you need a new one.
4. Add an **Encrypt Key** only if you turn encryption on. When it is set, events arrive encrypted and Famulor needs the same key.
5. Subscribe to **im.message.receive\_v1**.
6. Enable the bot capability. Add the scopes for direct messages and, if you want groups, for group messages that mention the bot.
7. Create and publish an app version so the bot can be installed.

## Connect it in Famulor

Your plan includes this channel. Open **Settings → Channels**, choose the card, name the connection, pick an assistant and save. The shared conversation settings — response delay (default 5 seconds) and inactivity timeout (default 30 minutes) — are described on the [messaging channels](https://docs.famulor.io/channels/messaging.md) page.

On the **Lark / Feishu** card choose **Lark (International — larksuite.com)** or **Feishu (China — feishu.cn)**. Paste **App ID**, **App Secret** and **Verification Token**. Paste **Encrypt Key** only when the app uses one.

After saving, open the connection menu and choose **Copy webhook URL**. Paste that exact address into the provider. A verified custom domain is already part of the address Famulor shows.

## Point the provider at Famulor

1. Copy the Famulor webhook URL.
2. In the app’s event subscription, set the request URL to that address and save. The console checks the verification token.
3. Install the published app for the users who should chat with it.
4. Send the bot a direct message, or @mention it in a group. The thread appears in History.

## History

Open [History](https://docs.famulor.io/monitoring/history.md) and filter by **Lark / Feishu**. The thread, the assistant reply and any analysis appear there. You can pause the assistant and answer manually.

## API, MCP and command line

The same connection can be created with the public API, the MCP tool `create_messaging_connector`, or the command line. Replace the placeholders with your own values.

```bash theme={null}
famulor create-messaging-connector --platform lark --name "Support" \
  --assistant-id ASSISTANT_UUID --domain lark --app-id cli_… --app-secret APP_SECRET --verification-token VERIFY_TOKEN
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.