# Connect Coze to WeCom (internal app)

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

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

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

Coze builds agents visually. LangBot calls a Coze bot through the Coze API, so you can reach platforms Coze does not publish to and keep one bot across many channels.

## 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 Coze 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 Coze

1. In the Coze developer console, create a token under **API Management** (coze.com offers Personal Access Tokens; coze.cn also supports service credentials).
2. Publish your agent with the **API** channel selected and copy its `bot_id`.

## 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       | **Coze** (official Coze Agent runner plugin)                             |
| API Key      | The Coze token                                                           |
| Bot ID       | The agent's `bot_id`                                                     |
| API Base URL | `https://api.coze.cn` for coze.cn or `https://api.coze.com` for coze.com |

## 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

- Calls fail: check the token and `bot_id` for extra spaces, that the agent was published with the API channel, and that the base URL matches the Coze site.
- **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 Coze 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 Coze runner guide](https://langbot.app/docs/en/usage/pipelines/coze.md)
- Other AI back ends on WeCom (internal app): [Dify](https://langbot.app/docs/en/recipes/dify/wecom.md) · [n8n](https://langbot.app/docs/en/recipes/n8n/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)
- Coze on other platforms: [Telegram](https://langbot.app/docs/en/recipes/coze/telegram.md) · [Discord](https://langbot.app/docs/en/recipes/coze/discord.md) · [Slack](https://langbot.app/docs/en/recipes/coze/slack.md) · [Lark (Feishu)](https://langbot.app/docs/en/recipes/coze/lark.md) · [DingTalk](https://langbot.app/docs/en/recipes/coze/dingtalk.md) · [WeCom Intelligent Bot](https://langbot.app/docs/en/recipes/coze/wecombot.md)