Dingtalk NodeInstall

Summary

Send a custom DingTalk robot group message using a JSON request body or a form assembled from the selected message type. Form mode supports text, link, Markdown, ActionCard, and FeedCard messages, with optional @ mentions for supported types.

Inputs

• sendBody — Choose the JSON body or the form fields (default).
• jsonBody — In JSON mode, provide the complete DingTalk message payload, including its message type and any content or mention settings.
• msgtype — In form mode, choose text, link, Markdown, ActionCard, or FeedCard.
• content — Required for text messages: the message content.
• title, text, messageUrl, picUrl — For link messages, provide the required title, message text, and destination URL; an image URL is optional.
• title, text — For Markdown messages, provide the required session preview title and Markdown content. Mention a user in the content with their userId if needed.
• title, text, btns — For ActionCard messages, provide the required preview title and Markdown content, then choose whole-card or individual-button navigation. Whole-card mode requires a button title and URL; individual-button mode accepts a button list with titles and URLs, and a button orientation.
• links — For FeedCard messages, add links, each with required text, destination URL, and image URL.
• isAtAll, atMobiles, atUserIds — In form mode for text, Markdown, and ActionCard messages, optionally @ all members or specify comma-separated phone numbers and user IDs to mention. The individual mention fields are shown when @ all is disabled.

Output shape

A single DingTalk API response object per input item.

The operation sends the selected message to the configured custom robot endpoint. The source pack does not expose the response fields.

Links

• n8n community nodes installation guide