← Back to Skills Marketplace
yang1002378395-cmyk

Dingtalk Connector Guide

by yang1002378395-cmyk · GitHub ↗ · v2.0.0 · MIT-0
cross-platform ✓ Security Clean
551
Downloads
0
Stars
3
Active Installs
30
Versions
Install in OpenClaw
/install dingtalk-connector-guide
Description
钉钉机器人接入指南 - OpenClaw 连接钉钉完整教程。适合:中国企业用户、钉钉开发者。
README (SKILL.md)

钉钉机器人接入指南

让 AI 助手连接钉钉,自动处理群消息。

前置条件

  1. 钉钉企业账号(管理员权限)
  2. OpenClaw 已安装
  3. 公网可访问的服务器(或内网穿透)

步骤 1:创建钉钉应用

  1. 登录 钉钉开放平台
  2. 进入「应用开发」→「企业内部开发」
  3. 点击「创建应用」
  4. 填写应用信息:
    • 应用名称:AI 助手
    • 应用描述:OpenClaw AI 助手
    • 应用 Logo:上传图标

步骤 2:获取凭证

创建完成后,记录以下信息:

AppKey(Client ID):dingxxxxxxxxxxxxxxx
AppSecret(Client Secret):xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

步骤 3:配置机器人

  1. 进入应用 →「机器人与消息推送」
  2. 点击「添加机器人」
  3. 配置机器人:
    • 机器人名称:AI 助手
    • 机器人图标:上传
    • 消息接收地址:https://your-server.com/webhook/dingtalk

步骤 4:权限配置

在「权限管理」中开通:

  • ✅ 企业会话消息读权限
  • ✅ 企业会话消息写权限
  • ✅ 通讯录只读权限
  • ✅ 成员信息读权限

步骤 5:配置 OpenClaw

# 设置钉钉连接
openclaw connect dingtalk

# 输入凭证
Client ID: dingxxxxxxxxxxxxxxx
Client Secret: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

# 启动服务
openclaw start

步骤 6:测试机器人

在钉钉群中 @机器人 发送消息:

@AI助手 你好

机器人应该回复:

你好!我是 AI 助手,有什么可以帮助你的?

常见问题

Q: 消息接收地址填什么?

需要是公网可访问的 HTTPS 地址。如果没有公网服务器:

# 使用 ngrok 内网穿透
ngrok http 3000
# 将生成的 https://xxx.ngrok.io 填入

Q: 机器人不回复?

检查清单:

  1. 权限是否开通
  2. 服务是否启动
  3. 网络是否可达
  4. 日志是否有错误
# 查看日志
openclaw logs -f

Q: 如何支持图片消息?

需要在钉钉开放平台开通「图片消息」权限,并在 OpenClaw 配置中启用。

高级配置

多群支持

机器人默认支持所有群,可以通过配置限制:

# ~/.openclaw/config.yaml
dingtalk:
  allowed_chats:
    - chat_id_1
    - chat_id_2

自定义欢迎语

dingtalk:
  welcome_message: |
    欢迎加入!我是 AI 助手。
    有问题随时 @我

工作时间限制

dingtalk:
  work_hours:
    start: "09:00"
    end: "18:00"
    timezone: "Asia/Shanghai"

需要帮助?

  • 📖 完整文档:https://docs.openclaw.ai
  • 💬 技术支持:
    • 基础接入:¥99
    • 高级配置:¥299
    • 企业定制:¥999

联系:微信 yang1002378395 或 Telegram @yangster151

