DingTalk
This is a shipped config-backed outbound surface. Dingtalk custom robot surface is outbound-onlyAt A Glance
| Field | Value |
|---|---|
| Catalog id | dingtalk |
| Config key | dingtalk |
| Implementation status | config_backed |
| Transport | dingtalk_custom_robot_webhook |
| Aliases | ding, ding-bot |
| Default send target kind | endpoint |
Minimal Config
Smoke Test
Command Surface
| Operation | Command | Usage or status |
|---|---|---|
| custom robot send | dingtalk-send | Usage: loong dingtalk-send [OPTIONS] —text <TEXT> |
| outgoing callback service | dingtalk-serve | dingtalk custom robot surface is outbound-only |
Required Fields For Send
| Requirement | Config paths | Env pointer paths | Default env |
|---|---|---|---|
| channel enabled | dingtalk.enableddingtalk.accounts.<account>.enabled | none | none |
| custom robot webhook url | dingtalk.webhook_urldingtalk.accounts.<account>.webhook_url | dingtalk.webhook_url_envdingtalk.accounts.<account>.webhook_url_env | DINGTALK_WEBHOOK_URL |
Gateway And Ownership
This surface is a direct-send delivery lane. It does not joinmulti-channel-serve or the gateway-owned reply-loop contract today.
Operator Notes
- The custom robot
secretis optional and only matters when the DingTalk webhook is configured for signed requests.
Related Docs
- Continue to Channel Guides for the full shipped channel matrix.
- Continue to Channels for the conceptual surface model.
- Continue to Channel Setup for the shared public setup contract.