What breaks without openclaw feishu bot
Feishu users unreachable. No document automation. Approval flows still manual.
→
Full Feishu/Lark bot access × ByteDance's open platform API ÷ 20-minute setup ÷ no vendor lock-in = automation where your team actually works.
Security check — openclaw feishu bot
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.1; requires HTTPS with valid TLS compatibility.
Quick start — openclaw feishu bot in 20–40 minutes
Setup time: 20–40 minutes
!
You need:
- OpenClaw core
- Feishu developer account
- registered Feishu App
Install the package:
npm install @alexanys/openclaw-feishu
1
Create an app in Feishu Open Platform at open.feishu.cn
2
Enable bot capabilities and note App ID and App Secret
4
Set FEISHU_APP_ID and FEISHU_APP_SECRET in .env
5
Configure event subscription URL in Feishu console
6
Restart OpenClaw and send a test message to the bot
Compatibility & status
Works with: Linux, macOS; OpenClaw ≥1.1; requires HTTPS with valid TLS
intermediate
Last updated: Oct 2025
★ 180 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — openclaw feishu bot
Does this work with Lark (international) as well as Feishu?
Yes. Set apiBase to open.larksuite.com for Lark.
Can the bot send Feishu document links?
The bot can send message cards with hyperlinks to Feishu Docs. Direct doc creation requires the separate Feishu Docs API.
Is the App ID the same as the bot token?
No. The adapter handles token refresh automatically using App ID and App Secret.