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 £15 per month. 14-day trial. No card on Free.
Catch Hook
Webhooks by Zapier
POST /hooks/catch/8842019/az7f0
{
"monitor": "api.acme.io /v2/orders",
"type": "api",
"event": "down",
"status_code": 503,
"location": "London, UK",
"response_ms": 15000,
"failures": 2,
"timestamp": "2026-07-25T09:14:07Z"
}Next action
Create ticket, notify channel, update sheet
8
monitor types feed Zapier
2
events per incident: down and up
£15
plan where Webhooks unlock
1
webhook, unlimited Zaps
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 Alerting, add a new Webhook channel and paste the Catch Hook URL as the destination. This is the same reliable Webhook channel that powers our custom integrations.
Assign the webhook to the monitors you care about and set your consecutive-failure threshold so you only trigger on confirmed 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.
monitorHuman-readable name of the monitor that changed statetypeOne of the eight monitor types, for example http or heartbeateventdown on failure, up on recoverystatus_codeHTTP status returned, when applicablelocationThe checking location that observed the failureresponse_msResponse time in milliseconds at the moment of the checkfailuresConsecutive failure count that crossed your thresholdtimestampISO 8601 timestamp of the eventWhen 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.
{
"monitor": "api.acme.io /v2/orders",
"type": "api",
"event": "up",
"status_code": 200,
"location": "London, UK",
"response_ms": 214,
"failures": 0,
"timestamp": "2026-07-25T09:19:41Z"
}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 and voice are available as an add-on on the Team and Enterprise plans.
Watch pages and endpoints for downtime, slow responses and wrong status codes.
Confirm expected text is present, or alert when forbidden text appears.
Check that a host answers at the network level from multiple locations.
Verify a specific service port is open and accepting connections.
Validate JSON responses and status codes from your own or third-party APIs.
Catch silent failures in cron jobs and background workers that stop checking in.
Detect record changes, resolution failures and unexpected propagation.
Get ahead of a lapsing domain long before it takes your site offline.
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.
Google Chat, Notion, ClickUp and thousands of others become reachable the moment the payload lands in your Catch Hook.
Use Zapier Paths and Delays to notify an on-call engineer, wait, then escalate to a manager if the failure count keeps climbing.
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.
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, copy the generated URL, then add a Webhook contact in PulseStack and paste that URL as the destination. Assign the contact to your monitors and your alerts start flowing into Zapier.
Any of PulseStack's eight monitor types can route through the Webhook contact: HTTP, Keyword, TCP Ping, Port, API, Heartbeat, DNS and Domain Expiry. Assign the Webhook contact to whichever monitors you want in Zapier.
Yes. PulseStack fires on failure and again on recovery, after a configurable consecutive-failure threshold so single blips are filtered out. The payload indicates which state it is, so your Zap can open and close incidents automatically.
The Webhook channel is available on paid plans starting at £15 per month for Starter, which includes all alert types. 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.