Engineering on-call
Production HTTP and API monitors post to a dedicated incidents channel. Failures are re-tested and confirmed from two locations first, so the rota only wakes for real outages.
Slack alert channel
Connect PulseStack™ to Slack with a single incoming webhook URL. Every confirmed failure posts the monitor name, its type, the error and the failing locations straight into the channel your team already watches. Recovery messages follow automatically.
Native channel on every plan, including Free. No card required to start a 14-day trial.
🔴 Monitor DOWN: Acme API
Type: HTTP
Error: Down from 2/3 locations: London, New York
Failing: London, New York
Passing: Sydney
Time: 2026-07-25T08:41:07.000Z
09:44
🟢 Monitor RECOVERED: Acme API
Type: HTTP
Status: Back online (was down 3m 12s)
All 3 locations reporting UP
Time: 2026-07-25T08:44:19.000Z
Example. Slack shows the name and icon of the Slack app that owns your webhook.
The whole setup is one webhook URL copied from Slack into PulseStack™. There is no PulseStack™ app to install from the Slack Marketplace.
In Slack's app settings (api.slack.com/apps), create an app for your workspace, switch on Incoming Webhooks, add a new webhook and pick the channel it should post to.
Slack generates a URL for that channel that starts https://hooks.slack.com/services/. Copy it to your clipboard.
In the dashboard, open Alert Contacts, click Add contact, choose Slack and paste the URL into Webhook URL. Then click Send test.
In each monitor's settings, tick the Slack contact under Notify on failure. A monitor with no contacts ticked alerts every contact.
A PulseStack alert is built to be read at a glance from your phone. No jargon, no dashboard hunt, just the facts your team needs to decide whether to jump in.
Example request body sent to your Slack webhook
POST https://hooks.slack.com/services/T000/B000/XXXX
Content-Type: application/json
{
"text": "🔴 *Monitor DOWN*: Acme API\nType: HTTP\nError: Down from 2/3 locations: London, New York\nFailing: London, New York\nPassing: Sydney\nTime: 2026-07-25T08:41:07.000Z"
}Slack shows the text between asterisks in bold. If you want structured JSON for your own automation (event, monitor, error, per-location status codes and response times), add a Webhook contact as well.
Email piles up and gets missed. A message in the right Slack channel gets seen. PulseStack meets your engineers where they are during the working day.
Incidents surface in the channel your on-call rota is already watching, not buried in an inbox.
Everyone in the channel sees the same alert and the same recovery, so nobody double-acts.
Teams reply in a thread under the alert to coordinate, keeping the whole incident in one place.
Send the same incident to as many channels as you like. Slack for the team, PagerDuty for the on-call rota, SMS for the emergencies. Zapier and Google Chat connect through the Webhook channel rather than as native integrations.
SMS alerts are included on the Team and Enterprise plans. See all integrations.
Whatever you watch with PulseStack, including SSL certificate, DNS record and domain expiry monitors, can post to Slack as soon as a failure is confirmed and again when it recovers.
Uptime, status codes and response times for any web endpoint.
Confirm a phrase is present or absent in the page body.
TCP connection checks to any host and port.
Watch a specific service port stays open and accepting.
Send your method, headers and body, and check the expected status code.
Catch silent cron jobs and workers that stop checking in.
Alerts a set number of days before expiry (7 by default), or when the certificate is not trusted.
Alerts when no record of the chosen type contains the value you expect.
Alerts a set number of days before the registration runs out (7 by default).
Production HTTP and API monitors post to a dedicated incidents channel. Failures are re-tested and confirmed from two locations first, so the rota only wakes for real outages.
One PulseStack account, one Slack channel per client. Each client's monitors route to their own webhook so nothing gets crossed.
DNS record, domain expiry and SSL certificate monitors feed a low-noise channel that flags slow-burn risks before they cause an outage.
Start free and keep Slack alerts as you grow. Every paid tier begins with a 14-day trial.
| Plan | Monitors | Fastest interval | Price |
|---|---|---|---|
| Free | 5 (HTTP only) | 5 min | £0 |
| Starter | 50 | 60s | £9/mo |
| Pro | 150 | 30s | £19/mo |
| Team | 500 | 30s | £39/mo |
| Enterprise | 2,000 | 30s | £99/mo |
Start with Send test next to the contact on the Alert Contacts page. It posts a test message to the channel straight away, and if Slack refuses it the error shows the status code Slack returned, for example Slack returned 404.
The form only accepts URLs that start https://hooks.slack.com. Copy the URL from your Slack app's Incoming Webhooks page, not a channel link or a bot token.
Slack answers 404 when a webhook has been disabled or removed, for example after the app was uninstalled, and 410 when the channel has been archived. Add a new webhook in Slack and replace the contact.
If a monitor has any contacts ticked under Notify on failure, only those are alerted. Tick the Slack contact, or untick everything so the monitor alerts every contact.
Messages are sent when a monitor goes down or recovers, not on every check, so a monitor that was already down when you added Slack posts nothing until it recovers. If an alert you did get looks wrong, see why a monitor status can be wrong.
PulseStack™ posts each alert once and does not retry, so a message Slack rejected or never received at that moment is not sent again.
Slack is a native alert channel. You create an incoming webhook for the Slack channel you want, add its URL in PulseStack™ under Alert Contacts as a Slack contact, then tick that contact under Notify on failure on your monitors (a monitor with nothing ticked alerts every contact). When a monitor goes down or recovers, PulseStack™ posts a message to the channel.
Each alert is a short text message: the monitor name, its type, the error (or, on recovery, how long it was down), the failing and passing check locations for multi-location monitors, and the time in UTC. Down alerts start with a red circle and recoveries with a green one. The monitor URL is not included, so give monitors names your team will recognise.
No. PulseStack™ posts when a monitor changes state, once when it goes down and once when it recovers, not on every failed check. HTTP, keyword, API, ping and port monitors are only marked down when at least two of the three locations (London, New York and Sydney) fail, and SSL, DNS, domain expiry and heartbeat checks are re-tested 3 seconds after a failure. There is no consecutive-failure setting to tune.
All nine: HTTP(S), Keyword, TCP Ping, Port, API, Heartbeat, SSL certificate, DNS record and Domain expiry. SSL, DNS, domain expiry and heartbeat alerts carry the check's own message instead of location lines.
Yes. Create a separate Slack contact for each channel, each with its own incoming webhook URL, then tick whichever contact each monitor should use. Production alerts can go to your incident channel while staging goes somewhere quieter.
Slack is one of eight native alert channels available in PulseStack. The free plan covers 5 monitors with HTTP checks and email alerts, and paid plans come with a 14-day trial so you can set up Slack alerting before you commit.
Wire up Slack in minutes and let PulseStack post every outage and recovery to the channel that matters. Free to start, no card required.