Alert integrations that page the right person.
12 channels, one alert engine — the same confirmed incident can go to a chat room, a pager rotation, a phone or an endpoint you wrote yourself. Eight of them carry a signed acknowledge link that pauses the escalation ladder without a login.
Team chat
Four rooms, one setup step: each takes a single incoming webhook URL and the alert lands where your on-call people already have a tab open.
Slack
Team chatAlerts post as a Block Kit card carrying the priority and the monitor type. Grouped incidents add an Acknowledge incident link to the same card. A send that fails is retried once, two seconds later.
Microsoft Teams
Team chatBuilt for the Power Automate Workflows webhook that replaced Office 365 connectors. Alerts render as an Adaptive Card with the monitor, the priority and the type; grouped incidents add an Acknowledge incident button.
Discord
Team chatOne channel webhook from your server settings. For infrastructure teams, OSS projects and game backends whose incident chatter happens in Discord, not Slack.
Mattermost
Team chatThe same incoming-webhook setup as Slack, pointed at your Mattermost server, so the alert text lands on the chat infrastructure you already run.
Mobile messaging
Reach a phone without asking anyone to install an app. Both channels send through Uptimia's own bot and business number, so you supply one identifier and nothing else.
Telegram
Mobile messagingAdd @uptimia_bot to a channel or group and paste the chat ID. There is no bot to register and no token to rotate.
One field: the number. Alerts go out from Uptimia's WhatsApp Business account using Meta-approved templates, which is why there is nothing to connect.
Text messages
Two ways to put an SMS on someone's lock screen: out of the allowance in your plan, or through your own Twilio account and sender number.
SMS
Text messagesText alerts sent from Uptimia's own gateway, drawn from the monthly SMS allowance in your plan — 50 messages on the entry plan, more above it. Nothing to connect.
Twilio
Text messagesBring your own Twilio account: your sender number, your rates, any country Twilio reaches — and it never touches the SMS allowance in your plan.
Incident response
For teams who already decided who is on call this week, and want the alert to enter that system rather than compete with it.
Customer updates
Publish the incident where customers already look for it, instead of answering the same question forty times in the inbox.
The channel nobody has to be onboarded onto. A contact is an address; there is no integration to connect first.
Developer
One JSON POST to a URL you control, for the routing you would otherwise build against our API by hand.
Add once, route per monitor
A channel is configured once on the account, then attached to monitors as a contact. All 12 monitor types feed the same engine — uptime, transactions, page speed, RUM, SSL, domains, malware, servers, heartbeats, blacklists, DNS and API checks.
-
1
Connect the channel
Paste the webhook URL, routing key or number under Integrations. Most channels are a single field; Twilio takes four and Statuspage takes two, plus an optional component ID.
-
2
Send a test alert
The Test action pushes a real message through the integration, so you learn it lands in the right room before an incident is riding on it.
-
3
Attach it as a contact
A contact pairs a channel with an owner. Pick contacts per monitor, or hand the monitor to an escalation policy and let the ladder decide who is pulled in next.
-
4
Cut the noise
Set an alert delay, merge a storm of incidents into one grouped message, and let maintenance windows hold alerts while you deploy.
Your tool is not listed
The webhook posts the same JSON to any endpoint that speaks HTTP, which covers most of the routing you would otherwise build by hand. If you would rather have it native, tell us which one and it goes on the list.
Try it on your own site.
You'll know in a minute.
Free for 30 days. No credit card. Full platform during your trial — every engine, every region, every channel.