Slack
ChatIncident updates in channels
Ecosystem and Connectivity
Integrations, Routing, and Error Intake
Alertum integrates with operational chat tools, webhook endpoints, and api platforms so alerts and incident context can reach the right surfaces without adding custom glue code to every team.
Integration Catalog
Native Connectors
Google Chat
ChatTeam space notifications
Telegram
ChatMobile-first alert delivery
Discord
ChatOperational notification rooms
Teams
ChatMicrosoft ecosystem alerting
Webhook
WebhookCustom event routing
Splunk
ApiEvent analytics and search
Pushbullet
ChatDevice and channel pushes
Pushover
ChatReal-time app notifications
New Relic
ApiAlert ingestion via webhook
Error Intake Contract
Payload Fields
Error Intake accepts contextual fields that map application failures directly into incident records.
status (open | acknowledge | resolved | reopened)
message
project
service
environment
group
severity (Critical | High | Medium | Low)
details (structured metadata)
Escalation Channels
How Notifications Leave Alertum
Policy levels can notify through multiple channels, supporting both synchronous team chat and strict incident paging workflows.
Email
Slack
PagerDuty
Webhook
Sms
Phone Call
Operational Note
The most reliable pattern is to combine one human-facing chat channel with one strict escalation channel (for example Slack + PagerDuty or Teams + Sms) on critical policy levels.
Connect Signal Sources Before Incidents Start
Strong operations depends on integration readiness. Define channels and ingestion paths ahead of incidents so routing is automatic when service health degrades.