Notification Channels
Every alert provider OpsKitty supports and what you need to configure each one.
- Email (all plans)
- Enter one or more email addresses. Alerts and recovery notifications are sent to all listed addresses. Supports team aliases (e.g., ops@yourcompany.com).
- Slack (Launch+)
- Requires an Incoming Webhook URL. Create one in your Slack workspace under Apps → Webhooks. Alerts appear as formatted messages with endpoint name, URL, failure reason, and timestamp.
- Discord (Launch+)
- Requires a Discord Webhook URL from a channel's settings (Integrations → Webhooks). Alerts appear as embeds with color coding — red for down, green for resolved.
- PagerDuty (Growth+)
- Requires a PagerDuty Events API v2 Integration Key. OpsKitty sends trigger events when alerts fire and resolve events when they recover. Incidents appear in PagerDuty with full endpoint context.
- Microsoft Teams (Growth+)
- Requires an Incoming Webhook URL from a Teams channel (More options → Connectors → Incoming Webhook). Alerts appear as Adaptive Cards with status details.
- Telegram (Growth+)
- Requires a Telegram Bot Token and Chat ID. Create a bot via @BotFather, add it to your group, and enter the bot token and the group's chat ID.
- Webhook (Pro+)
- OpsKitty POSTs a JSON payload to any HTTPS URL when an alert fires or resolves. Useful for custom integrations, ticketing systems, or runbook automation. See the Webhooks page for the payload schema.
- Twilio SMS (Pro+)
- Requires a Twilio Account SID, Auth Token, and a Twilio phone number. Sends SMS alerts to one or more phone numbers.
- OpsGenie (Pro+)
- Requires an OpsGenie API key. OpsKitty creates and closes OpsGenie alerts automatically as endpoints go down and recover.