clawdbot-feishu plugin
An OpenClaw plugin for Feishu and Lark: a chat bot that also works with docs, wiki, drive, tasks and tables
- 4,221 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The bot holds the app's App Secret and permissions over company documents, drive, wiki and messages; writing, deletion and urgent notifications are separate permissions.
- With `dmPolicy: "open"` any user can message the bot directly, so start with `pairing`.
Install
- Works in
Manual install
openclaw plugins install @m1heng-clawd/feishuThe README command. Update with `openclaw plugins update feishu`. Then create an app on the Feishu Open Platform and set `appId` and `appSecret`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The bot holds the app's App Secret and permissions over company documents, drive, wiki and messages; writing, deletion and urgent notifications are separate permissions.
- With `dmPolicy: "open"` any user can message the bot directly, so start with `pairing`.
This is third-party code. Review the repository files before installing.
What it does
The plugin connects OpenClaw to Feishu and Lark as a messaging channel. The bot receives direct and group messages over WebSocket or webhook, reads images and files that are sent to it, replies with quoting and shows that it is typing through an emoji reaction. Groups have a mode where the bot answers only when mentioned. Beyond chat the plugin gives the agent tools: `feishu_doc` for documents, `feishu_wiki` for wiki, `feishu_drive` for drive, `feishu_bitable` for multidimensional tables, a `feishu_task_*` group for tasks, lists, comments and attachments, plus `feishu_chat`, `feishu_message`, `feishu_reaction` and `feishu_urgent`. The `skills/` folder holds nine skills that tell the agent which tool to call in which case.
Who it is for. Teams that work in Feishu or Lark and connect an OpenClaw agent to the messenger for chat, documents and tasks.
Good fit when
- Employees message the bot directly or mention it in a Feishu group chat.
- An agent creates and edits Feishu documents from markdown.
- Multidimensional table records are read and updated by a `/base/` or `/wiki/` link.
- An agent creates tasks, subtasks and task lists and assigns the requester as the assignee.
- An urgent notification reaches the assignee in the app, by SMS or by a call through `feishu_urgent`.
Not a fit when
- You work in Claude Code, Cursor or another agent without OpenClaw: the plugin is built only for OpenClaw.
- Company policy forbids bot access to documents, drive and wiki.
- The answer has to stream as it is typed: because of API limits the plugin sends it whole.
Example request
Create a Feishu document with the meeting summary, add tasks for colleagues from its points and send them the link in direct messages.Limitations
The plugin works only with OpenClaw and needs your own app on the Feishu Open Platform: an App ID, an App Secret, permissions and an event subscription, above all `im.message.receive_v1`. The bot sees only what has been opened to it: drive files, wiki spaces and tables must be shared explicitly, and the bot itself has to stay the owner of a task list. Replies arrive whole, without streaming, because of Feishu API limits. The last commit in the repository was made in March 2026.
How to disable. Turn the channel off with `openclaw config set channels.feishu.enabled false` and remove the plugin with OpenClaw. Revoke the app in the Feishu console separately.
FAQ
How do I install the Feishu plugin in OpenClaw?
Run `openclaw plugins install @m1heng-clawd/feishu`. If installation fails on Windows with `spawn npm ENOENT`, download the archive with `npm pack @m1heng-clawd/feishu` and install it from the `.tgz` file.
Why does the bot send messages but not receive them?
Most likely the event subscriptions are not set up. In the Feishu console pick long connection for the `websocket` mode or Request URL for `webhook` and add the `im.message.receive_v1` event.
Who can message the bot directly?
`dmPolicy` decides that. With `pairing` the bot sends a code and the owner approves it with `openclaw pairing approve feishu <code>`. `allowlist` admits only users from `allowFrom`, and `open` together with `allowFrom: ["*"]` admits everyone.
Why does the bot not see files on the drive or wiki?
The bot has no root space of its own and sees only what was shared with it. Share a drive folder with it, add it as a member of each wiki space and give it access to the tables.
How do I start a new conversation with the bot?
Send the `/new` command in the chat: it clears the conversation history.
Discussion
No questions or reviews yet.
Related
PluginsThe official Lark and Feishu plugin for OpenClaw: chat, docs, bases, calendar and tasks of your workspace from a conversation with the agent
A Feishu CLI with two-way Markdown conversion and nine skills so Claude Code can run chats, mail and calendars.
An MCP server for Feishu and Lark: the agent reads and edits documents block by block, manages tasks and finds colleagues, with the same tools as a CLI
Lark CLI
lark-cli
The official Lark and Feishu CLI with agent skills: messages, docs, sheets, calendar, mail and tasks from the terminal, over 200 commands
Claude-to-IM
claude-to-im
A bridge between Claude Code or Codex and messengers: talk to the agent from Telegram, Discord, Feishu, QQ or WeChat
Console tool and skill for Meegle (Lark Project): an agent manages work items, workflow nodes, subtasks and schedules without a browser
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| clawdbot-feishu (this card) | no | 4,221 | ||
| Feishu-MCP | no | API key | 746 | an MCP server for Feishu and Lark where an agent edits documents by blocks and manages tasks; this is a messenger channel for OpenClaw with such tools built in |
| Lark CLI | yes | 17,988 | the official Lark and Feishu CLI for the terminal; this is a channel plugin through which a bot answers people in chats |
README in short
The README, in English and Chinese, goes from installation to configuration: permissions, event subscriptions, access policies and a feature list. A Wiki with practical tips sits alongside, and the end covers common problems: the bot not receiving messages, a 403 error and replies without streaming.