Usage Guidance
This file is a plaintext setup guide (no code) for connecting OpenClaw to DingTalk. Before following it: 1) verify you trust the OpenClaw binary/service that will store your AppKey/AppSecret; 2) store AppKey/AppSecret in a secure place (secrets manager or verified OpenClaw config) and avoid pasting them into untrusted UIs; 3) if you use ngrok or another tunnel, be aware traffic will be exposed through that service; 4) the contact details and paid support offers in the doc are external and unrelated to the skill—treat them like any third‑party vendor outreach. If you need a higher assurance review, ask for the exact OpenClaw client implementation or documentation that will handle your credentials.
Capability Analysis
Type: OpenClaw Skill Name: dingtalk-connector-guide Version: 2.0.0 The skill bundle is a purely instructional guide for connecting OpenClaw to the DingTalk platform. It contains no executable code, obfuscated scripts, or malicious instructions; it focuses on documenting standard API integration steps, credential management, and webhook configuration in files like SKILL.md and skill.json.
Capability Assessment
Purpose & Capability
Name/description match the content: the SKILL.md is a step‑by‑step guide to create a DingTalk app and configure OpenClaw. It does not request unrelated binaries, services, or credentials.
Instruction Scope
Instructions stay within the scope of onboarding a DingTalk bot (creating app, obtaining AppKey/AppSecret, webhook URL, OpenClaw commands, optional ngrok for tunneling). It tells the user to place settings in ~/.openclaw/config.yaml and to run openclaw commands — expected for this guide. Note: it suggests using ngrok (an external tunnel) and entering secrets into OpenClaw; users should ensure they trust the OpenClaw binary/service before providing secrets.
Install Mechanism
No install spec or code is included (instruction-only), so nothing is downloaded or written by the skill itself.
Credentials
The guide does not declare or request environment variables or unrelated credentials. It appropriately expects the user to obtain DingTalk AppKey/AppSecret for the integration; these are proportionate to the described task. Users should store them securely in OpenClaw or a secrets manager.
Persistence & Privilege
always is false and there are no code files that would persist or modify other skills. The guide references editing OpenClaw's own config file (~/.openclaw/config.yaml), which is appropriate for this integration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install dingtalk-connector-guide
  3. After installation, invoke the skill by name or use /dingtalk-connector-guide
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.0
重大更新:优化钉钉连接器配置指南
v1.0.52
- Version bumped to 1.0.52 with no file changes detected. - No updates to documentation, features, or configuration.
v1.0.51
- No file changes detected in this version. - Skill remains at version 1.0.0 with unchanged content and instructions. - No new features, fixes, or documentation updates.
v1.0.50
- No file changes detected in this version. - The skill guide, description, and metadata remain unchanged. - No new features, fixes, or documentation updates included in this release.
v1.0.49
- No changes were detected in this version; the skill content remains the same. - Version number updated to 1.0.49.
v1.0.48
- No changes detected in this version; content and configuration remain the same. - Version number updated, but file contents are unchanged.
v1.0.47
No file changes detected in this version. - No updates or modifications in this release.
v1.0.46
- No file changes detected in this version. - Functionality and guide content remain the same as the previous release.
v1.0.45
- No file changes detected in this version. - Version and content remain unchanged from previous release.
v1.0.44
- No file changes detected in this version. - No updates or modifications to documentation or code. - Functionality and content remain unchanged from the previous release.
v1.0.43
- No file changes detected in this version. - Documentation, configuration instructions, and features remain unchanged. - No updates or modifications introduced in this release.
v1.0.42
- No file changes detected in this version. - Content and functionality remain the same as the previous release.
v1.0.41
No changes detected in this version. - Version bumped to 1.0.41 with no file or content updates.
v1.0.40
- No file changes detected in this version. - The documentation, configuration guide, and files remain unchanged.
v1.0.39
Version 1.0.39 - No file changes detected in this release. - All features and documentation remain the same as the previous version.
v1.0.38
No changes detected in this version.
v1.0.37
No file changes detected in this version. - No updates were made; content and instructions remain the same as the previous version.
v1.0.36
- Version bump to 1.0.36 with no file changes detected. - No updates to documentation or code.
v1.0.35
- No changes detected in this version (1.0.35). - All files and documentation remain the same as the previous release.
v1.0.34
No changes detected in this version. - No updates or file changes were made for version 1.0.34.
Metadata
Slug dingtalk-connector-guide
Version 2.0.0
License MIT-0
All-time Installs 4
Active Installs 3
Total Versions 30
Frequently Asked Questions

What is Dingtalk Connector Guide?

钉钉机器人接入指南 - OpenClaw 连接钉钉完整教程。适合:中国企业用户、钉钉开发者。 It is an AI Agent Skill for Claude Code / OpenClaw, with 551 downloads so far.

How do I install Dingtalk Connector Guide?

Run "/install dingtalk-connector-guide" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Dingtalk Connector Guide free?

Yes, Dingtalk Connector Guide is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Dingtalk Connector Guide support?

Dingtalk Connector Guide is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Dingtalk Connector Guide?

It is built and maintained by yang1002378395-cmyk (@yang1002378395-cmyk); the current version is v2.0.0.

💬 Comments