Slack Integration: Alerts Straight to Your Channel
Availability monitoring with second-level precision — delivered to the team that needs to act on it.
Set Up Your Slack Webhook in 3 Minutes
Pulsely pushes every status change through a Slack Incoming Webhook. No OAuth dance, no app review — just a URL you paste into your workspace settings.
1. Enable Incoming Webhooks
Open api.slack.com/apps, click Manage on your Pulsely app (or create one called "Pulsely Uptime"), then navigate to Incoming Webhooks and toggle it on.
2. Add a New Webhook
Click Add New Webhook to Workspace. Choose the default channel — for example #ops-alerts — and confirm. Slack will display a URL starting with https://hooks.slack.com/services/T…/B…/….
3. Paste Into Pulsely
Go to Settings → Integrations → Slack in your Pulsely dashboard. Paste the webhook URL, give the connection a label like "Production Alerts," and click Test Connection. A verification message appears in your channel within seconds.
Tip: Create separate webhooks for different severity levels. Use one webhook pointing to #incidents-critical for downtime and another to #incidents-warning for latency spikes. Pulsely lets you assign webhooks per-check or per-alert-rule.
What Your Team Sees in Slack
Every alert is a rich, color-coded message with actionable context — not a bare URL. Here is how Pulsely structures notifications so your on-call engineer can triage without leaving Slack.
Color-Coded Severity
Red border for Down events, amber for Degraded, green for Recovered. The border color is set via Slack's mrkdwn_in attachment format so it's visible even in dark mode.
Key Metrics in the Preview
Each message includes the monitored endpoint (e.g., api.pulsely.io), last successful response time (e.g., 142 ms), current response time (4.2 s), and incident duration (12 min). No need to open the dashboard to understand the situation.
Mentions & Threads
Critical alerts @mention your on-call rotation (e.g., @oncall-week-23). Every recovery post replies in a thread to the original incident message, keeping the channel clean and preserving the full timeline.
Channel Strategy by Incident Type
Teams at companies like Meridian Pay and CloudHaven use a three-channel model with Pulsely:
- #incidents-critical — full downtime, HTTP 5xx errors, SSL expiry < 24 h. Triggers PagerDuty escalation.
- #incidents-warning — response time > 2 s, certificate expiry < 7 days, DNS propagation delays.
- #incidents-info — recovery confirmations, scheduled maintenance windows, monthly uptime reports.
Each channel gets its own webhook URL in Pulsely. You assign the right webhook per check or per alert rule, so the right people see the right noise at the right time.