Dingtalk NodeInstall

Summary

Send a DING message using a specified DingTalk robot by providing necessary message details either as a form or raw JSON.

Inputs

• 发送请求体 — Choose how to send the request body data, either as a form or as JSON.
• 请求体JSON (required) — When sending raw JSON, provide the full request body matching DingTalk's API schema, including robotCode, remindType, receiverUserIdList, and content.
• 发DING消息的机器人ID (required) — The unique robotCode identifying the DingTalk robot used to send the DING message (required if sending as form).
• DING消息类型 — The type of DING message to send: 1 (in-app DING), 2 (SMS DING), or 3 (phone DING). SMS and phone DING require additional purchase; without it only in-app DING is supported (used if sending as form).
• 接收人userId列表 (required) — Comma-separated userId list of the receivers of the DING message (required if sending as form).
• 消息内容 (required) — Content text of the DING message to send (required if sending as form).
• 电话音色 — Voice type for phone DING messages, applicable only if remindType is 3 (phone DING). Options include various female and male voices (used if sending as form and remindType=3).

Output shape

a single JSON object representing the DingTalk API response for the send request

Returned data corresponds to the DingTalk API's response for sending a DING message and may include success or error information.

Examples

Example 1: Send a simple in-app DING message via form inputs specifying robotCode, remindType (default 1), receiverUserIdList, and message content.

Set '发送请求体' to '使用下面定义的表单', provide robotCode, receiverUserIdList (comma-separated), content, and optionally change remindType and callVoice if applicable.

Example 2: Send a customized DING message by providing full JSON request body.

Set '发送请求体' to '使用JSON' and supply a valid JSON body including robotCode, remindType, receiverUserIdList array, and content as per DingTalk API specification.

Links

• n8n community nodes installation guide