Connect Dify to WeCom Intelligent Bot

This recipe puts your Dify 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.

Dify builds chat assistants, Chatflows, Agents and Workflows. LangBot calls the published app through its Service API, so prompts, tools and knowledge stay in Dify.

What you need

• A running LangBot instance: LangBot Cloud (no server needed) or a self-hosted deployment with Docker or uvx langbot.
• A Dify 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 Dify

1. Build and publish a Chat Assistant (including Chatflow), Agent or Workflow app in Dify.
2. Open the app's Access API page and create an API key.
3. For a Workflow app, output the answer under the key summary.

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

• Self-hosted Dify in Docker on the same host: put both stacks on a shared Docker network and use the container address (for example http://dify-nginx/v1), not localhost.
• Chatflow apps only return what the Answer node outputs.
• 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 Dify 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 Dify runner guide
• Other AI back ends on WeCom Intelligent Bot: n8n · Coze · Langflow · DeepSeek · OpenAI (ChatGPT models)
• Dify on other platforms: Telegram · Discord · Slack · Lark (Feishu) · DingTalk · WeCom (internal app)