Post a confirmed outage
The message goes out once enough independent EU locations fail the check often enough in a row, both thresholds sit in your package, not on the first failed request.
Use Uptimeify with Lark and Feishu.
One custom bot in the group, and every confirmed outage arrives in the chat your team already runs, in either edition.
What lands in Lark and Feishu
Everything the alert pipeline sends into Lark and Feishu 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 bot
Each event is one text message in the envelope the custom bot expects, posted by the bot you created in the group.
Carry the security keyword
Every message leads with the keyword Uptimeify, so a bot secured by a custom keyword accepts it instead of dropping it silently.
Notice a refusal that looks like success
Lark answers a rejected message with a normal HTTP 200 and an error code inside, which is read and recorded as a failed delivery.
Accept both editions, and nothing else
Only open.feishu.cn and open.larksuite.com are allowed as the bot host, so a mistyped or internal URL never gets called.
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 bot URL, so a client's outage reaches the people who look after that client instead of everyone.
Keep the bot URL out of sight
The URL is the credential, 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 custom bot
In Lark or Feishu open the target group, then Settings, then Bots, and add a custom bot.
2. Set the keyword to Uptimeify
Under the bot's security settings add Uptimeify as the custom keyword, which is the word every message leads with.
Bot webhook URL
open.larksuite.com/open-apis/bot/v2/hook/xxxxStored encrypted
3. Paste the URL into Uptimeify
Add the URL as a Lark channel, assign the monitors it covers, and send the test message.
Before you connect Lark or Feishu.
The custom keyword Uptimeify, if you secure the bot with keywords at all. Every message leads with that word. A bot secured by signature or by IP range instead will refuse it, because the alerts are not signed.
Both do. open.larksuite.com and open.feishu.cn are the two hosts the integration accepts, and nothing else, which is what keeps a mistyped or internal address from being called.
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.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Lark, email, webhook or Slack do not draw on it.
Yes. Every channel carries its own bot 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 Lark or Feishu once, and every confirmed outage reaches the group chat that is already open.