wechat advanced active

OpenClaw WeChat

1.3 billion WeChat users. Your bot doesn't reach any of them. Fix that with a 45-minute setup.

openclaw wechat weixin tencent channel-adapter china messaging

What breaks without openclaw wechat adapter

WeChat API requiring business verification. Incoming messages unhandled by bot framework. No unified event model for WeChat types.

→
Full WeChat Official Account bot access × OpenClaw's unified event model ÷ 45-minute setup ÷ no WeChat API custom code = bots running where Chinese users actually are.

openclaw wechat adapter — what it actually does

01
Connects OpenClaw to WeChat Official Accounts via Tencent's messaging API.
02
Handles incoming text, image, voice, and event messages through OpenClaw events.
03
Sends text, media cards, and template messages in response to user interactions.
04
Requires a verified WeChat Official Account — approval takes 1–5 business days.
05
Covers both Subscription Accounts and Service Accounts with different API limits.

Security check — openclaw wechat adapter

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.1; requires verified domain with HTTPS for WeChat server URL compatibility.

Quick start — openclaw wechat adapter in 45–90 minutes

Setup time: 45–90 minutes

!
You need:
  • OpenClaw core
  • WeChat Official Account (OA) or WeChat Work admin access
  • server with verified domain

Install the package:

git clone https://github.com/Xueheng-Li/openclaw-wechat
cd openclaw-wechat && npm install
1
Register a WeChat Official Account and complete identity verification
2
Configure server URL and token in the WeChat OA admin console
3
Install the adapter
4
Set WECHAT_APP_ID, WECHAT_APP_SECRET, and WECHAT_TOKEN in .env
5
Register adapter in openclaw.config.js
6
Verify the server URL via WeChat's admin console verification flow

Troubleshooting openclaw wechat adapter

1
1. Using an unverified server domain — WeChat requires a domain that passes its HTTP challenge verification
2
2. Not handling WeChat's XML message format — WeChat sends messages as XML, not JSON
3
3. Responding after the 5-second WeChat timeout — async operations must use the customer service message API

Compatibility & status

Works with: Linux, macOS; OpenClaw ≥1.1; requires verified domain with HTTPS for WeChat server URL advanced Last updated: Sep 2025 ★ 215 on GitHub MIT

Official docs →

View on GitHub →

FAQ — openclaw wechat adapter

Can this access regular WeChat personal chat messages?

No. WeChat's API only supports Official Accounts and WeChat Work. Personal chat is not accessible via the open API.

What happens if my response takes more than 5 seconds?

WeChat will show the user an error. Use the Customer Service Message API to send async replies instead.

Does this support WeChat Pay notifications?

Payment notifications require a separate WeChat Pay API integration — not included in this adapter.

Related — more like openclaw wechat adapter

Openclaw Qqbot
From OpenClaw logic to QQ groups and DMs — the official Tencent-maintained QQ adapter.
Openclaw Channel Dingtalk
From OpenClaw events to DingTalk workspaces — enterprise-grade messaging integration for Alibaba's platform.
Openclaw Feishu
From OpenClaw workflows to Feishu/Lark — ByteDance's enterprise platform, fully integrated.
OpenClaw Docker CN IM
From npm registry timeouts to fast Docker-based OpenClaw installs inside China.
OpenClaw China
OpenClaw optimised for China — pre-bundled adapters for WeChat, DingTalk, Feishu, and QQ with CN infrastructure configs.

Businesses without WeChat bot automation manually answer every inquiry in a market that expects instant response.

Every unanswered WeChat message is a customer lost to a competitor who automated.

Get it on GitHub →