OpenClaw DingTalk Channel

OpenClaw connects to DingTalk through the DingTalk Open Platform's Stream mode (WebSocket long connection). Unlike traditional webhook setups, Stream mode has the Gateway initiate an outbound WebSocket connection to DingTalk's servers, receiving event pushes in real time — no public IP or domain required. The message flow is: User sends a message in DingTalk → DingTalk Open Platform → Stream push to your Gateway → OpenClaw processes with AI → reply via DingTalk Bot API → message delivered in DingTalk. This architecture is ideal for self-hosted deployments behind NATs or corporate firewalls, since no inbound connections are needed. The Gateway automatically maintains the connection and handles reconnection with exponential backoff.

There are two popular community plugins for DingTalk integration: • @soimy/dingtalk — The most widely used plugin with an active community. Supports both Markdown and AI Card reply formats, and covers the vast majority of use cases. • @dingtalk-real-ai/dingtalk-connector — An officially affiliated project from DingTalk, focused on AI Card streaming replies. Supports multi-agent routing and async mode, but requires OpenClaw v0.7.7+. Both plugins use DingTalk's Stream mode, so the core connection experience is the same. For most users, go with @soimy (more documentation and community support). Choose @dingtalk-real-ai if you need multi-agent routing or async processing.

# Install @soimy version (recommended)
openclaw plugins install @soimy/dingtalk

# Or install @dingtalk-real-ai version
openclaw plugins install @dingtalk-real-ai/dingtalk-connector

Setting up DingTalk integration requires creating an app on the DingTalk Open Platform: 1. Log in to the DingTalk Open Platform at open-dev.dingtalk.com and open the Developer Console. 2. Click 'Create Application' and select 'Internal Enterprise Development' → 'Bot' type. 3. Fill in the app name and description. Once created, go to 'Credentials & Basic Info' and copy the ClientID (AppKey, format: dingXXX) and ClientSecret (AppSecret). 4. Under 'Bot Configuration', set the message receiving mode to **Stream mode** (not HTTP mode). 5. In Permission Management, add the required permissions. Key permissions include: - qyapi_robot_sendmsg (bot message sending) - Card.Instance.Write (card instance write) - Card.Streaming.Write (streaming card write) - mediaId.download and mediaId.upload (media file upload/download) 6. Publish the app and wait for your organization admin to approve it.

# Via environment variables
export DINGTALK_CLIENT_ID="dingXXXXXX"
export DINGTALK_CLIENT_SECRET="your_app_secret"

# Or via CLI
openclaw channels add

The DingTalk plugin supports flexible messaging policies: **DM Policy (dmPolicy):** • open — Anyone can DM the bot and get a response • disabled — Direct messages are turned off entirely **Group Policy (groupPolicy):** • open — Any group member can trigger the bot by @mentioning it • disabled — Group messages are completely ignored In group chats, the bot requires an @mention by default to avoid responding to every message in busy conversations.

{
  "channels": {
    "dingtalk": {
      "dmPolicy": "open",
      "groupPolicy": "open"
    }
  }
}

The DingTalk plugin supports multiple reply formats: • **Text** — Basic plain-text replies • **Markdown** — Formatted content with headings, lists, and links (recommended default) • **AI Card (streaming)** — A ChatGPT-like typewriter effect where the message updates progressively inside a card AI Card streaming provides the best user experience — the response updates in place without flooding the chat with multiple messages. It requires Card-related permissions to be granted in your DingTalk app.

{
  "channels": {
    "dingtalk": {
      "messageType": "markdown",
      "streaming": true
    }
  }
}

The OpenClaw DingTalk plugin handles various message types: **Inbound (receive):** Text, images, audio (with automatic speech recognition), video, and files **File parsing:** .docx, .pdf, .txt, .md, .json, .xlsx, .pptx, .zip and more — files are read and analyzed by the AI **Outbound (send):** Text, Markdown, AI Card, images, and files Audio messages are automatically transcribed to text before being passed to the AI, with no extra configuration needed.

Using the @dingtalk-real-ai plugin, you can configure multi-agent routing to have different AI agents handle different types of conversations. For example, route DMs to a general assistant while sending specific group chats to a specialized support agent. Through OpenClaw's bindings configuration, you can precisely control which agent handles each conversation.

{
  "bindings": [
    { "agentId": "main", "match": { "channel": "dingtalk", "peer": { "kind": "direct" } } },
    { "agentId": "tech-support", "match": { "channel": "dingtalk", "peer": { "kind": "group" } } }
  ]
}

OpenClaw provides several commands for managing your DingTalk bot: • openclaw gateway status — Check Gateway connection status • openclaw gateway restart — Restart the Gateway service • openclaw logs --follow — View real-time logs • openclaw channels add — Interactively add a new channel • openclaw plugins list — List installed plugins • openclaw plugins update @soimy/dingtalk — Update the DingTalk plugin • openclaw doctor — Run a comprehensive diagnostic check