Fifteen channels: chat, mobile push, on-call paging, or your own webhook. Maintenance alerts land exactly where they should.
No card required · 50 monitors free · No time limit
Alert channels — Slack, Discord, Telegram, webhooks — plus API access to wire ErrorDetector into your own systems.
Add a channel
Fifteen channels are live today — nothing here is marked “coming soon”. Every one can be tested before you rely on it, every alert fires again on recovery, and the three paging tools close their own incident when the check passes.
Webhook payload
POST https://hooks.lumen-agency.com/errordetector
{
"monitor_url": "https://checkout.acmecorp.com",
"status_code": 0,
"message": "Connection timeout after 5000 ms",
"timestamp": "2026-08-09T09:41:12Z"
}
Each feature earns its place by making the client relationship easier to protect: fewer surprises, clearer proof, and faster explanations when something changes.
Slack, Discord, Telegram, Microsoft Teams, Mattermost, Rocket.Chat and Google Chat. The self-hosted ones work against your own server, not a vendor cloud.
PagerDuty, Opsgenie and SIGNL4 open an incident when a check fails and resolve it when the check passes — so a recovery at 3am ends the page instead of leaving it open.
ntfy and Pushover reach a phone directly; extra email recipients need no app at all; and a custom webhook takes a JSON payload you control the shape of.
The alert channel picker, rebuilt here in markup rather than photographed. Downtime, SSL and keyword alerts go to every connected channel the moment a check fails, and again on recovery. All fifteen shown are live today — nothing on this screen is marked "coming soon", because nothing on it is.
Alert channels
Downtime, SSL and keyword alerts go to every connected channel the moment a check fails — and again on recovery.
Concrete moments from the feature: setup, the signal that matters, and the client-facing proof that makes maintenance feel easy and valuable.
Channels · example data
Connect once, then pick per monitor which of those channels it may wake.
Channels
4
Routing
Per monitorTelegram
Bot token and chat ID, stored encrypted
Slack / Discord
Incoming webhook URL — formatted natively for each
Custom webhook
POST JSON to any HTTPS endpoint you control
Payload · example data
A flat JSON body you can route on, or your own template if you would rather shape it.
Method
POST
Delivery
200 OKmonitor_url
"https://checkout.acmecorp.com"
event / status_code
"down" · 0
Your own template
{{monitor_url}} {{status_code}} {{message}} {{timestamp}}
Routing · example data
Downtime, failed checks and recovery are separate events, so nobody has to read the message to know which is which.
Repeat while down
Every 15 min
Escalation
After 15 mindown
Reachability failure — every channel on the monitor
issue
Keyword, API policy or certificate warning — same channels, different message
up
Sent as soon as the monitor answers again
Add the signal once, then let alerts, history, and reports build automatically.
Open the API tab in your dashboard.
A webhook URL for chat, a routing key for PagerDuty, a token pair for Pushover. Each one tells you which it wants.
Send a test message to verify everything works.
Fifteen: Slack, Discord, Telegram, Microsoft Teams, Mattermost, Rocket.Chat, Google Chat, ntfy, Pushover, PagerDuty, Opsgenie, SIGNL4, Zapier, extra email recipients, and a generic webhook. Anything not on that list can usually be reached through the generic webhook or Zapier.
Yes. PagerDuty, Opsgenie and SIGNL4 all model an open incident, so a recovery sends a resolve keyed to the same monitor rather than a second alert. Chat and push channels have nothing to close, so they simply receive the recovery message.
Yes, you can have Slack, PagerDuty, and custom webhooks all active simultaneously. Alerts are sent to all configured channels.
Webhook, Slack, Discord and Telegram integrations start on the Solo plan. The free plan covers monitoring and a status page; alerting begins on Solo.
Combine uptime, SSL, domains, incidents, alerts, teams, and reports into one maintenance workspace.
An API monitor calls one endpoint with the method, headers, JSON body and auth y…
Push-based heartbeat monitoring for backups, syncs, exports, and scheduled tasks…
A DNS monitor asks a resolver for one record type — A, AAAA, CNAME, MX or TXT — …
A blacklist monitor asks the public DNS blocklists whether an IP address has bee…
Track every client domain expiry date and receive timely warnings before a renew…
Automatic incident detection, response notes, status updates, and reports so cli…
A keyword monitor loads one URL and searches the HTML the server returned for a …
Monitor SSL certificates and receive warnings well before they expire, so client…
Give maintenance clients transparency with a professional, automatically updated…
Invite your team, assign roles, and collaborate on monitoring, alerts, and repor…
Start with webhook monitoring and build client trust with real data. Free, no credit card required.
Create free accountNo card required · 50 monitors free · No time limit