How to Connect OpenClaw to Enterprise WeChat: A Complete Step‑by‑Step Guide
This article walks you through the entire process of integrating OpenClaw with Enterprise WeChat, covering prerequisite checks, creating an API‑mode robot with long‑connection, binding credentials, two deployment paths (Tencent Cloud Lighthouse or local), common pitfalls, and post‑integration extensions.
Integration overview
Connecting Enterprise WeChat (WeCom) with OpenClaw turns the chat platform into an AI entry point for the organization. OpenClaw handles model calls, message processing, and can be extended with additional capabilities.
Pre‑checks
Enterprise WeChat client is updated to the latest version (the official workflow assumes the new UI).
OpenClaw is installed and running (locally or on Tencent Cloud Lighthouse).
You have permission to create an Enterprise WeChat smart robot (required to save robot configuration).
Step 1 – Create the Enterprise WeChat robot
The robot must be created in API mode and using the long‑connection option; any other mode will cause later failures.
1. Open the Workbench and locate “Smart Robot”
2. Create a robot and select API mode
3. Choose “Long Connection” and copy Bot ID and Secret
These two parameters are required when binding OpenClaw.
Step 2 – Bind the robot to OpenClaw
Select the path that matches your deployment.
Option A – OpenClaw on Tencent Cloud Lighthouse
Open the Lighthouse instance and go to “Application Management”.
Select the channel “Enterprise WeChat (Long Connection)”.
Paste the Bot ID and Secret obtained earlier.
Click “Add and Apply”, wait for the configuration to take effect, then restart.
Return to Enterprise WeChat, save the robot and send a test message.
Option B – OpenClaw running locally
Install the Enterprise WeChat plugin
openclaw plugins install @wecom/wecom-openclaw-pluginStart or restart the OpenClaw gateway openclaw gateway start Add the Enterprise WeChat channel openclaw channels add Choose “Enterprise WeChat” in the selector.
Enter the Bot ID and Secret.
Select finish.
Choose Pairing – this binds the OpenClaw instance to the robot.
Complete the remaining configuration and confirm the channel is added.
In Enterprise WeChat, save the robot and send a message; the bot replies with a pairing key.
Copy only the last line of the key from the message and paste it back into the terminal to finish pairing.
Send another message to verify normal replies.
Common pitfalls
Choosing a robot mode other than API or not using long‑connection leads to mismatches.
Adding the channel but skipping the Pairing step leaves the robot non‑functional.
Copying the wrong part of the pairing message; only the last line contains the key.
Possible extensions after basic conversation
1. Connect to Smart Sheet webhook
Enable “Receive external data” in a Smart Sheet to obtain a unique webhook URL. OpenClaw can write results back to the sheet or update existing rows.
2. Call additional Enterprise WeChat APIs
Obtain the enterprise ID and application Secret from the admin console, send them to the bound OpenClaw robot, retrieve an access token, and invoke APIs such as document handling or workflow automation.
Quick checklist for the minimal closed loop
Create an API‑mode robot in Enterprise WeChat.
Select long‑connection and record Bot ID and Secret.
Add the Enterprise WeChat channel in OpenClaw.
Complete Pairing and send a test message to verify.
References
Enterprise WeChat Help Center: https://open.work.weixin.qq.com/help2/pc/cat?doc_id=21657
Smart Sheet external data: https://developer.work.weixin.qq.com/document/path/101239
Access token retrieval: https://developer.work.weixin.qq.com/document/path/91039
Document API usage: https://developer.work.weixin.qq.com/document/path/97392
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Tech Ocean
Focused on AI programming, sharing ready-to-use development efficiency solutions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
