# Connect n8n to WeCom (internal app)

Source: https://langbot.app/docs/en/recipes/n8n/wecom

Step-by-step guide to running your n8n app as a WeCom (internal app) bot with LangBot: n8n setup, bot credentials, networking, testing and troubleshooting.

This recipe puts your n8n app behind a WeCom (internal app) bot. LangBot receives messages from WeCom (internal app), 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](https://space.langbot.app/cloud) (no server needed) or a [self-hosted deployment](https://langbot.app/docs/en/deploy/langbot/docker.md) with Docker or `uvx langbot`.
- A n8n account or instance that LangBot can reach over the network.
- A WeCom self-built app: **Corporate ID**, the app **Secret**, the **Contact Sync Secret**, and the callback **Token** and **EncodingAESKey**.

## Networking

WeCom delivers messages to a callback URL, so LangBot needs a public domain with HTTPS (see [reverse proxy and SSL](https://langbot.app/docs/en/workshop/production/proxy-and-ssl.md)). LangBot Cloud includes a ready-to-use public URL.

## 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](https://space.langbot.app/market).

| Field               | Value                                                      |
| ------------------- | ---------------------------------------------------------- |
| Runner              | **n8n** (official n8n workflow runner plugin)              |
| Webhook URL         | The workflow's production webhook URL                      |
| Authentication Type | None, Basic Auth, JWT or Header, matching the trigger node |

## 3. Create the WeCom (internal app) bot

1. Create a bot with the **WeCom** adapter, enter the Corporate ID, app Secret and Contact Sync Secret, enable it and copy the webhook callback URL.
2. In the WeCom admin console, open **Receive Messages → Set API Reception**, paste the URL, generate the Token and EncodingAESKey, save them in LangBot first and then in WeCom. Add LangBot's outbound IP to **Corporate Trusted IP**.

## 4. Bind and test

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

Open the app in the WeCom client and send it a message.

## 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.
- **request URL failed** when saving the callback: the URL is not publicly reachable over HTTPS, or the Token/EncodingAESKey in LangBot does not match.
- Replies fail to send: add LangBot's outbound IP to the corporate trusted IP list.
- 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 (internal app)?

Yes, or use LangBot Cloud. WeCom delivers messages to a callback URL, so LangBot needs a public domain with HTTPS (see [reverse proxy and SSL](https://langbot.app/docs/en/workshop/production/proxy-and-ssl.md)). LangBot Cloud includes a ready-to-use public URL.

### Does the WeCom (internal app) bot support streaming replies?

Check the [platform feature matrix](https://langbot.app/docs/en/insight/platform-features.md) for what this platform supports. Replies are delivered once the AI back end has finished.

### 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 (internal app) setup guide](https://langbot.app/docs/en/usage/platforms/wecom/wecom.md)
- [Full n8n runner guide](https://langbot.app/docs/en/usage/pipelines/n8n.md)
- Other AI back ends on WeCom (internal app): [Dify](https://langbot.app/docs/en/recipes/dify/wecom.md) · [Coze](https://langbot.app/docs/en/recipes/coze/wecom.md) · [Langflow](https://langbot.app/docs/en/recipes/langflow/wecom.md) · [DeepSeek](https://langbot.app/docs/en/recipes/deepseek/wecom.md) · [OpenAI (ChatGPT models)](https://langbot.app/docs/en/recipes/openai/wecom.md)
- n8n on other platforms: [Telegram](https://langbot.app/docs/en/recipes/n8n/telegram.md) · [Discord](https://langbot.app/docs/en/recipes/n8n/discord.md) · [Slack](https://langbot.app/docs/en/recipes/n8n/slack.md) · [Lark (Feishu)](https://langbot.app/docs/en/recipes/n8n/lark.md) · [DingTalk](https://langbot.app/docs/en/recipes/n8n/dingtalk.md) · [WeCom Intelligent Bot](https://langbot.app/docs/en/recipes/n8n/wecombot.md)