n8n has no built-in DingTalk node: n8n’s integrations documentation lists none. To send messages to DingTalk groups, receive DingTalk events, work with DingTalk interactive cards or with AI tables, approvals and to-dos, you install a community node. Most of their READMEs are in Chinese, so this guide sums them up in English, using the description and README each author publishes on npm and our own download data.
What do you need?
| You want to | Look at |
|---|---|
| Interactive cards, including streamed AI replies, and card button callbacks | n8n-nodes-dingtalk-card |
| Robot messages, events without a public server, AI tables, approvals, to-dos and users | @cryozerolabs/n8n-nodes-dingtalk |
| Only send messages through a custom group robot | n8n-nodes-dingtalk or n8n-nodes-dingtalk-bby |
DingTalk community nodes
Our DingTalk hub lists 8 packages that pass our quality rule, with 7,609 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 28 October 2026):

| Package | Weekly downloads | Latest version | Author’s description, in English |
|---|---|---|---|
| n8n-nodes-dingtalk-card | 7,471 | 1.1.0 (26 October 2026) | DingTalk Card Platform lifecycle nodes |
| @cryozerolabs/n8n-nodes-dingtalk | 81 | 0.11.0 (27 October 2026) | DingTalk nodes: Stream event subscription, AI tables, user API, custom robot messages, workbooks and to-dos |
| n8n-nodes-dingtalk | 26 | 0.0.8 (28 June 2025) | DingTalk custom robot |
| n8n-nodes-dingtalk-bby | 18 | 0.3.2 (9 October 2026) | DingTalk robot node and robot card node |
Versions and dates come from the npm registry.
n8n-nodes-dingtalk-card
By far the most installed DingTalk package, and narrow on purpose: its README says it covers the DingTalk Card Platform lifecycle and card callbacks, not approvals, to-dos, tables or general robot messaging. Card operations are Create & Deliver, Update, Streaming Update and Finalize, and version 1.1.0 adds a profile for DingTalk’s AI Markdown streaming cards. A trigger receives button and action callbacks over DingTalk Stream. The repository ships example workflows for a notification hub, a report hub and card actions.
You create a DingTalk enterprise internal application, grant it the Card Platform permissions and enter it in a DingTalk Card API credential. Its README lists Node.js 24 and n8n 2.44.x as the supported versions, so check your n8n version first.
@cryozerolabs/n8n-nodes-dingtalk
The broadest package. Its README lists:
- Event subscription: a trigger in DingTalk’s Stream mode, which per the README needs no public server, IP address or domain.
- Robot: custom robot group messages, and robot messages in group chats as text, links, Markdown, images, ActionCards, voice, files and video.
- AI tables (Notable): tables, fields and records, plus reading the base, sheet and view IDs from a table URL.
- Workbooks: sheets, rows and columns, and cell ranges.
- OA approvals: get approval instances and their IDs, add comments, download attachments and list the forms a user can see.
- To-dos: create, list, get, update and delete tasks.
- Users and documents: look up users by ID or phone number, and upload documents.
- API: a custom request to any DingTalk JSON API, with the access token refreshed for you.
The credential takes the Client ID and Client Secret of a DingTalk enterprise internal application.
n8n-nodes-dingtalk and n8n-nodes-dingtalk-bby
n8n-nodes-dingtalk sends messages through a DingTalk custom robot in text, link, Markdown, ActionCard and FeedCard formats, or as raw JSON; its last release dates from June 2025. n8n-nodes-dingtalk-bby describes a robot node and a robot card node. Of the smaller packages on the hub, n8n-nodes-dingtalk-stream still carries n8n’s starter template as its README, so we don’t describe it.
Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.
How to choose
- Cards that update as an AI writes, or buttons that call back into n8n: n8n-nodes-dingtalk-card, the most used package, if your n8n version matches.
- Most other DingTalk work, or events without exposing n8n to the internet: @cryozerolabs/n8n-nodes-dingtalk.
- Just post alerts to a group: n8n-nodes-dingtalk or the robot operations of @cryozerolabs/n8n-nodes-dingtalk.
To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Similar guides: Lark and Feishu and Microsoft Teams.
FAQ
Does n8n have a DingTalk node?
Not a built-in one. DingTalk support comes from community nodes, or from calling DingTalk’s API with the HTTP Request node.
Can n8n receive DingTalk events without a public URL?
The @cryozerolabs/n8n-nodes-dingtalk README says its Stream mode trigger needs no public server, IP address or domain. n8n-nodes-dingtalk-card also receives card callbacks over Stream.
How do I send a DingTalk group message from n8n?
With a robot node such as @cryozerolabs/n8n-nodes-dingtalk or n8n-nodes-dingtalk, which send text, Markdown, links or ActionCards to a group through a robot.
What is the most used DingTalk community node?
n8n-nodes-dingtalk-card, with 7,471 weekly npm downloads on 28 October 2026.



