What breaks without openclaw dingtalk integration
Manual notifications. Missed approvals. Automation dead outside the bot framework.
→
DingTalk group automation × ActionCard and stream mode ÷ 25-minute install ÷ no Alibaba custom code = enterprise bots that actually fire.
Security check — openclaw dingtalk integration
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.1; outbound HTTPS to api.dingtalk.com compatibility.
Quick start — openclaw dingtalk integration in 25–45 minutes
Setup time: 25–45 minutes
!
You need:
- OpenClaw core
- DingTalk developer account
- registered DingTalk robot application
Install the package:
npm install @soimy/openclaw-channel-dingtalk
1
Create a DingTalk bot in the DingTalk Open Platform console
2
Record AppKey, AppSecret, and webhook URL
4
Set DINGTALK_APP_KEY and DINGTALK_APP_SECRET in .env
5
Register plugin in openclaw.config.js
6
Send a test message via DingTalk console to confirm receipt
Compatibility & status
Works with: Linux, macOS; OpenClaw ≥1.1; outbound HTTPS to api.dingtalk.com
intermediate
Last updated: Aug 2025
★ 290 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — openclaw dingtalk integration
Does this adapter support DingTalk Stream Mode?
Yes. Set mode: 'stream' in plugin config for DingTalk's persistent connection mode.
Can the bot send messages proactively?
Yes, via the DingTalk robot webhook URL. The adapter exposes a ctx.send() method.
Is this officially maintained by Alibaba?
No. It's a community plugin by @soimy. Check GitHub for current maintenance status.