Notification Integrations
Send incident alerts where your team already works — email for records, Telegram for mobile push, Slack for team channels, webhooks for automation. Route different monitors to different channels so production, staging, and dev alerts never mix.
Channels by plan
| Channel | Echo (Free) | Pulse | Wave |
|---|---|---|---|
Email | 10/day | 50/day | 200/day |
Telegram | 1 channel | 2 channels | 10 channels |
Slack | 2 channels | 10 channels | |
Webhook | 2 channels | 10 channels |
Available on all plans. Email is the default channel for every account, and can be toggled per monitor the same as Telegram, Slack, or Webhook. Route incidents to email for some monitors and to chat for others.
- Echo: 10 email alerts per day
- Pulse: 50 email alerts per day, recovery email alerts
- Wave: 200 email alerts per day, recovery email alerts
Telegram
Available on all plans. Create a Telegram bot via @BotFather, then paste the bot token and target chat ID into upsonar. Each Telegram channel is independent — route different monitors to different chats.
- Echo: 1 Telegram channel
- Pulse: 2 Telegram channels
- Wave: 10 Telegram channels
Slack
Available on Pulse and Wave. Post incident alerts directly into any Slack channel using a Slack Incoming Webhook. Teams use Slack for production alerts — keep incident context in the same thread your team is already discussing.
- Pulse: 2 Slack channels — cover dev and production separately
- Wave: 10 Slack channels — route per environment, service, or team
- Per-monitor routing — Slack for production, email for staging
Webhook
Available on Pulse and Wave. Send a JSON POST with the full incident payload to any HTTPS endpoint. Works with PagerDuty, Opsgenie, Discord, Microsoft Teams, or your own internal systems.
- Pulse: 2 webhook endpoints
- Wave: 10 webhook endpoints
- Retries on transient 5xx failures