- Incoming. External tools push alerts into Warrn via webhook. Most support auto-resolve.
- Outgoing. Warrn sends notifications to your communication channels.
- Contextual. Warrn pulls data from external tools for triage, ticketing, and documentation.
Incoming (alert sources)
Receive alerts from monitoring tools. Attached to a service or team.
Grafana
Grafana Alerting webhooks. Auto-resolve supported.
Sentry
Sentry issue and error events. Auto-resolve supported.
CloudWatch SNS
CloudWatch alarms via SNS. Auto-resolve supported.
Pingdom
Pingdom uptime check alerts. Auto-resolve supported.
Coralogix
Coralogix alert webhooks. Auto-resolve supported.
MongoDB Atlas
MongoDB Atlas alert webhooks. Auto-resolve supported.
Zendesk
Zendesk ticket events.
REST API
Send alerts from any system via the API.
Outgoing (notifications)
Warrn sends alert events to your channels.Slack
Alert notifications via OAuth or webhooks.
Outgoing Webhooks
Send alert payloads to any HTTP endpoint.
Google Meet
Create war rooms for alerts and incidents.
Contextual
Warrn pulls data from these tools for triage, ticketing, and documentation.GitHub
Commits, PRs, code search, and deployments.
Jira
Create and link issues from alerts.
Confluence
Import runbooks and export post-mortems.
CloudWatch
Pull alarms and metrics via AWS credentials.
HubSpot
Customer context during incidents.
Best practices
- Use a bot account for Atlassian and Google Meet OAuth connections.
- For incoming integrations, configure both alert and resolve events in the source tool to enable auto-resolve.