OpenClaw Can it connect to DingTalk, and how
A-Jie's company uses DingTalk company-wide—calendars, to-dos, and daily reports all live there. He followed the tutorial and installed OpenClaw, then combed through the channel list in the official docs: Feishu and WeCom were both there, but DingTalk was nowhere to be found.
First, be clear about the dividing line here:
Quiz timeDoes OpenClaw's official docs channel list include DingTalk?
OpenClaw core doesn't support DingTalk, but the DingTalk team maintains an external plugin; once installed, you can use OpenClaw in DingTalk private chats and group chats. This plugin's repository calls itself "officially produced by DingTalk," but OpenClaw's official docs don't list it—if something goes wrong, you need to go to the plugin repository, not OpenClaw.
What you'll be able to do after this lesson
- Install the DingTalk plugin with one command and set up a bot by scanning a QR code
- When the QR scan fails, complete the configuration by manually filling in AppKey / AppSecret
- Chat with OpenClaw inside DingTalk, and know which configuration to change when group chats don't reply
Who made this plugin
| Project | Details |
|---|---|
| Repository | https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector |
| Maintainer | GitHub organization account DingTalk-Real-AI, with the repository description "Official OpenClaw DingTalk channel plugin | DingTalk official OpenClaw plugin" |
| npm package | @dingtalk-real-ai/dingtalk-connector |
| Latest version | 0.8.27 (2026-10-20) |
| Stars | 2,128 (2026-11-20 queried) |
| License | MIT |
| Requirement for OpenClaw | ≥ 2026.8.1; older OpenClaw versions should use plugin 0.8.25 |
Capabilities listed in the README: receiving and replying to group chat and private chat messages, @mentioning members; AI Card streaming replies; creating, appending to, and searching DingTalk Docs; DING high-priority alerts; personal to-dos; AI tables; calendar events; daily and weekly reports. Group to-dos and cloud-drive files are marked "Coming Soon" and not usable yet.
There is also another community plugin soimy/openclaw-channel-dingtalk (maintained by a personal account, 1,662 stars, 2026-11-20 queried). This lesson only covers the one from the DingTalk team.
- I understand this plugin is not part of OpenClaw core, and issues should be filed in the plugin repository
Read the security notice before using it
Before the installation instructions, the plugin's README includes a separate section, "Security and Risk Notice (must read before use)". The key points are:
- It connects to OpenClaw's AI automation capabilities, which carry inherent risks such as model hallucination, uncontrolled execution, and prompt injection.
- After authorization, OpenClaw will act as your user identity to operate within DingTalk within the authorized scope, which may lead to sensitive data leaks or unauthorized operations.
- The plugin enables multiple layers of security protection by default, and the README strongly recommends not modifying any default security configuration.
- It's recommended to treat it as a personal conversation assistant and avoid deploying it directly to an enterprise production environment; if you use it in a company account, follow your company's information security policies.
Also, this tutorial's baseline OpenClaw 2026.10.9 is affected by the high-severity advisory GHSA-pw3x. Before connecting OpenClaw to your company IM, first follow Upgrade and Version Channels to upgrade to 2026.11.4 or later, or 2026.10.33.
- I've read the plugin's security notice and confirmed my OpenClaw version
Step 1: Confirm your OpenClaw version
Why: starting with plugin 0.8.26, it switched to the new plugin SDK of OpenClaw 2, which requires at least OpenClaw 2026.8.1.
openclaw -vYou should see: a version number no lower than 2026.8.1. This tutorial's baseline 2026.10.9 meets the requirement, but please upgrade first to a version unaffected by the advisory as described in the previous section.
- Version number ≥ 2026.8.1
Step 2: Install with one command and authorize by QR code
Why: this is the method recommended by the README—installing the plugin and creating the bot are done in one go.
npx -y @dingtalk-real-ai/dingtalk-connector installThe terminal will display a DingTalk authorization QR code. Scan it with the DingTalk mobile app and tap "Create New Bot in One Click".
You should see: the terminal prints Success! Bot configured., indicating authorization is complete.
Then restart the Gateway so the new channel takes effect:
openclaw gateway restartThe README specifically notes that a failed QR scan (timeout, QR code not displaying, etc.) does not affect the plugin installation itself, and you can proceed to step 3 for manual configuration.
- Saw
Success! Bot configured.and restarted the Gateway
Step 3 (if the QR scan fails): Manually fill in credentials
Why: when the QR scan isn't available, you create an app yourself on the DingTalk Open Platform and write the credentials into the OpenClaw configuration.
- Open the DingTalk Open Platform https://open-dev.dingtalk.com/ and go to "App Development".
- On the app details page, create an OpenClaw bot app in one click.
- Under "Credentials & Basic Info", copy the AppKey (Client ID) and AppSecret (Client Secret).
Edit ~/.openclaw/openclaw.json (on Windows it's C:\Users\<你的用户名>\.openclaw\openclaw.json) and add the following under channels:
{
"channels": {
"dingtalk-connector": {
"enabled": true,
"clientId": "dingxxxxxxxxx",
"clientSecret": "your_app_secret"
}
}
}If the file already has content, only add the dingtalk-connector section under the channels node. These two values are the bot's unique credentials—don't post them in group chats or commit them to a code repository. After editing, run openclaw gateway restart.
You should see: the Gateway restarts normally with no configuration errors.
- Filled in clientId and clientSecret in
channels.dingtalk-connector
Step 4: Say your first words in DingTalk
Why: a private chat is the fastest end-to-end verification.
Find the bot you just created in DingTalk and send it a message in a private chat.
You should see: the bot replies. The plugin supports AI Card streaming replies, and the message card will show status changes such as thinking, generating, and complete.
Then add the bot to a test group and @mention it with a question.
- Received one reply each in private chat and group chat
Didn't work?
The plugin repository's FAQ page lists several scenarios:
Look it upWhat I'm running into is…
Click one to see.
For the case where group chats only reply with fallback text, the configuration to add is:
{
"messages": {
"groupChat": {
"visibleReplies": "automatic"
}
}
}Then openclaw gateway restart. The reason given on the FAQ page is: group chats by default only reply through the message tool, so the plugin cannot get the text and falls back to the fallback message. Newer versions of the plugin attach this fix guide directly in the fallback message.
For more issues, see the plugin repository's docs/TROUBLESHOOTING.md and Issues. For problems belonging to OpenClaw itself (gateway, models, multi-channel), the README directs you to openclaw/openclaw's Issues.
Checkpoint
- I can clearly state: DingTalk is not an OpenClaw core channel; it uses an external plugin maintained by the DingTalk team
- My OpenClaw ≥ 2026.8.1, and I have upgraded to a version not affected by GHSA-pw3x
- The bot can reply in DingTalk private chats
- When it only replies with the fallback message after being @-mentioned in a group, I know to change
messages.groupChat.visibleReplies
Common misunderstandings
Assuming that the "DingTalk official plugin" means official support from OpenClaw. "Official" is the plugin repository's own description, meaning it is produced by the DingTalk team. OpenClaw's official documentation does not include the DingTalk channel; the plugin's compatibility and issues are the responsibility of the plugin repository.
Assuming it can be safely rolled out company-wide once installed. The plugin's README itself recommends using it as a personal assistant and avoiding direct deployment to enterprise production environments; after authorization, OpenClaw operates DingTalk as you. To use it in a company, first go through Security Hardening (1): Access Control and Identity.
Assuming group To-Dos and cloud drive are already usable. The README marks these two items as Coming Soon. What is currently usable are personal To-Dos, documents, schedules, AI sheets, daily reports, and DING.
Next section
The office IM is set up, so you can switch to another track: B1 Daily Morning Brief to have Claw send a summary of news to your IM at a fixed time every day.