Channels: DingTalk
DingTalk is a Tier 2 channel. Wayland connects as a DingTalk app and robot. You create the app and copy its client credentials. A webhook secret is only needed if your robot has signed webhook security turned on.
Before you start (prerequisites and accounts)
Section titled “Before you start (prerequisites and accounts)”- A DingTalk developer account and an internal app.
- The Wayland desktop app running with a model provider connected.
Create the credentials (on the provider side)
Section titled “Create the credentials (on the provider side)”- In the DingTalk developer console, create an app and note its Client ID and Client secret (also shown as AppKey and AppSecret).
- Add a robot to the app. If you enable signed webhook security, also note the Webhook secret.
Connect it in Wayland (Settings -> Channels -> DingTalk)
Section titled “Connect it in Wayland (Settings -> Channels -> DingTalk)”- Open Settings -> Channels and choose DingTalk.
- Enter the Client ID.
- Enter the Client secret.
- If your robot uses signed webhook security, enter the optional Webhook secret.
- Save.
Verify (status goes from idle to connected, send a test message)
Section titled “Verify (status goes from idle to connected, send a test message)”After saving, the status moves from idle to connected. Message the robot in DingTalk and confirm a reply.
Route to an assistant or team
Section titled “Route to an assistant or team”Set the assistant and default model on the DingTalk page. Inbound messages route to that assistant.
Troubleshooting
Section titled “Troubleshooting”A wrong client ID or client secret prevents authentication. If you enabled signed webhook security, a wrong webhook secret fails the signature check. Confirm the values you supplied. See Channel Connection Issues.