---
title: Zapier Integration for Uptime Monitoring
description: Trigger any Zapier workflow from a confirmed downtime incident, using a flattened payload built for Zapier's field mapping.
canonical: https://watchfor.io/integrations/zapier
---

[← All alert channels](/integrations)

# Start any Zapier workflow from a confirmed incident

Zapier is how a lot of teams connect monitoring to the rest of their tooling — a row in a spreadsheet, a ticket, a message somewhere we do not integrate with directly. The catch with most webhook integrations is nested JSON, which Zapier maps badly. Ours sends a flattened payload for exactly this reason.

[Start free](/auth/sign-up)[Setup guide](/docs/notifications/webhooks)

## Setting it up

Catch Hook webhook with a flattened payload .

- 1 In Zapier, create a Zap with a 'Webhooks by Zapier — Catch Hook' trigger and copy the URL.
- 2 Add it in Alerting → Channels & contacts → New channel → Zapier.
- 3 Send a test so Zapier can learn the fields, then build the rest of the Zap.

The full procedure, including every optional field, is in the [setup guide](/docs/notifications/webhooks).

## What the alert looks like in Zapier

A flat set of fields — incident id, monitor, target, severity, state, diagnosis, expected, detected, locations, timestamps — each mappable directly in Zapier without digging into nested objects.

## Specific to Zapier

- Flattened payload, because Zapier's field mapping struggles with nesting.
- Same confirmed-incident trigger as every other channel, so Zaps do not fire on a single blip.
- Send a test first and Zapier learns every field.

## True of every channel

- Alerts fire on confirmed incidents, not on a single failed check, so one blip from one probe does not wake anyone.
- During a storm, several incidents inside the grouping window arrive as one summary rather than as twenty separate messages.
- Recovery closes the same thread it opened, with the outage duration attached.
- Every channel is on every plan, including the free one. There is no per-channel upsell.

## Questions people ask

Why a separate Zapier channel rather than a plain webhook? The payload shape. Zapier maps flat fields well and nested JSON poorly, so the Zapier channel sends a flattened version of the same data.

Will a Zap fire on every failed check? No. The trigger is a confirmed incident, the same threshold as every other channel, so automations do not run on a single timeout.

What can I build with it? Anything Zapier reaches — a ticket in your tracker, a row in a sheet for post-incident review, a message in a tool we do not integrate with directly.

## Wire it up in a few minutes

15 monitors free, every alert channel included, no card required.

[Start free](/auth/sign-up)[See all channels](/integrations)

Slack, Microsoft Teams, Discord, Telegram, Google Chat, Mattermost, Rocket.Chat, PagerDuty, Opsgenie, ntfy, Gotify, Pushover, Pushbullet and Zapier names and logos are trademarks of their respective owners, shown only to indicate that WatchFor can send alerts to these services. WatchFor is not affiliated with, sponsored or endorsed by them. Gotify logo by the Gotify project, CC BY 4.0.

---

Canonical page: https://watchfor.io/integrations/zapier · Site guide: https://watchfor.io/llms.txt