dingtalk-connection_skill

Overview

This skill bridges DingTalk outgoing webhook messages to a Clawdbot Gateway and relays replies back into DingTalk sessions. It runs a local HTTP endpoint that validates DingTalk signatures, forwards user events to Clawdbot over WebSocket, and returns agent responses to the originating DingTalk conversation. Use it to add DingTalk as a messaging channel for an AI agent or run a local bridge for development and troubleshooting.

How this skill works

The bridge receives DingTalk webhook callbacks on a configurable HTTP path and port, verifies the request using the DingTalk signing secret, and forwards the event to a running Clawdbot Gateway via a local WebSocket connection. The Clawdbot agent processes the message and the bridge posts the generated reply back into the DingTalk session. It supports running as a foreground process or as a macOS launchd service for auto-start.

When to use it

• When adding DingTalk as a messaging channel for an existing Clawdbot agent.
• During local development to test DingTalk-to-agent message flow.
• When troubleshooting webhook delivery, signature validation, or reply routing.
• To run a resilient local bridge with auto-start on macOS.
• When you need a minimal, configurable connector without full cloud hosting.

Best practices

• Keep DINGTALK_SIGNING_SECRET private and set it in the environment before starting the bridge.
• Expose a stable public callback URL (use a reverse proxy or tunnel) so DingTalk can reach the bridge.
• Set DINGTALK_PORT and DINGTALK_PATH to avoid conflicts with other local services.
• Run the bridge as a service (macOS launchd or systemd) in production to ensure uptime.
• Monitor webhook delivery logs and Clawdbot Gateway connection state to catch dropped messages quickly.

Example use cases

• Connect an internal AI assistant to DingTalk so employees can ask questions from chat.
• Run the bridge locally while iterating on agent prompts and observe live responses in DingTalk.
• Validate webhook signature handling during a security audit of messaging integrations.
• Automatically restart the bridge on macOS by installing it as a launchd service.
• Troubleshoot message latency by adjusting DINGTALK_THINKING_THRESHOLD_MS and observing behavior.