April 10, 2026
Set Up Alert Channels in Uptrack — Email, Slack, Discord, and Telegram
Your monitors are running. Every 30 seconds, Uptrack checks your sites and APIs. But what happens when something goes down at 3 AM and nobody is watching the dashboard? That is where alert channels come in.
Why alerts matter
Dashboards are reactive. You have to open them, look at them, and interpret them. Alerts are proactive — they come to you the moment something needs attention.
You cannot stare at a dashboard 24 hours a day. Your team is building features, answering support tickets, or sleeping. Without alerts, downtime goes unnoticed until a customer complains — or worse, until revenue is already lost.
Uptrack supports five alert channel types: Email, Slack, Discord, Telegram, and Webhooks. Each one takes under two minutes to set up. Here is how.
Email alerts
Email is the simplest alert channel. No integrations, no OAuth, no bots. Just an email address.
Go to Dashboard → Alerts
Open your alert channels page and click "Add Channel".
Select "Email" as the channel type
Enter the email address where you want alerts delivered. This can be your personal inbox, a shared team inbox, or a distribution list.
Save and test
Click save, then send a test alert to confirm delivery. You should see it in your inbox within seconds.
Check your spam folder. Some email providers may route the first alert to junk. If that happens, mark it as "not spam" so future alerts land in your inbox. Alerts are sent from [email protected] — add it to your contacts to be safe.
Slack alerts
Slack is where most teams already live. Uptrack posts alerts directly into a Slack channel of your choice — no webhooks to configure manually.
Click "Connect Slack"
On your Dashboard → Alerts page, click the "Connect Slack" button. This starts an OAuth flow — you will be asked to authorize Uptrack in your Slack workspace.
Pick a channel
Choose which Slack channel should receive alerts. A dedicated #monitoring or #alerts channel works well so alerts do not get lost in general conversation.
Done
That is it. When a monitor goes down or recovers, Uptrack posts a message with the monitor name, current status, and response time.
Want to check monitor status directly from Slack? See our Slack slash commands guide for advanced usage like /uptrack status.
Discord alerts
If your team uses Discord — whether for a dev community, a game studio, or an internal server — Uptrack integrates with one click.
Click "Connect Discord"
On your Dashboard → Alerts page, click "Connect Discord". You will go through Discord's OAuth flow to authorize Uptrack.
Select your server and channel
Pick the Discord server and text channel where alerts should appear. You need "Manage Webhooks" permission on the server to complete this step.
Rich embeds, automatically
Alerts arrive as rich embeds with color-coded status — red for down, green for recovered. Each embed includes the monitor name, URL, response time, and timestamp so your team gets full context at a glance.
Telegram alerts
Telegram is ideal for personal, mobile-first alerts. Your phone buzzes the moment a monitor goes down. Uptrack supports two setups: personal DMs and group channels.
Option A: Personal DM
On your Dashboard → Alerts page, click "Connect Telegram".
This opens a link to @UptrackAppBot in Telegram. Press Start to begin the conversation.
Uptrack auto-detects the connection via polling. Within a few seconds, your alert channel will show as connected. Alerts go directly to your Telegram DMs.
Option B: Group or Channel
Add @UptrackAppBot to your Telegram group or channel.
In the group, send /connect CODE where CODE is the connection code shown on your Uptrack dashboard.
Polling auto-detects the connection. Alerts will now be posted to the group for everyone to see.
Webhook alerts
Webhooks let you send alert data anywhere. If a service accepts HTTP POST requests, you can connect it to Uptrack.
Add a Webhook channel
Go to Dashboard → Alerts, click "Add Channel", and select "Webhook" as the type.
Paste your endpoint URL
Enter the URL where Uptrack should send alert data. Each alert sends a JSON payload with the monitor name, URL, status, response time, and timestamp.
Use it with anything
Webhooks work with PagerDuty, Opsgenie, n8n, Zapier, or any custom integration you build. If you can receive a POST request, you can receive Uptrack alerts.
Example JSON payload
{
"event": "monitor.down",
"monitor": {
"name": "API Production",
"url": "https://api.example.com/health",
"status": "down",
"responseTime": null
},
"timestamp": "2026-04-10T14:32:00Z"
}Which channel for what situation
Different channels serve different purposes. Here is how to think about it:
Slack / Discord — Team awareness
Best for non-urgent visibility. Your whole team sees when something goes down and when it recovers. Great for shared context during incidents.
Email — On-call engineer, audit trail
Email provides a searchable record of every alert. Use it for the on-call engineer or for compliance where you need a paper trail.
Telegram — Personal mobile alerts
Telegram notifications hit your phone instantly. Ideal for the person who needs to know right now, especially outside working hours.
Webhook — Automation, ticketing systems
Trigger automated workflows: create a Jira ticket, page someone via PagerDuty, run a restart script via n8n, or log the event to your own database.
Use multiple channels for critical monitors. Your production API should not rely on a single notification path. Pair Slack for team awareness with Telegram for the on-call engineer and a webhook for your incident management tool.
Assign channels to monitors
Creating alert channels is step one. Step two is telling each monitor which channels to use.
Open monitor settings
Go to any monitor in your dashboard and open its settings page.
Select alert channels
Under the "Alert Channels" section, check the channels you want to notify when this monitor goes down or recovers. Each monitor can use multiple channels.
Save
Save the monitor settings. From now on, this monitor will alert through every channel you selected. You can update these assignments at any time without pausing the monitor.
A common pattern: use Slack for all monitors (team visibility), add Telegram only for production-critical monitors (immediate personal alert), and attach a webhook to monitors that need automated incident response.
Start getting alerts in under 2 minutes
50 free monitors with alerts on every plan — Email, Slack, Discord, Telegram. No credit card required.
Get Started Free