Connect WeCom
ClawPi uses long connections for WeCom intelligent bots, supporting direct messages and group mentions. You need a WeCom account allowed to create a bot and an online ClawPi client.
Create an intelligent bot
- Open the intelligent bot entry in WeCom, create a bot and choose manual configuration. If the entry is unavailable, check the client version and ask your enterprise administrator about creation permission.
- Choose API mode and the long-connection option.
- Set the bot name and visibility, obtain its Bot ID and Secret, and save.
Locations can vary by WeCom version. Refer to Tencent's long-connection setup instructions. ClawPi connects through the official WeCom intelligent bot SDK and does not need a public callback URL.
Enter credentials in ClawPi
Open Message channels → WeCom → Add account, fill in these fields and submit:
| ClawPi field | Source | Note |
|---|---|---|
botId | Bot ID in the intelligent bot's API configuration | Use the bot ID, not the enterprise ID |
secret | Secret for the same bot | Stored as a write-only value, never echoed on the account card |
Wait for Connected. Enter the Secret only in local setup, never in a bot message or task prompt. A regular group bot's Webhook URL cannot replace these credentials.
Verify direct and group messages
- Open the bot using a member within its visibility range and send text.
- Select a workspace and approve the pending pairing in ClawPi, then verify the result returns to the original conversation.
- For group use, add the bot to an allowed group and mention it. Other members must pair separately.
See Connect and pair for workspace changes, pairing and deletion behavior.
Common problems
| Symptom | Action |
|---|---|
| Credential validation fails | Check that the Bot ID and Secret belong to the same bot; remove surrounding whitespace |
| Connection stays pending | Check that long connections are enabled and the computer permits outbound connections |
| A member cannot find the bot | Check visibility and enterprise administrator approval |
| No group reply | Check bot membership, the mention and sender pairing |
After rotating a secret, update its connection without deleting healthy accounts. See Troubleshooting if the problem persists.