Get early access
Features · Alerting & Incidents · Notification Channels
Alerting & Incidents · Notification Channels

Slack · email · webhook · push,
routed per rule, per severity.

A channel is "Slack #ops". A route is "everything from prod, severity ≥ page, business hours UTC". Together they get the right person paged at the right time, without the “noisy-channel-bankruptcy” spiral.

routes
Slack #ops prod · severity ≥ page
PagerDuty prod · critical only
Discord #build build hosts · any
email digest everything · daily 08:00
webhook all events · HMAC signed
— Why this matters

A channel is where. A route is what and when.

01

Everything everywhere is the same as nothing.

Separating the destination from the rule is what lets prod criticals page and staging warnings sit in a digest.

02

The receiving system decides the format.

Slack wants blocks, Discord wants embeds, Teams wants a MessageCard and PagerDuty wants its events API. A generic JSON body helps none of them.

— What's included

Where it can send, and in what shape.

Email
Branded templates, dark mode included.
Slack and Discord
Webhook-based, formatted natively — blocks for one, severity-coloured embeds for the other.
Telegram
Through the bot API.
Generic webhook
With payload templates for HostAtlas JSON, Slack, Discord, Microsoft Teams, PagerDuty, or raw passthrough.
HMAC-SHA256 signing
Optional secret per webhook, so the receiver can verify it was us.
Test before you need it
Every channel can be verified from the UI.
Multi-channel routing
Per alert rule, so one event can page and log at once.
— Works with

Connected capabilities

Smart Alerts
Define which alerts go to which channels.
→
In-App Notifications
Bell + archive inside HostAtlas itself.
→
Webhooks
Generic outbound integration, not just for alerts.
→
SIEM Forwarding
Bulk alert stream to your SIEM.
→
— FAQ

Questions, answered honestly.

Do channels test themselves? +
Yes — periodic synthetic ping per channel. Stale channels surface a warning before you find out via a missed page.
Can I de-duplicate cross-channel? +
Yes — incident grouping is platform-wide, not per-channel. One incident, one Slack thread + one email + one push.
On-call rotation support? +
Built-in basic rotations; mature on-call (escalation policies, schedule overrides) is on the roadmap. PagerDuty integration covers it today.

Send the right alert to the right place.

Slack + email + webhook on every plan; mobile push + PagerDuty from Starter.

Get early access Back to Alerting & Incidents