Discord alerts for downtime with StillOnline (workarounds)
Teams that live in Discord often ask for a Discord webhook on their uptime tool. StillOnline ships owner alerts on email, Telegram (official StillOnline bot), and Slack Incoming Webhooks — not a native Discord webhook.
That gap is intentional for the current product: you still get fast owner notifications through supported channels, and you can mirror or forward them into Discord with the patterns below. This page is the canonical reference when someone searches “StillOnline Discord alerts.”
Quick answer
Use StillOnline for external HTTP monitoring and a status page. For Discord notifications, enable Slack alerts and mirror to Discord with a vetted bridge, use Telegram DMs from the StillOnline bot for on-call, forward email via Zapier/Make, or poll public status JSON from a bot you host. Native Discord POST from StillOnline is not available today.
Native StillOnline channels (recommended)
Before building bridges, try the channels StillOnline supports out of the box. They are faster to set up and do not depend on third-party bots in your Discord workspace.
| Channel | Setup doc |
|---|---|
| Telegram | Telegram owner alerts — StillOnline bot, no BotFather |
| Slack | Slack Incoming Webhook |
| Email uptime alerts |
On Free you pick one owner channel. On Pro / Ultimate you can enable all three in settings.
Workaround A — Slack webhook → Discord
Many communities already bridge a Slack channel into Discord. StillOnline can feed that Slack channel directly.
- Configure StillOnline Slack alerts to
#stillonline-alerts(or your ops channel). - In Discord, add a supported Slack bridge integration. Evaluate bot permissions and vendor trust for your workspace — bridges are third-party software.
- Outages appear in Slack first, then in Discord for members who never open Slack.
On Free, Slack can be your single owner channel if Discord visibility matters more than Telegram.
Workaround B — Email → Discord
Email automation is slower than Telegram but works when your team already routes alerts through an inbox.
- Enable StillOnline email owner alerts — email guide.
- Use Zapier, Make, or similar: “New email matching subject” → “Post to Discord channel.”
- Expect higher latency than mobile Telegram; fine for non-critical teams or community channels.
Workaround C — Telegram for on-call, Discord for community
Split audiences: founders need a ping in seconds; Discord members need a link when something is wrong.
- Founder on-call: StillOnline Telegram bot in your pocket.
- Community: post the public status page link in Discord during incidents — incident template.
You are not duplicating monitoring; you are choosing where each audience reads updates.
Workaround D — Your bot reads public status JSON
If you already run a Discord bot, you can poll StillOnline’s public status API without storing API keys in Discord.
GET https://api.stillonline.tech/v1/public/status/{project-id} — no API key required. Your bot can announce changes — see REST guide. Respect rate limits; owner alerts remain the fastest path for on-call.
What not to do
These mistakes create security risk or false confidence.
- Do not paste
sk_live_…or other secrets into Discord bots. - Do not expect StillOnline to POST to Discord without an integration — not supported.
- Do not monitor Discord’s gateway instead of your product health URL — see Telegram/Discord bot monitoring.
Related guides
FAQ
Can I use StillOnline Slack alerts and mirror them to Discord?
Yes on Pro / Ultimate (Slack plus other channels), or on Free if Slack is your one owner channel. Point StillOnline Slack alerts to a channel, then use a vetted Slack→Discord bridge — evaluate bot permissions for your workspace.
Should StillOnline replace Telegram with Discord for on-call?
They serve different apps. Many teams use Telegram for mobile founder on-call and Discord for community updates — bot monitoring guide explains product bots vs owner alerts.
Why does StillOnline not offer native Discord owner alerts?
Owner notifications today are email, Telegram (StillOnline bot), and Slack only. For Discord visibility now, use the bridges above or share your status page link in your server during incidents.