Slack Integration

Availability monitoring without blind spots — get real-time uptime alerts, incident summaries, and recovery notifications delivered straight to your Slack channels.

Connect UptimeGuard to Slack in 3 Steps

No webhooks to configure manually. No token management. Install the official UptimeGuard app, pick a channel, and start receiving alerts within 60 seconds.

Step 1

Add the UptimeGuard App

Open Settings & More → Apps in Slack, search for "UptimeGuard," and click Add to Slack. The app requests only Channels: Read and Messages: Write scopes — nothing more. Confirm the OAuth prompt to authorize the connection between your workspace and UptimeGuard.

Step 2

Select Your Alert Channel

After installation, the UptimeGuard bot posts a setup message in #general by default. Run /uptimeguard setup in any channel to designate it as your alert destination. You can assign one channel per monitoring project, or route all alerts through a single #ops-alerts channel.

Step 3

Configure @here Mentions

In your UptimeGuard dashboard, open Project → Integrations → Slack and toggle "Mention @here on critical alerts." When enabled, every P0 incident — such as an SSL certificate expiring within 24 hours or your API returning 5xx errors for more than 3 consecutive checks — will include an @here tag so the entire channel is notified instantly.

Channel Routing & Alert Policies

Keep your Slack workspace organized by mapping alert severity to the right channels. UptimeGuard lets you define per-project routing rules so your engineering team sees only what matters.

Critical Alerts → #incidents

Service down, DNS resolution failures, and TLS certificate expirations route to your primary incident channel. These messages include the affected endpoint, last known status, and a deep link to the UptimeGuard incident timeline. Example: "🔴 api.example.com — HTTP 503 for 120 s — [View Timeline]"

Warnings → #monitoring-warnings

Elevated response times (above your configured threshold, e.g., >2 s for an API endpoint), intermittent 4xx spikes, or disk-usage warnings from your agent-based checks go to a dedicated warnings channel. No @here mention — just a clear, timestamped message for async review.

Daily Digest → #uptime-digest

Opt in to a daily summary at 08:00 UTC that lists every check's uptime percentage, mean response time, and any resolved incidents. Messages look like: "✅ dashboard.example.com — 99.97 % uptime, avg 340 ms (24 h)". Disable or reschedule from the Integrations panel anytime.

Frequently Asked Questions

Can I connect multiple Slack workspaces?

Yes. Each UptimeGuard project can link to one Slack workspace, but you can create multiple projects (e.g., "Production," "Staging") and connect each to a different workspace. Teams at companies like Meridian Health and NovaPay use this to separate internal ops alerts from partner-facing status updates.

What happens if the Slack connection drops?

UptimeGuard queues up to 500 Slack messages locally and retries delivery with exponential backoff for up to 6 hours. If the connection is still unavailable after that window, you'll receive a fallback email to the project's primary contact (e.g., ops@example.com) with a condensed incident report.

Do I need a Slack admin to install the app?

Only if your workspace enforces Custom Integration Restrictions in the Slack Admin settings. If restrictions are in place, a workspace owner must approve the UptimeGuard app from the Approved Integrations list. Otherwise, any member with App Installer permissions can add it.

Can I silence alerts during maintenance windows?

Absolutely. Schedule a maintenance window from the UptimeGuard dashboard (e.g., June 14, 02:00–04:00 UTC), and all Slack alerts for the affected checks are suppressed for that period. A single notice posts to your channel: "⏸️ Maintenance window active for api.example.com until 04:00 UTC."

Still have questions? Email support@uptimeguard.io or start a chat from the dashboard. Our team typically responds within 15 minutes during business hours (08:00–18:00 CET).