How to Install and Use Feishu Bridge in OpenClaw

Open your terminal and run the clawhub install command to add the feishu-bridge skill to your OpenClaw instance. ClawHub downloads the skill package from the registry, verifies its integrity, and registers it with your local OpenClaw configuration. The installation typically takes under 30 seconds. When it completes, you will see a confirmation message listing the installed version and the configuration keys required: primarily FEISHU_APP_ID and FEISHU_APP_SECRET. The skill is installed but inactive until you supply these credentials in the following steps. If you see `clawhub: command not found`, verify that your OpenClaw installation is complete and that the OpenClaw binary directory is on your PATH. The ClawHub CLI is bundled with OpenClaw and should be available after a standard installation. You can also run `clawhub --version` to confirm it is available before proceeding.

1clawhub install feishu-bridge

To connect OpenClaw to Feishu, you need to create a Feishu application in the Feishu Open Platform. This application acts as the identity that OpenClaw uses to authenticate with Feishu's API and send/receive messages on your behalf. Navigate to open.feishu.cn and sign in with your Feishu account. Click 'Create App' (or 'Create Custom App' depending on your tenant's configuration). Give your app a clear name like 'OpenClaw Bridge' and a brief description. Choose 'In-House Apps' if building for your own team, or 'Marketplace App' if distributing more broadly — for most OpenClaw integrations, In-House is correct. Once the app is created, the app detail page shows your App ID (a string starting with 'cli_') and App Secret. Copy both values carefully — the App Secret is particularly sensitive and functions like a password for your app's Feishu access. Before the app can send messages, you need to add the correct permissions. In the app settings, navigate to 'Permissions & Scopes' and add at minimum: `im:message:send_as_bot` (to send messages) and `im:chat:readonly` (to read chat information). Click 'Save' and publish the app if prompted. Some tenants require admin approval for new apps — check with your Feishu admin if the app does not activate immediately.

With your Feishu App ID and App Secret ready, add them to OpenClaw's configuration using the `clawhub config set` command or by editing your `~/.openclaw/.env` file directly. Both methods write to the same configuration store. The environment variable names must match exactly: `FEISHU_APP_ID` and `FEISHU_APP_SECRET`. Case matters — incorrect variable names will cause authentication to fail silently, which can be confusing to debug. After setting both variables, run `clawhub reload` to apply the configuration without a full OpenClaw restart. You can then verify both keys are present by running `clawhub config get` for each variable name. Note that if your Feishu tenant is on the Lark international edition (lark.com) rather than the China edition (feishu.cn), you may need to set an additional variable specifying the API base URL. Check the feishu-bridge documentation with `clawhub info feishu-bridge` to see if a `FEISHU_API_BASE` option is available in your installed version.

1# Add to ~/.openclaw/.env
2FEISHU_APP_ID=cli_your_app_id_here
3FEISHU_APP_SECRET=your_app_secret_here
4
5# Or set via clawhub config command
6clawhub config set FEISHU_APP_ID cli_your_app_id_here
7clawhub config set FEISHU_APP_SECRET your_app_secret_here
8
9# Verify both are set
10clawhub config get FEISHU_APP_ID
11clawhub config get FEISHU_APP_SECRET
12
13# Apply changes
14clawhub reload

Open OpenClaw chat and test the feishu-bridge skill by asking OpenClaw to send a message to a Feishu chat. You will need the Feishu chat ID or user email of your target — the chat ID can be found in your Feishu app's developer console under 'Event Subscriptions' or by running a bot command that returns chat metadata. For user-to-user messages, you can reference the target user's Feishu email address directly. For group chats, you need the group chat ID. The simplest way to get a group chat ID is to open Feishu, navigate to the group, click the group name at the top, then 'Settings' → 'Copy Chat ID' (available in the desktop app or via Open Platform API). Once you have a valid target, your OpenClaw test message should arrive in Feishu within a few seconds. If the message does not appear, check the OpenClaw error output for authentication or permission errors — the most common issues are missing app permissions (the app needs `im:message:send_as_bot`) or the app not being added to the target group chat.

For recurring messaging workflows, configure default Feishu chat targets in the feishu-bridge skill configuration file so you do not need to specify the recipient in every OpenClaw prompt. You can also configure the default message format — Feishu supports plain text, Markdown, and rich card formats. The skill configuration file lives at `~/.openclaw/skills/feishu-bridge.yaml`. If it does not exist, create it — the skill will pick up settings from here on reload. The most useful settings are `default_chat_id` for a primary team chat and `message_format` for controlling how messages are rendered in Feishu. RapidDev can help teams set up feishu-bridge as part of a broader OpenClaw messaging and notification pipeline — particularly useful when routing alerts from multiple sources into organized Feishu channels with consistent formatting.

1# Configure feishu-bridge defaults in ~/.openclaw/skills/feishu-bridge.yaml
2feishu-bridge:
3  default_chat_id: "oc_your_default_chat_id"  # default target chat
4  message_format: "markdown"                   # plain | markdown | card
5  bot_name: "OpenClaw"                         # display name for sent messages
6  include_timestamp: true                      # add timestamp to messages
7  lark_mode: false                             # set to true for Lark (lark.com)