Connect n8n to DingTalk

This recipe puts your n8n app behind a DingTalk bot. LangBot receives messages from DingTalk, runs them through a pipeline, and sends the answer back, so you do not write any platform code.

n8n runs the workflow; LangBot handles the chat platform, sessions and delivery and calls your workflow through a webhook for every message.

What you need

• A running LangBot instance: LangBot Cloud (no server needed) or a self-hosted deployment with Docker or uvx langbot.
• A n8n account or instance that LangBot can reach over the network.
• A DingTalk app robot (Client ID and Client Secret). The one-click setup fills both after you authorize on your phone.

Networking

In Stream Mode LangBot connects out to DingTalk, so no public callback URL is needed.

1. Prepare n8n

1. Start the workflow with a Webhook or On chat message trigger. Set Response Mode to Streaming if you want streamed replies.
2. Answer with an AI Agent node (streaming) or a Respond to Webhook node whose response key matches LangBot's output key.
3. Click Active to enable the workflow and copy its production webhook URL.

2. Create a pipeline

Open Pipelines in the LangBot WebUI, create a pipeline (or edit the default one) and set AI as follows. If the runner is not listed, install the official runner plugin from Plugins or the LangBot Space marketplace.

3. Create the DingTalk bot

1. Create a bot with the DingTalk adapter and use One-Click Setup, or create the robot manually and enter its credentials.
2. Use Stream Mode for event delivery. For streaming replies, import LangBot's dingtalk_stream_card.json card template, enable Use Card Replies and paste the Card Template ID.

4. Bind and test

Open the bot, select the pipeline you created, save and make sure the bot is enabled.

Message the robot directly, then add it to a group and @mention it.

Troubleshooting

• Empty replies: the key in Respond to Webhook must match the output key configured in LangBot.
• The test URL only works while the n8n editor is listening; use the production URL of an active workflow.
• Replies arrive as plain text instead of streaming: the card template is not imported or Use Card Replies is off.
• Messages do not arrive: publish the app version and check that Stream Mode is selected under event subscriptions.
• Check Monitoring in the WebUI: every message, pipeline run and error is recorded there.

FAQ

Do I need a server with a public IP for DingTalk?

No. In Stream Mode LangBot connects out to DingTalk, so no public callback URL is needed.

Does the DingTalk bot support streaming replies?

Yes. Enable streaming on the bot; the AI back end must also stream. See the platform feature matrix for details.

Can the same n8n setup serve other platforms too?

Yes. A pipeline can be bound to many bots, so one configuration can answer on several platforms at once.

Related guides

• Full DingTalk setup guide
• Full n8n runner guide
• Other AI back ends on DingTalk: Dify · Coze · Langflow · DeepSeek · OpenAI (ChatGPT models)
• n8n on other platforms: Telegram · Discord · Slack · Lark (Feishu) · WeCom (internal app) · WeCom Intelligent Bot