# How to Install and Use Feishu Bridge in OpenClaw - Tool: OpenClaw - Difficulty: Beginner - Time required: 15 minutes - Last updated: March 2026 ## TL;DR To connect Feishu (Lark) to OpenClaw, run `clawhub install feishu-bridge` in your terminal, create a Feishu app in the Feishu Open Platform to get your App ID and App Secret, configure those credentials in OpenClaw, and start sending and receiving Feishu messages directly from OpenClaw chat. The feishu-bridge skill handles all message routing and authentication automatically. ## How to Bridge Feishu Messaging with OpenClaw Feishu (also known as Lark outside China) is the enterprise messaging and collaboration platform used by millions of teams across Asia and globally. If your team runs on Feishu for chat, project updates, and notifications, integrating OpenClaw with Feishu lets you automate messaging workflows, send AI-generated notifications, and receive Feishu messages as OpenClaw chat context — all without switching between applications. The feishu-bridge skill provides the foundational layer of this integration: basic bidirectional messaging. You can instruct OpenClaw to send formatted messages to specific Feishu chats, users, or groups, and you can configure the skill to relay incoming Feishu messages as prompts to OpenClaw. This covers the majority of messaging automation use cases: daily summaries sent to a Feishu group, alert notifications for monitored conditions, and simple command-response bots. For teams that need more advanced capabilities — event-driven triggers, complex multi-step workflows, or interactions between multiple bots — the companion feishu-evolver-wrapper skill adds Evolver middleware on top of this foundation. For straightforward send/receive messaging automation, feishu-bridge is the right starting point: simpler to configure, easier to debug, and sufficient for the vast majority of messaging use cases. ## Before you start - OpenClaw installed and running (see openclaw.ai for installation instructions) - ClawHub CLI available in your terminal (bundled with OpenClaw) - A Feishu account with access to the Feishu Open Platform at open.feishu.cn - Permission to create apps in your Feishu tenant (usually admin or developer role) - Terminal/command line access to run the clawhub install command ## Step-by-step guide ### 1. Install the Feishu Bridge Skill via ClawHub 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. ``` clawhub install feishu-bridge ``` **Expected result:** Terminal shows 'feishu-bridge@X.X.X installed successfully. Required config: FEISHU_APP_ID, FEISHU_APP_SECRET'. The skill appears in your `clawhub list` output. ### 2. Create a Feishu App and Get Your API Credentials 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. **Expected result:** Your Feishu app is created and published with messaging permissions. You have your App ID (starting with 'cli_') and App Secret copied and ready to configure in OpenClaw. ### 3. Configure Feishu Credentials in OpenClaw 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. ``` # Add to ~/.openclaw/.env FEISHU_APP_ID=cli_your_app_id_here FEISHU_APP_SECRET=your_app_secret_here # Or set via clawhub config command clawhub config set FEISHU_APP_ID cli_your_app_id_here clawhub config set FEISHU_APP_SECRET your_app_secret_here # Verify both are set clawhub config get FEISHU_APP_ID clawhub config get FEISHU_APP_SECRET # Apply changes clawhub reload ``` **Expected result:** Both `clawhub config get FEISHU_APP_ID` and `clawhub config get FEISHU_APP_SECRET` return masked values. Running `clawhub status` shows feishu-bridge as 'active'. ### 4. Test the Skill by Sending a Feishu Message from OpenClaw 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. **Expected result:** The test message appears in the target Feishu chat within a few seconds. OpenClaw chat shows a confirmation that the message was sent successfully. ### 5. Configure Default Chat Targets and Message Formatting 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. ``` # Configure feishu-bridge defaults in ~/.openclaw/skills/feishu-bridge.yaml feishu-bridge: default_chat_id: "oc_your_default_chat_id" # default target chat message_format: "markdown" # plain | markdown | card bot_name: "OpenClaw" # display name for sent messages include_timestamp: true # add timestamp to messages lark_mode: false # set to true for Lark (lark.com) ``` **Expected result:** Feishu messages sent from OpenClaw are routed to your configured default chat and rendered in your chosen format without needing to specify these details in every prompt. ## Best practices - Store FEISHU_APP_ID and FEISHU_APP_SECRET only in your OpenClaw `.env` file or via `clawhub config set` — never paste them into OpenClaw chat or store them in version-controlled files. - Grant your Feishu app only the minimum permissions it needs — start with `im:message:send_as_bot` and add more permissions only as required. - Add your Feishu bot app to group chats before trying to send messages to them — bots must be explicit members of any group they message. - Use Feishu's Markdown message format for notifications that need structure; use plain text for simple one-line alerts to avoid formatting overhead. - Test with a personal Feishu DM first before sending to team group chats — this lets you verify the integration works before broadcasting to colleagues. - If your organization uses Lark (lark.com) rather than Feishu (feishu.cn), set `FEISHU_API_BASE=https://open.larksuite.com` in your config — the two editions use different API base URLs. - For complex event-driven workflows or multi-bot scenarios, upgrade to feishu-evolver-wrapper rather than trying to build that complexity into feishu-bridge — the wrapper skill is purpose-built for advanced automation. - Regularly rotate your Feishu App Secret (every 90 days is a reasonable practice) and update the value in OpenClaw config immediately after rotation. ## Use cases ### Send Automated Status Updates to Feishu Groups Configure OpenClaw to send daily, weekly, or event-triggered status messages to a Feishu group chat. This is ideal for team standup summaries, monitoring alerts, or automated reports that your team already reads in Feishu. Prompt example: ``` Send a message to the Feishu group 'Engineering Daily' with the following update: 'Deployment completed successfully at 14:30. All health checks passing. No incidents in the last 24 hours.' ``` ### Feishu Bot Command Handler Use feishu-bridge to make OpenClaw respond to specific commands sent in a Feishu chat. Team members type a command in Feishu, the message is relayed to OpenClaw via the skill, and OpenClaw sends back an AI-generated response — creating a lightweight Feishu bot without any custom bot development. Prompt example: ``` Monitor the Feishu chat 'Support Requests' for any message starting with '/help' and respond with a formatted list of available commands and their descriptions. ``` ### Cross-Platform Notification Routing Use OpenClaw as the central routing layer to take alerts or events from one source and deliver formatted notifications to Feishu. For example, route error alerts from a monitoring system into a Feishu engineering channel, formatted with severity level, timestamp, and suggested action. Prompt example: ``` Send an urgent alert to the Feishu channel 'Incident Response' with the message: 'HIGH SEVERITY — API error rate exceeded 5% threshold. Current rate: 7.3%. Timestamp: [now]. Affected service: payment-gateway.' ``` ## Troubleshooting ### OpenClaw shows 'feishu-bridge: authentication failed' or '401 Unauthorized' when sending a message Cause: FEISHU_APP_ID or FEISHU_APP_SECRET is missing, incorrect, or the Feishu app credentials have been regenerated and the old values are stale in OpenClaw's config. Solution: Run `clawhub config get FEISHU_APP_ID` and `clawhub config get FEISHU_APP_SECRET` to confirm both are present. Verify the App ID starts with 'cli_' and that the App Secret matches exactly what the Feishu Open Platform shows. Re-run `clawhub config set` for either value and then `clawhub reload`. ``` # Re-set credentials clawhub config set FEISHU_APP_ID cli_XXXXXXXXXXXX clawhub config set FEISHU_APP_SECRET XXXXXXXXXXXXXXXXXXXX clawhub reload ``` ### `clawhub install feishu-bridge` returns '429 Too Many Requests' or the install hangs indefinitely Cause: ClawHub's registry has temporary rate limits during peak usage. This is a ClawHub registry issue, not a Feishu issue. Solution: Wait 2-5 minutes and retry the install command. If it hangs rather than failing, press Ctrl+C to cancel, wait a moment, then try again. Use `clawhub install feishu-bridge --force` if a previous partial installation is blocking the retry. ``` # Force reinstall clawhub install feishu-bridge --force ``` ### Messages are sent from OpenClaw but never appear in the Feishu group chat Cause: The Feishu app (bot) has not been added as a member of the target group chat. Feishu bots cannot send messages to groups they are not members of, even with valid credentials. Solution: In Feishu, open the target group chat. Click the group name at the top, then 'Add Members'. Search for your app name and add it as a bot member. After adding, retry the message send from OpenClaw — it should now appear in the group. ### Feishu API rate limit error — messages fail intermittently with '429' during high-frequency sending Cause: Feishu's Open Platform API enforces per-app rate limits. Sending many messages in quick succession from OpenClaw will hit these limits. Solution: Add pauses between high-frequency message sends in your OpenClaw workflows. For bulk notification scenarios, batch messages into fewer sends with more content per message. Review Feishu's current API rate limit documentation in the Open Platform developer console. ## Frequently asked questions ### How do I connect Feishu to OpenClaw? Run `clawhub install feishu-bridge`, create a Feishu app at open.feishu.cn to get your App ID and App Secret, then configure them with `clawhub config set FEISHU_APP_ID cli_xxx` and `clawhub config set FEISHU_APP_SECRET xxx`. Run `clawhub reload` and you can send Feishu messages from OpenClaw chat immediately. ### What is the difference between feishu-bridge and feishu-evolver-wrapper in OpenClaw? feishu-bridge provides basic bidirectional messaging — sending and receiving Feishu messages from OpenClaw. feishu-evolver-wrapper adds Evolver middleware on top, enabling complex event-driven automation, multi-step workflow triggers, and advanced bot interaction patterns. Start with feishu-bridge for simple messaging; upgrade to feishu-evolver-wrapper when you need workflow automation. ### How do I configure the OpenClaw Feishu API key and app credentials? Feishu Bridge uses two credentials: your App ID and App Secret from the Feishu Open Platform. Set them with `clawhub config set FEISHU_APP_ID cli_xxx` and `clawhub config set FEISHU_APP_SECRET xxx`. You can also add both to `~/.openclaw/.env` as `FEISHU_APP_ID=` and `FEISHU_APP_SECRET=`. Run `clawhub reload` after setting either method. ### Why can't my Feishu Bridge send messages to a group chat? Your Feishu app (bot) must be added as a member of the group chat before it can send messages to it. Open the group in Feishu, click the group name, then 'Add Members', and search for your app name to add it as a bot member. After adding, retry the message send. ### Does feishu-bridge work with Lark (the international version)? Yes — Lark and Feishu use the same underlying API but with a different base URL. Add `FEISHU_API_BASE=https://open.larksuite.com` to your OpenClaw config alongside your App ID and Secret. The rest of the setup process is identical to the Feishu (feishu.cn) edition. ### Does RapidDev offer help setting up Feishu Bridge with OpenClaw? Yes — RapidDev can assist with feishu-bridge configuration, especially for teams integrating Feishu messaging into larger OpenClaw notification or automation pipelines. The setup described on this page is self-serve for standard use cases; teams with specific routing or formatting requirements can contact RapidDev for guidance. ### OpenClaw feishu-bridge authentication keeps failing even with correct credentials — what else should I check? Verify that your Feishu app has been published (not just saved as draft) in the Feishu Open Platform. Unpublished apps cannot make API calls even with valid credentials. Also confirm the app has the `im:message:send_as_bot` permission granted and saved. Finally, check that your tenant admin has not restricted app API access at the organization level. --- Source: https://www.rapidevelopers.com/openclaw-integrations/feishu-bridge © RapidDev — https://www.rapidevelopers.com/openclaw-integrations/feishu-bridge