PingChange LogoPingChange
Sign inStart monitoring

Automation channels

Zapier, Make, n8n, and Google Sheets—route PingChange alerts into workflows and spreadsheets.

Available on paid plans that include automations (Zapier, Make, n8n) and/or Google Sheets—check your subscription.

Automation channels turn each detected change into an event your stack can consume: trigger a workflow, append a row to a spreadsheet, open a ticket, or fan out to other systems.

They use the same channel model as email or Slack: create the integration under Dashboard → Channels, then link it to the monitors that should feed it.

Svix-powered delivery — Zapier, Make, and n8n channels are delivered via Svix, which adds automatic retries, delivery history, and signed request headers. Your endpoint receives the same JSON payload as before, plus Svix envelope headers (svix-id, svix-timestamp, svix-signature) that you can use to verify authenticity.

Zapier

Good for: no-code combinations ("when PingChange fires → create row / notify / post").

Setup

  1. In Zapier, start a Zap whose trigger is Webhooks by Zapier → Catch Hook (or the PingChange app if published—hooks are the universal pattern).
  2. Copy the webhook URL Zapier shows.
  3. In PingChange: Dashboard → Channels → Zapier.
  4. Integration name — label for you (for example Pricing alerts Zap).
  5. Webhook URL — paste from Zapier.
  6. Throttle rate (optional) — max events per second PingChange will deliver to this endpoint (1–1000).
  7. Save, run a test from Zapier, then trigger a sample from PingChange if available.

What Zapier receives — Each change sends one event your Zap can map: monitor name and URL, when the change was detected, a unified message with the summary (and any AI text your plan includes), keywords, link to the full diff in PingChange, and sometimes a screenshot URL.

Request headers — Zapier also receives svix-id, svix-timestamp, and svix-signature headers on every request. You can use these to verify the payload came from PingChange.

Make (Integromat)

Good for: multi-step scenarios with branches, retries, and data stores.

Setup

  1. In Make, add a Custom webhook module as the first step and copy the URL.
  2. In PingChange: Dashboard → Channels → Make.
  3. Integration name — label in PingChange.
  4. Webhook URL — paste from Make.
  5. API key (optional) — if Make should send a header PingChange echoes for your scenario; only fill this if your team uses that pattern.
  6. Throttle rate (optional) — max events per second (1–1000).
  7. Save and run Make's determine data structure using a test ping.

What Make receives — The same practical fields as Zapier: enough to route, filter, and open the dashboard link without copying the raw diff twice. Svix headers (svix-id, svix-timestamp, svix-signature) are included for signature verification.

n8n

Good for: self-hosted or technical teams that want full control in n8n.

Setup

  1. In n8n, create a workflow whose entry is a Webhook node set to POST, then activate and copy the production URL.
  2. In PingChange: Dashboard → Channels → n8n.
  3. Integration name — label in PingChange.
  4. Webhook URL — paste from n8n.
  5. Header name / Header value (optional) — e.g. a shared secret your n8n workflow checks.
  6. Throttle rate (optional) — max events per second (1–1000).
  7. Save and execute the workflow once using PingChange's test tools if available.

What n8n receives — One POST per change with monitor metadata, timestamps, the unified alert text, optional keywords, dashboard link, and screenshot link when present. Svix headers are included for request verification.

Verifying Svix signatures

If you want to confirm that requests come from PingChange, verify the svix-signature header:

import { Webhook } from "svix"

const wh = new Webhook(SVIX_SIGNING_SECRET) // your endpoint's signing secret
wh.verify(rawBody, {
  "svix-id": req.headers["svix-id"],
  "svix-timestamp": req.headers["svix-timestamp"],
  "svix-signature": req.headers["svix-signature"],
})

The signing secret for your endpoint is available in the PingChange channel settings.

Design tips

  • Prefer one automation per severity or SLA so duplicate routing does not spam multiple workflows for the same change.
  • Pair automations with RSS or MCP only when each path has a distinct job (pull vs push).
  • Use the throttle rate field to protect downstream systems that have their own rate limits.