Connect n8n to WeCom Intelligent Bot

This recipe puts your n8n app behind a WeCom Intelligent Bot bot. LangBot receives messages from WeCom Intelligent Bot, 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 WeCom intelligent bot in long connection API mode: its BotID and long-connection Secret. One-click setup can fill both.

Networking

Long connection mode needs no public callback URL. The alternative callback-URL mode does, and the two modes cannot be used at the same time.

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 WeCom Intelligent Bot bot

1. Create a bot with the WeCom Intelligent Bot adapter and use One-Click Setup, or create the bot in WeCom, switch its API mode to long connection and enter the BotID and Secret.
2. Set the bot's visibility scope so the right people can use it, then save and enable.

4. Bind and test

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

Find the bot in the WeCom client, chat with it directly, then add it to a group chat 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.
• The long-connection Secret differs from the callback Token/EncodingAESKey. Switching the API mode to callback URL invalidates existing long connections.
• 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 WeCom Intelligent Bot?

No. Long connection mode needs no public callback URL. The alternative callback-URL mode does, and the two modes cannot be used at the same time.

Does the WeCom Intelligent Bot 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 WeCom Intelligent Bot setup guide
• Full n8n runner guide
• Other AI back ends on WeCom Intelligent Bot: Dify · Coze · Langflow · DeepSeek · OpenAI (ChatGPT models)
• n8n on other platforms: Telegram · Discord · Slack · Lark (Feishu) · DingTalk · WeCom (internal app)