What breaks without openclaw wecom enterprise
WeCom API distinct from consumer WeChat requiring separate adapter. Internal notifications still manually sent. Approval workflows unautomated.
→
Enterprise WeCom automation × official Work API via OpenClaw ÷ 30-minute setup ÷ no consumer WeChat confusion = bots inside your company's communication platform.
Security check — openclaw wecom enterprise
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm Linux, macOS; OpenClaw ≥1.1; outbound HTTPS to qyapi.weixin.qq.com compatibility.
Quick start — openclaw wecom enterprise in 30–50 minutes
Setup time: 30–50 minutes
!
You need:
- OpenClaw core
- WeCom enterprise admin account
- registered WeCom application
Install the package:
npm install @wecomteam/wecom-openclaw-plugin
1
Log into your WeCom admin console
2
Create a custom application and note Corp ID, AgentId, and Secret
3
Install the plugin via npm
4
Set WECOM_CORP_ID, WECOM_AGENT_ID, and WECOM_SECRET in .env
5
Configure server URL and token in WeCom admin console
6
Add plugin to openclaw.config.js and restart
7
Send a test message from a WeCom member to verify receipt
Compatibility & status
Works with: Linux, macOS; OpenClaw ≥1.1; outbound HTTPS to qyapi.weixin.qq.com
intermediate
Last updated: Oct 2025
★ 330 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — openclaw wecom enterprise
Can WeCom bots send messages to personal WeChat users?
Yes, if users have linked their WeChat and WeCom accounts — this is the WeCom External Contact feature.
Does this support WeCom's approval workflow API?
Yes. The plugin exposes the approval workflow trigger and status query APIs.
Is this plugin maintained by Tencent?
The WecomTeam organization is a community team, not an official Tencent entity.