Prerequisites
- A WeCom admin account
- A LemonClaw instance:
- Hosted: create a Claw instance
- Self-hosted: install LemonClaw
Setup Guide
Create a WeCom App
- Log in to WeCom Admin Console
- Go to App Management → Create App
- Enter an app name, upload a logo, and set the visible range
- Click Create
Get Credentials
- Note your Corp ID — found at My Enterprise → Enterprise Info at the bottom
- In your app settings, copy the Secret (Corp Secret)
Configure Callback URL
- In your app settings, go to Receive Messages → Set API Receive
- For hosted Claw, your callback URL is displayed in the LemonClaw WebUI when you expand the WeCom section:
- For self-hosted LemonClaw, expose your own public HTTPS URL ending in
/webhook/wecom - Set a Token (random string) and EncodingAESKey (43-character random string)
- Click Save — WeCom will verify the callback URL
Open the LemonClaw WebUI
- If you’re using hosted Claw, go to your Claw Dashboard and click Open WebUI
- If you’re self-hosting LemonClaw, open your own WebUI (for example
http://your-ip:18789) and sign in with your token - In the WebUI, navigate to Settings → Channels
- Expand the WeCom section
- Copy the Callback URL shown at the top if you’re using hosted Claw, or enter your own public webhook URL if you’re self-hosting
- Fill in: Corp ID, Corp Secret, Token, EncodingAESKey
- Click Save
Current LemonClaw WeCom support is user-scoped 1:1 messaging. Full group mention, thread, and reply semantics are not available yet.
Troubleshooting
Current LemonClaw WeCom support is user-scoped 1:1 messaging. Full group mention, thread, and reply semantics are not available yet.
Callback URL verification fails
Callback URL verification fails
- Make sure your LemonClaw instance is running
- Verify the URL format:
https://claw-{subdomain}.lemondata.cc/webhook/wecom - Check that Token and EncodingAESKey are saved in LemonClaw config before verifying in WeCom
Bot doesn't respond
Bot doesn't respond
- Verify Corp ID and Corp Secret are correct
- Check that the app is visible to your user account (visible range setting)
- Make sure Token and EncodingAESKey match between WeCom and LemonClaw