With WeCom bot notifications, StoreClaw can send store operation alerts, daily reports, anomaly notifications, and automation task results to a specified WeCom group. Once connected, your team can view key updates in WeCom without logging in to StoreClaw.
The current version supports one-way notifications only. StoreClaw can send messages to a WeCom group, but it does not read group chat content or receive replies from the group.
Use cases
WeCom bot notifications are useful for team updates and anomaly alerts, such as:
- Send StoreClaw automation task results to a team group.
- Push daily or weekly store reports, summaries, or key metric updates to an operations group.
- Notify relevant team members when issues occur with orders, inventory, ads, products, or store data.
- Share important updates with a fixed operations group, management group, or project group.
Before you begin
Before you start, make sure that:
- You can access the target WeCom group.
- You have permission to add a group bot to the WeCom group.
- The group is an internal WeCom group. Some groups that include external contacts may not support group bots. Please refer to the options shown in your WeCom client.
- You already have StoreClaw tasks, reports, or notification scenarios that need to be sent to the WeCom group.
Step 1: Add a bot to your WeCom group
- Open the WeCom desktop app.
- Go to the WeCom group where you want to receive StoreClaw notifications.
- Open your target group chat.
- Click ... to open the group settings menu. Find the Message Push, Automated Notifications, or Group Bot option. The entry name may vary depending on your WeCom version. Please refer to the actual interface.
- Click Add.
- Select Custom message push or Custom bot.
- Give the bot a recognizable name, such as
StoreClaw notifications. - After the bot is added, copy the Webhook URL generated for the bot.
The Webhook URL usually starts with:
https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=...
Note: The Webhook URL works as the sending credential for the group bot. Anyone with this URL may be able to send messages to your WeCom group. Do not share it publicly or paste it into untrusted documents, screenshots, or conversations.
Step 2: Connect the WeCom bot in StoreClaw
- Log in to StoreClaw.
- In the left sidebar, click Channels.
- Find WeCom Bot.
- Click the add button on the card.
- Paste the Webhook URL from step 1 into the Webhook URL field.
- Click Connect WeCom Bot.
- Wait until the page shows that the connection is successful.
After the connection is successful, StoreClaw will send a test message to the corresponding WeCom group. Go back to the WeCom group and check whether the test notification is received.
Tip: If your workspace has multiple message channels or bot notification entries, connect the most commonly used business group first. After confirming that the flow works, you can continue configuring other message channels.
Plan your notification groups
StoreClaw currently supports connecting one WeCom bot. We recommend choosing the core business group that most needs to receive StoreClaw notifications, such as a daily operations group, store management group, or cross-functional collaboration group.
If your team manages multiple stores, brands, or regional sites, choose the group with the broadest impact and the highest need for timely updates. This helps avoid spreading notifications across too many communication channels.
After setup, you can adjust notification tasks based on actual usage to reduce unnecessary message interruptions.
Security recommendations
A WeCom bot Webhook URL is essentially a sending credential. To prevent misuse or accidental message sending, follow these recommendations:
- Do not paste the Webhook URL into public documents, chat screenshots, or support ticket comments.
- For internal handover, store the Webhook URL in a controlled document or password management tool.
- If you suspect that the Webhook URL has been exposed, delete the original bot and create a new one in WeCom.
- If a group is no longer used for StoreClaw notifications, remove the related configuration from both WeCom and StoreClaw.
FAQ
Q: Why is the Webhook URL invalid?
A: Please check:
- Whether the full Webhook URL was copied.
- Whether the URL starts with
https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=. - Whether the URL contains extra spaces, line breaks, or invalid characters.
- Whether the WeCom bot has been deleted or recreated.
If the bot has been deleted, add a new bot in WeCom and enter the new Webhook URL in StoreClaw.
Q: Why does StoreClaw show that the connection is successful, but there is no message in the group?
A: Possible reasons include:
- The WeCom group bot has been removed.
- The bot Webhook URL has expired or become invalid.
- WeCom has limited the bot sending frequency.
- You are checking a different WeCom group from the one actually connected.
- The connection was saved, but no notification task has been triggered yet.
You can trigger a test notification or wait for the next automation task to run. If there is still no message, check the following:
- Confirm that the Webhook URL saved in StoreClaw matches the current bot Webhook URL in WeCom.
- Check whether the message was sent to another group with a similar name or to the wrong business group.
- Confirm whether someone recently recreated the bot but did not update the Webhook URL in StoreClaw.
- Confirm that the group bot is still available in the WeCom client.
Q: Can StoreClaw see replies in the WeCom group?
A: No. The current WeCom bot notification only supports sending messages from StoreClaw to a WeCom group. It does not read group messages, recognize replies, or continue conversations in the group.
To continue working on a task, start the conversation inside StoreClaw.
Q: Can I connect multiple WeCom groups?
A: Currently, StoreClaw only supports configuring one WeCom bot Webhook URL. We recommend connecting the commonly used business group first.
Q: What should I do if there are too many bot messages?
A: You can reduce message volume in two ways:
- Reduce unnecessary automation tasks or notification types in StoreClaw.
- Create a dedicated notification group in WeCom to avoid interrupting daily team conversations.
Q: What is the difference between WeCom bot notifications and Lark Bot?
A: They are designed for different use cases:
- WeCom bot notifications: Best for one-way notifications, not two-way conversations.
- Lark Bot: Supports direct interaction with StoreClaw in Lark and can also receive push notifications.
If your goal is to "let the group see results", WeCom bot notifications are more lightweight. If your goal is to "directly interact with StoreClaw in a messaging tool", choose a channel that supports two-way communication.