How to Set Up Slack Alerts with a TwoPulse Incoming Webhook
Getting downtime alerts into Slack shouldn't require a custom Slack app or a complicated OAuth install. With TwoPulse, you create one Incoming Webhook in Slack, paste the URL into Settings, and alerts for downs, reminders, and recoveries start posting to the channel you choose. This guide walks through the full setup — from creating the webhook to confirming alerts arrive where your team already works.
What You'll Need
Before you start, make sure you have:
- A Slack workspace where you can add apps (or an admin who can)
- A TwoPulse account with at least one monitored service
- Access to Dashboard → Settings in TwoPulse
That's it. No bot tokens, no Slack App submission, no developer account beyond what Slack already gives workspace members.
How Incoming Webhooks Work
A Slack Incoming Webhook is a unique HTTPS URL tied to a specific channel. When TwoPulse detects an incident (or a recovery), it sends a formatted JSON message to that URL. Slack posts it in the channel as a normal message — with the same incident details you already get by email: service name, status, latency, endpoint, consecutive failures, and links back to your dashboard.
You can add more than one webhook in TwoPulse if you want the same alerts in multiple channels (for example, #ops and #engineering).
Step 1: Create an Incoming Webhook in Slack
- Open Slack's Incoming Webhooks page: api.slack.com/messaging/webhooks
- Click Create your Slack app (or pick an existing app if you already use webhooks)
- Choose From scratch, name it something clear like "TwoPulse Alerts", and select your workspace
- In the app settings, open Incoming Webhooks and turn the feature On
- Click Add New Webhook to Workspace
- Pick the channel where you want alerts (for example
#alertsor#ops) - Click Allow
- Copy the webhook URL — it looks like
https://hooks.slack.com/services/T…/B…/…
Treat that URL like a secret. Anyone with it can post to that channel, so don't commit it to git or share it publicly.
Step 2: Add the Webhook in TwoPulse
- Sign in to TwoPulse and go to Settings
- Find the Slack card under Notification Settings
- Paste your webhook URL into the Incoming Webhooks field
- Click Add
The webhook appears in your list, enabled by default. The Slack card badge switches to Active once at least one webhook is enabled. You can add more URLs the same way if you want alerts in additional channels.
Step 3: Pause or Remove Delivery When Needed
Open the webhook list from the icon on the Slack card:
- Toggle a webhook off to pause Slack delivery without deleting the URL
- Remove a webhook if that channel should stop receiving alerts entirely
Email alerts are independent — turning Slack off does not stop email notifications, and vice versa.
What a TwoPulse Slack Alert Looks Like
Slack messages mirror the structure of TwoPulse alert emails so your team sees the same incident context wherever they look:
- Subject-style header — for example "TwoPulse Alert: API is down (HTTP 503)"
- Eyebrow — Incident / Reminder / Recovered
- Details — status, HTTP code, latency, endpoint, expected status, consecutive failures, error output when available
- Actions — buttons to open the incident log or status view in your TwoPulse dashboard
Reminder alerts use the same schedule as email reminders, so Slack stays in sync with your existing notification cadence.
Tips for a Clean Setup
- Use a dedicated channel —
#alertsor#twopulsekeeps noise out of day-to-day chat - One webhook per channel — add multiple webhooks in TwoPulse if different teams need the same alerts
- Rotate if leaked — revoke the webhook in Slack and add a new URL in TwoPulse if the old one is exposed
- Confirm threshold settings — alerts fire after consecutive failed checks reach your service's alert threshold, same as email
Troubleshooting
Alerts aren't appearing in Slack
Confirm the webhook is listed and enabled in Settings, the URL still starts with https://hooks.slack.com/services/, and the Slack app's Incoming Webhooks feature is still turned on. Also check that the monitored service is active and has crossed its alert threshold.
Slack returns an error when TwoPulse posts
The webhook may have been revoked or the channel deleted. Create a new Incoming Webhook in Slack and replace the URL in TwoPulse.
I only want Slack, not email
Keep at least one email recipient enabled for account safety, but you can disable extra teammate emails. Slack delivery is controlled separately from the email list.
Frequently Asked Questions
Do I need to build a Slack App for TwoPulse?
Not for this flow. You create a simple Incoming Webhook (Slack may walk you through a lightweight app for that webhook). TwoPulse does not need its own published Slack App or OAuth install.
Can I send alerts to more than one Slack channel?
Yes. Add one Incoming Webhook URL per channel in TwoPulse Settings. Each enabled webhook receives the same alert payload.
Will recoveries post to Slack too?
Yes. Down alerts, reminder alerts, and recovery alerts all post when Slack is configured and enabled.
Is the webhook URL safe to share with teammates?
Only with people who should be able to post to that channel. Prefer adding the URL yourself in TwoPulse rather than pasting it into a public chat.
Does this replace email alerts?
No — Slack is an additional channel. Most teams keep email for a durable record and Slack for fast in-channel visibility.
Ready to route incidents where your team already works? Get started with TwoPulse and add a Slack webhook from Settings — or log in to connect one now.
```