Alert where your team already lives.
Route incident signals from Alertum into chat, observability, and automation systems — so teams respond faster without building custom integration glue.
Google Chat
Route alerts to Google Chat spaces.
Telegram
Deliver alerts to Telegram groups or bots.
Discord
Send structured alerts to Discord channels.
Teams
Adaptive card notifications in Microsoft Teams.
Reliable incident and recovery notifications to any address.
Webhook
Push any event to your own HTTP endpoint.
Pushbullet
Push notifications to personal devices.
Pushover
Priority-based mobile push alerts.
Error intake
Every error from your server becomes an incident. Alertum ingests errors directly from your backend and turns them into incidents with service context — created, grouped, and routed through your existing notification stack with no manual triage and no separate error tracker to check.
- ·Send every error your services throw — unhandled exceptions, failed background jobs, database timeouts, third-party API failures. If your backend can report it, Alertum can ingest it.
- ·POST event payloads to your ingest endpoint with a Team API key — one HTTP call from any language or framework, no SDK required.
- ·Repeated events group into one incident by project + error group, so a burst of the same exception becomes a single incident with an event count instead of hundreds of pages.
- ·Each incident arrives with service, environment, and severity attached, and is routed through the same escalation policies as your uptime monitoring — one on-call flow for everything.
curl -X POST https://api.alertum.co/ingest/errors \
-H "Authorization: Bearer <team-api-key>" \
-d '{"message": "Database connection pool exhausted",
"project": "payments", "service": "payments-api",
"environment": "prod", "group": "db-pool", "severity": "high"}'