Post a confirmed outage
The message goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with WeCom.
One message push, the group robot WeCom renamed, and every confirmed outage arrives in the group your team already runs. Nothing to configure on it.
What lands in WeCom
Everything the alert pipeline sends into WeCom is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same group gets the all clear as soon as the check is green again, under its own heading rather than as another alarm.
Send through your message push
Each event is one text message in the envelope the message push expects, posted by the message push you created in the group.
Say what actually broke
Site, URL, the error in plain language, incident type, status code, response time and the checking locations follow the heading.
Notice a refusal that looks like success
WeCom answers a rejected message with a normal HTTP 200 and an error code inside, which is read and recorded as a failed delivery.
Accept only the WeCom host
The robot URL has to be a qyapi.weixin.qq.com address, so a mistyped or internal URL is refused before any request leaves.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same group, early enough to act without a rush.
A group per monitor
Each channel is its own robot URL, so a client's outage reaches the people who look after that client instead of everyone.
Keep the robot URL out of sight
The key sits in the URL, so it is stored encrypted and shortened to its origin before the attempt shows up under History & Logs → Alerts.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Add a message push
In WeCom open the group, then the overflow menu, then Message Push, still labelled Group Robot in older clients, and create a custom one.
Message push webhook URL
qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxxxStored encrypted
2. Copy the webhook URL
Copy the URL the message push shows, key included, without changing anything on the message push itself.
3. Paste it into Uptimeify
Add the URL as a WeCom channel, assign the monitors it covers, and send the test message.
Before you connect WeCom.
No. Unlike a DingTalk or Lark custom bot, a WeCom message push has no keyword requirement, so the URL is all the setup needs.
It is read, not trusted. A rejected message comes back as HTTP 200 with an error code in the body, and that code turns the delivery into a recorded failure instead of a false success.
Only a qyapi.weixin.qq.com address, the one the message push hands you. Anything else is refused when the channel is saved.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over WeCom, email, webhook or Slack do not draw on it.
Yes. Every channel carries its own robot URL, and you assign monitors and clients to it. A client's outage then reaches the people who look after that client, not everyone.
Every alert, where your team already works.
Connect WeCom once, and every confirmed outage reaches the group that is already open.