Connect Langflow to WeCom Intelligent Bot

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

Langflow builds agents and flows with a drag-and-drop editor. LangBot runs a flow through the Langflow API 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 Langflow 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 Langflow

1. Build a flow in Langflow (the Simple Agent template is a good start).
2. Create an API key under Settings.
3. Copy the Flow ID from Share → API access.

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

• Connection refused: http://localhost:7860 only works when Langflow runs on the same host and network namespace as LangBot.
• 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 Langflow 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 Langflow runner guide
• Other AI back ends on WeCom Intelligent Bot: Dify · n8n · Coze · DeepSeek · OpenAI (ChatGPT models)
• Langflow on other platforms: Telegram · Discord · Slack · Lark (Feishu) · DingTalk · WeCom (internal app)