Connect Dify to WeCom Customer Service

This recipe puts your Dify app behind a WeCom Customer Service bot. LangBot receives messages from WeCom Customer Service, 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.
• WeCom Customer Service (WeChat Kefu) with API access: Corporate ID, Secret, and a callback Token and EncodingAESKey.

Networking

Customer Service delivers events to a callback URL, so LangBot needs a public HTTPS address. LangBot Cloud includes one.

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 Customer Service bot

1. In WeCom Customer Service Developer Settings, generate the Token and EncodingAESKey and enter them with the Corporate ID in a bot using the WeCom Customer Service adapter.
2. Enable the bot, paste its webhook callback URL into the admin console, then fill in the Secret and restart the bot. Generate the customer service link or QR code users will open.

4. Bind and test

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

Open the customer service link or scan the QR code in WeChat and send a message.

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.
• Welcome messages can only be sent when WeChat supplies a welcome_code, and only once before it expires.
• 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 Customer Service?

Yes, or use LangBot Cloud. Customer Service delivers events to a callback URL, so LangBot needs a public HTTPS address. LangBot Cloud includes one.

Does the WeCom Customer Service bot support streaming replies?

Check the platform feature matrix for what this platform supports. Replies are delivered once the AI back end has finished.

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