docs/src/content/docs/en/agentclaw/wecom.md
WeCom is for bringing the agent into an enterprise messaging environment, so team members can receive and reply to agent messages inside WeCom.
New to AgentClaw? Read the AgentClaw overview and usage and configuration first, then come back here for a single platform.
| Name in the WeCom dashboard | CCR field | Required | Notes |
|---|---|---|---|
企业ID (CorpID) | Corp ID | Required | Enterprise-level ID, under "My Enterprise" |
| AgentId | Agent ID | Required | The self-built app's ID |
| Secret | Secret | Required | App secret — admins usually confirm on their phone to view it |
CCR exchanges Corp ID and the app Secret for a WeCom access_token for you — you don't fetch it manually.
我的企业 (My Enterprise) at the top.企业信息 (Enterprise Info).企业ID (CorpID) and copy it for CCR's Corp ID.应用管理 (App Management).自建 (Self-built) section.创建应用 (Create App).CCR.AgentId for CCR's Agent ID.Secret and click to view it.Secret.If WeCom asks for
企业可信IP(Trusted Enterprise IPs), add the outbound public IP of the machine running the CCR Bot Gateway (or your relay service's outbound IP).
For lock-screen-only alerts, use Handoff without Forward agent messages.
How to tell it worked: WeCom shows the agent's message, and replies keep the agent going.
企业可信IP in the WeCom dashboard.