What breaks without dingtalk openclaw connector
Custom DingTalk webhook setup. Enterprise approval delays. Unofficial connector risks.
→
Platform-official DingTalk integration × 375-star enterprise connector ÷ 30-minute install ÷ no unofficial workarounds = trusted enterprise bot.
Security check — dingtalk openclaw connector
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm OpenClaw ≥1.1; DingTalk Enterprise account; HTTPS required for webhooks compatibility.
Quick start — dingtalk openclaw connector in 30–60 minutes
Setup time: 30–60 minutes
!
You need:
- OpenClaw core
- DingTalk Enterprise account
- DingTalk Open Platform developer access
Install the package:
npm install @dingtalk-real-ai/openclaw-connector
# Set DINGTALK_APP_KEY, DINGTALK_APP_SECRET in .env
1
Register a DingTalk App in the Open Platform console
2
Install the connector package
3
Configure App credentials in .env
4
Register the connector in openclaw.config.js
5
Enable bot capabilities in the DingTalk console
6
Test by sending a message to the bot in DingTalk
Compatibility & status
Works with: OpenClaw ≥1.1; DingTalk Enterprise account; HTTPS required for webhooks
intermediate
Last updated: Oct 2025
★ 375 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — dingtalk openclaw connector
Is this the same as openclaw-channel-dingtalk?
No — this is maintained by DingTalk's AI team and supports additional enterprise APIs.
Does it support DingTalk Stream Mode?
Yes — configure via the mode option in the connector config.
Can it access the DingTalk organisation directory?
Yes, with the appropriate org permissions granted in the DingTalk console.