Alert channels and webhooks

Email

Email is always on. You get one message when an outage is confirmed and one when the site recovers. If you switch on "still down" reminders in your settings (after 1, 4 and 24 hours), a site that stays down keeps reminding you until you acknowledge the outage with the link in the email. SSL, domain and Google-safety warnings use the same address.

One webhook address

In your dashboard settings, paste a single address into the webhook field. We recognise the service from the address and format the message for it:

• Slack: create an incoming webhook in your Slack workspace and paste its address.
• Discord: in a channel's settings choose Integrations, create a webhook and paste its address.
• Microsoft Teams: add an incoming webhook connector to a channel and paste its address.
• Telegram, one tap: open Telegram alerts in your dashboard settings, press Connect Telegram, open the link and press Start. Add the OwlHound bot to a group and press Start there to alert a whole team. Send /status to the bot any time to see your sites. This is separate from the webhook field, so you can use both.
• Telegram, your own bot: create a bot with @BotFather, add it to your chat, then paste https://api.telegram.org/bot<TOKEN>/sendMessage?chat_id=<CHAT_ID> as the webhook.
• Anything else: any public https address, for example Zapier, n8n or your own server.

The JSON message

For addresses we do not recognise, we send a JSON body with these fields: event (monitor.down, monitor.up, monitor.still_down, ssl.expiring, domain.expiring, seo.issue or alert), status (down, up, warning or info), subject, body, text, source (always owlhound) and, when known, monitor, url, started, ended and cause.

Private and internal addresses are refused for safety. If your endpoint answers with an error, the email alert still goes out.