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 DingTalk.
One custom robot in the group, and every confirmed outage arrives in the chat your team already runs. No app to install.
What lands in DingTalk
Everything the alert pipeline sends into DingTalk 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 custom robot
Each event is one text message in the envelope the custom robot expects, posted by the robot you created in the group.
Carry the security keyword
Every message leads with the keyword Uptimeify, so a robot secured by a custom keyword accepts it instead of dropping it silently.
Notice a refusal that looks like success
DingTalk 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 DingTalk host
The robot URL has to be an oapi.dingtalk.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 access token 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 group robot
In DingTalk open the group, then Group Settings, then Robot, then Add Robot, and pick the custom one.
2. Set the keyword to Uptimeify
Under the robot's security settings set Uptimeify as the custom keyword, which is the word every message leads with.
Robot webhook URL
oapi.dingtalk.com/robot/send?access_token=xxxxStored encrypted
3. Paste the URL into Uptimeify
Add the URL as a DingTalk channel, assign the monitors it covers, and send the test message.
Before you connect DingTalk.
The custom keyword Uptimeify. Every message leads with that word, so a keyword-secured robot accepts it. A robot secured by signature or by IP range instead will refuse it, because the alerts are not signed.
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 an oapi.dingtalk.com address, the one the group robot 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 DingTalk, 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 DingTalk once, and every confirmed outage reaches the group that is already open.