Zapier via the Webhook channel
Zapier is not a native PulseStack channel, and we would rather say so plainly. You connect it in minutes by pointing a PulseStack Webhook at a Zapier Catch Hook. From there, every failure and recovery can trigger thousands of downstream apps.
Webhook channel included from Starter at GBP 9 per month. No card needed for the 14-day trial or the Free plan.
Catch Hook
Webhooks by Zapier
POST /hooks/catch/8842019/az7f0
{
"event": "monitor.down",
"monitor": { "name": "Orders API", "url": "https://api.acme.io/v2/orders", "type": "API" },
"error": "Down from 2/3 locations: London, New York",
"locations": [
{ "locationCode": "LHR", "city": "London", "isUp": false, "statusCode": 503, "responseMs": 8412 },
{ "locationCode": "NYC", "city": "New York", "isUp": false, "statusCode": 503, "responseMs": 8120 },
{ "locationCode": "SYD", "city": "Sydney", "isUp": true, "statusCode": 200, "responseMs": 1290 }
],
"timestamp": "2026-10-14T09:14:07.000Z"
}Next action
Create ticket, notify channel, update sheet
9
monitor types feed Zapier
2
events per incident: down and up
GBP 9
plan where Webhooks unlock
1
Catch Hook URL per Webhook contact
There is no native Zapier app to install. PulseStack talks to Zapier through the same Webhook channel that powers our custom integrations. You point a webhook at a Zapier Catch Hook, and Zapier takes it from there. It is simple, transparent and completely under your control.
In Zapier, start a new Zap and choose Webhooks by Zapier as the trigger, then select Catch Hook. Zapier generates a unique inbound URL. Copy it.
Open Alert Contacts, click Add contact, choose Webhook and paste the Catch Hook URL into Webhook URL. It is the same Webhook channel that posts to your own endpoints.
Tick the contact under Notify on failure on the monitors you care about. Failed checks are confirmed first (two of three locations, or a re-test), so you only trigger on real incidents, not one-off blips.
Map the JSON fields PulseStack sends into any Zapier action. Create a ticket, post to a channel, update a sheet, page an engineer or branch with Paths.
Every PulseStack alert arrives as structured JSON. Zapier parses it automatically, so each field is available as a token in your downstream steps without any custom code or parsing.
Because both the down and up events use the same shape, a single Zap can open and close incidents from one consistent payload.
eventmonitor.down when a monitor goes down, monitor.up when it recoversmonitorThe monitor's name, url and type (for example HTTP or HEARTBEAT)errorWhat failed, for example which locations; null on recovery for multi-location monitorsdownDurationOn recovery, how long the monitor was down; left out of monitor.down eventslocationsThe latest result from each location, with status code and response time; empty for SSL, DNS, domain expiry and heartbeat monitorstimestampISO 8601 time the alert was sentWhen the monitor comes back up, PulseStack sends a matching payload with the event set to up. Wire your Zap to detect this and resolve the incident automatically.
Example monitor.up payload
{
"event": "monitor.up",
"monitor": { "name": "Orders API", "url": "https://api.acme.io/v2/orders", "type": "API" },
"error": null,
"downDuration": "11m 26s",
"locations": [
{ "locationCode": "LHR", "city": "London", "isUp": true, "statusCode": 200, "responseMs": 182 },
{ "locationCode": "NYC", "city": "New York", "isUp": true, "statusCode": 200, "responseMs": 431 },
{ "locationCode": "SYD", "city": "Sydney", "isUp": true, "statusCode": 200, "responseMs": 1264 }
],
"timestamp": "2026-10-14T09:19:41.000Z"
}PulseStack delivers alerts through eight native channels. Zapier and Google Chat are not on this list, because they ride on top of the Webhook channel rather than being built in.
SMS alerts are included on the Team and Enterprise plans. See all integrations.
Watch pages and endpoints for downtime and wrong status codes, with response times recorded.
Confirm expected text is present, or alert when forbidden text appears.
Check that a host accepts TCP connections, from multiple locations.
Verify a specific service port is open and accepting connections.
Check status codes from your own or third-party APIs, with your own method, headers and body.
Catch silent failures in cron jobs and background workers that stop checking in.
Start a Zap a set number of days before a certificate expires (7 by default), or when it is not trusted.
Start a Zap when no record of the chosen type holds the value you expect.
Start a Zap a set number of days before a domain registration runs out (7 by default).
Route a down event into Jira, Trello, Asana or Linear through Zapier and close the ticket automatically when the matching up event arrives.
Append each event to Google Sheets or Airtable to build your own uptime ledger, then chart mean time to recovery however you like.
Notion, ClickUp and the other apps in your Zapier account become reachable the moment the payload lands in your Catch Hook. Google Chat does not need Zapier: a Webhook contact can post to the space directly, as the Google Chat guide shows.
Use Zapier Paths and Delays to notify an on-call engineer, wait, then escalate to a manager if the monitor has not recovered.
If your destination is one of the eight native channels, use it directly for the simplest setup. Reach for Zapier when you need to touch an app we do not natively support or build multi-step logic.
Start with Send test next to the Webhook contact on the Alert Contacts page. It posts a small test event to your Catch Hook straight away, and if Zapier refuses it the error reads Webhook returned, followed by the status code Zapier sent back.
The Send test request carries only event, message and timestamp, so Zapier shows no monitor fields from it. To map monitor.name, monitor.url, error or locations, let one real alert reach the hook first (for example from a test monitor pointed at a page that returns 404), then test the trigger again in Zapier and pick that request.
A Zap only runs while it is published and switched on. A copied or rebuilt Zap gets a new Catch Hook URL, so paste the new one into the Webhook contact in PulseStack™.
Zapier counts the actions your Zap performs against your Zapier plan's task limit. If runs stop, check Zap history in Zapier first; PulseStack™ sends the request either way.
Alerts go to the contacts ticked under Notify on failure (every contact if none are ticked), and only when a monitor goes down or recovers. If an alert looks wrong, see why a monitor status can be wrong.
PulseStack™ posts each alert once and does not retry, so a request Zapier could not accept at that moment is not sent again.
No. Zapier is not a one-click native app in PulseStack. It connects through the Webhook alert channel. You create a Zapier Catch Hook and paste its URL into a PulseStack Webhook contact, so every alert becomes a Zap.
Create a new Zap using Webhooks by Zapier with the Catch Hook trigger and copy the generated URL. In PulseStack™, open Alert Contacts, click Add contact, choose Webhook and paste the URL. Then tick the contact under Notify on failure on your monitors, and your alerts start flowing into Zapier.
Any of PulseStack's nine monitor types can route through the Webhook contact: HTTP, Keyword, TCP Ping, Port, API, Heartbeat, SSL certificate, DNS record and domain expiry. Assign the Webhook contact to whichever monitors you want in Zapier.
Yes. PulseStack fires on failure and again on recovery, and every failure is double-checked first so single blips are filtered out. The payload's event field (monitor.down or monitor.up) indicates which state it is, so your Zap can open and close incidents automatically.
The Webhook channel is available on paid plans starting at GBP 9 per month for Starter. Paid plans come with a 14-day trial, and annual billing saves 20 percent.
Any service without a native PulseStack integration, such as Google Chat, connects by pointing a PulseStack Webhook alert at its incoming webhook URL. PulseStack has eight native channels: Email, SMS, Slack, Microsoft Teams, Discord, PagerDuty, Telegram and Webhooks.
Start monitoring in minutes, add a Webhook channel, point it at a Zapier Catch Hook and let your alerts drive real action.