Engineering on-call
Production HTTP and API monitors post to a dedicated incidents channel with a two-failure threshold, so the rota only wakes for real outages.
Slack alert channel
Connect PulseStack to Slack with a single incoming webhook URL. Every check that fails posts the monitor name, its status and the timing 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 is DOWN
api.acme-store.com
Recovered
api.acme-store.com is back up after 3m 12s
The whole setup is a copy and paste of one webhook URL. No app review, no OAuth scopes to approve.
In your Slack workspace, add an incoming webhook and pick the channel it should post to.
Slack generates a unique URL for that channel. Copy it to your clipboard.
Open your alert settings, choose Slack as the channel and paste the webhook URL in.
Select which monitors use the Slack rule and set your consecutive-failure threshold.
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 webhook payload
{
"monitor": "api.acme-store.com",
"type": "HTTP",
"status": "down",
"http_code": 503,
"started_at": "2026-07-25T09:41:07+01:00",
"consecutive_failures": 2,
"location": "London, UK"
}PulseStack formats this into a readable Slack message. The same event can also fire to a raw Webhook channel if you want to drive your own automation.
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 escalation, SMS for the emergencies. Zapier and Google Chat connect through the Webhook channel rather than as native integrations.
SMS and voice alerts are an add-on available on the Team and Enterprise plans.
Whatever you watch with PulseStack can post to Slack the moment it fails 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.
Reachability checks for hosts that answer on the network layer.
Watch a specific service port stays open and accepting.
Validate JSON endpoints, headers and expected responses.
Catch silent cron jobs and workers that stop checking in.
Detect record changes and resolution failures early.
Get warned before a domain lapses and takes you offline.
Production HTTP and API monitors post to a dedicated incidents channel with a two-failure threshold, 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, Domain Expiry and SSL-adjacent checks feed a low-noise channel that flags slow-burn risks well 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 | 10 | 60s | £15/mo |
| Pro | 50 | 60s | £39/mo |
| Team | 100 | 60s | £79/mo |
| Enterprise | 200 | 30s | £149/mo |
Slack is a native alert channel. You create a Slack incoming webhook URL for the channel you want, add it as a Slack alert contact in PulseStack, then attach that contact to your monitors. When a monitor goes down or recovers, PulseStack posts to your channel with the monitor name, status and timing.
Each post includes the monitor name, its new status and the timing of the check. Down alerts tell your channel what failed, and recovery alerts confirm when the monitor is healthy again.
No. Alerts fire only after a configurable number of consecutive failed checks, so a momentary blip will not post. You set the threshold to match how sensitive you want the channel to be.
All of them. You can route HTTP, Keyword, TCP Ping, Port, API and Heartbeat monitors, plus DNS and Domain Expiry monitors, to any Slack contact you set up.
Yes. Create a separate Slack contact for each channel, each with its own incoming webhook URL, then assign monitors to whichever contact you want. 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 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.