openclaw-channel-dingtalk

OpenClaw channel plugin that integrates with DingTalk (企业内部机器人) using a Stream mode to receive and send messages for private chats, group chats, and @机器人, including support for multiple message types and AI/markdown reply flows.

Evaluated Mar 30, 2026 (0d ago)
Homepage ↗ Repo ↗ Communication ai-ml automation communication dingtalk openclaw streaming channel-plugin typescript
⚙ Agent Friendliness
46
/ 100
Can an agent use this?
🔒 Security
54
/ 100
Is it safe for agents?
⚡ Reliability
38
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
60
Error Messages
0
Auth Simplicity
70
Rate Limits
20

🔒 Security

TLS Enforcement
80
Auth Strength
55
Scope Granularity
25
Dep. Hygiene
45
Secret Handling
60

Communication appears intended for internal enterprise use; README advises using clientId/clientSecret configuration. No explicit guidance in the excerpt about TLS enforcement, secret storage, logging redaction, or least-privilege scopes. Dependencies include axios and parsing libraries (axios/form-data/mammoth/pdf-parse/zod), but no CVE or security posture details are provided in the given content.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
60
Error Recovery
35
AF Security Reliability

Best When

You want an internal DingTalk enterprise bot integrated into OpenClaw with streamed responses and no need to expose public endpoints.

Avoid When

You cannot satisfy DingTalk enterprise credential requirements (clientId/clientSecret) or you require a clearly documented, external REST API contract independent of OpenClaw.

Use Cases

  • • Enable an OpenClaw bot to respond in DingTalk chats (DM, group, @mention)
  • • Stream AI-generated replies in DingTalk using OpenClaw outbound capabilities
  • • Handle rich DingTalk content types (text, images, audio/video, files, and document cards) and convert/attach them to OpenClaw flows
  • • Support multi-agent / multi-robot bindings and experimental routing via @-based routing

Not For

  • • Use as a public-facing webhook service (README indicates Stream mode without public IP/webhook entry)
  • • Projects needing a standalone, vendor-hosted API/SaaS (this is a channel plugin integrated into OpenClaw)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: DingTalk app credentials (clientId/clientSecret) configured in OpenClaw channels section
OAuth: No Scopes: No

Authentication/authorization is described at the configuration level (clientId/clientSecret). The README excerpt does not specify OAuth flows or fine-grained scopes.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; as a plugin, costs likely depend on OpenClaw and your DingTalk/AI usage.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ No MCP server indicated; agent integration depends on how OpenClaw plugins expose actions/events internally.
  • ⚠ NPM install via ClawHub is noted as buggy; prefer source installation as documented.

Alternatives

Other OpenClaw channel plugins for different IM platforms (if available) Build a custom DingTalk integration directly against DingTalk APIs (bypassing this plugin)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for openclaw-channel-dingtalk.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.

6533
Packages Evaluated
19870
Need Evaluation
586
Need Re-evaluation
♥
Community Powered