---
title: WeChat
subtitle: Connect a WeChat Official Account and turn inbound conversations into structured leads
slug: documentation/wechat
---

# WeChat

This page explains the OrcaPulse WeChat flow end to end: what credentials are needed, how the webhook is verified, how inbound messages become leads, and what operators should expect after the account is live.

## What this WeChat integration covers

WeChat in OrcaPulse is designed around Official Account messaging. After connection, incoming messages can enter OrcaPulse automatically, be stored as conversation history, and move through lead qualification without manual copy-paste between systems.

The current implementation supports account connection, webhook verification, inbound message capture, lead creation, AI or auto replies, and manual follow-up from the social inbox flow.

- Official Account login: OrcaPulse connects with App ID and App Secret from the WeChat Official Account Platform.
- Webhook-based capture: incoming messages are delivered into OrcaPulse through a verification-safe callback flow.
- AI and manual follow-up: teams can automate early qualification and still reply manually when needed.

## Before you connect

The cleanest setup starts when your team has the right WeChat admin access ready in advance.

- Official Account access: sign in at https://mp.weixin.qq.com/ with an account that can view the app credentials.
- App ID and App Secret: copy these from the developer or basic configuration area for the Official Account.
- Public HTTPS backend: WeChat webhook verification needs a public callback URL, not a localhost-only environment.
- Plaintext callback mode: the current OrcaPulse implementation expects plaintext callback handling.

## Step-by-step setup

1. Open the WeChat Official Account Platform and sign in.
2. Locate the App ID and App Secret for the account you want to connect.
3. In OrcaPulse, open the WeChat page and click Connect WeChat.
4. Paste the App ID and App Secret and confirm the connection.
5. After validation, open the WeChat integration settings in OrcaPulse and copy the generated callback URL, token, and EncodingAESKey.
6. Paste those values into the WeChat server configuration area and complete WeChat’s verification step.

Once setup is complete, OrcaPulse can start receiving inbound account messages and route them into the lead capture flow automatically.

## Webhook verification and delivery

WeChat uses a verification handshake before it will trust your callback URL. OrcaPulse generates the webhook values per integration so each connected account has its own callback details.

- Callback URL: generated by OrcaPulse after connection.
- Token: used for verification and signature validation.
- EncodingAESKey: shown for setup completeness even though the current flow expects plaintext callbacks.
- Verification result: once WeChat verifies the callback, the integration can be treated as webhook-ready.

If messages are not arriving after connection, first confirm that the callback URL is public, reachable over HTTPS, and entered exactly as shown in OrcaPulse.

## Lead capture and replies

After the webhook is live, OrcaPulse can use WeChat messages as a real lead source rather than a passive inbox.

- Inbound message capture: new WeChat conversations are stored as channel activity.
- Contact extraction: phone numbers and email addresses found in the conversation can be attached automatically.
- Duplicate-aware flow: existing lead checks can reduce duplicate creation.
- AI reply option: OrcaPulse can continue the conversation naturally and ask for missing details.
- Manual reply support: operators can still send replies directly when they want human control.

## What your team can do after connect

- Review the connected account and confirm that webhook setup values are stored correctly.
- Watch captured conversations inside the social leads and inbox flows.
- Tune AI DM assistant or auto-reply behavior in lead capture settings.
- Reply manually for high-value or sensitive conversations.
- Promote qualified prospects into the broader OrcaPulse lead pipeline once contact details are complete.

## Troubleshooting

- Connection fails immediately: re-check the App ID and App Secret.
- Webhook verification fails: confirm the callback URL and token were pasted exactly and that the backend is public over HTTPS.
- Messages do not appear after verification: verify that callback mode is aligned with OrcaPulse’s plaintext handling.
- Replies are not sent: check that the integration is active and token refresh is working.
- Users are not converting into strong leads: review whether the conversation is collecting both phone and email.