Page DeltasPage Deltas

Guide

How to automate website change alerts with Zapier or n8n

Route Page Deltas change webhooks into Zapier or n8n, then CRM, Jira, Notion, or email. AI-filtered alerts. Free plan, no card.

Start monitoring for freeSee pricing

Tell Page Deltas what matters

alert me when the Hubspot pricing changes

https://www.hubspot.com/pricing
HubSpot pricing page — Professional plan starting at €792/mo
PDPage DeltasAppnow

🔔 Change detected on https://www.hubspot.com/pricing:
Price of the Professional plan went up from €749/mo to €792/mo.

A competitor raises Pro from $29 to $39. Your change monitor catches it. Then someone copies the summary into a Notion page, opens a Jira ticket by hand, and forwards the screenshot to sales over Slack. By the time the deal desk sees it, half the team has already heard a softer version of the news in a hallway chat.

That copy-paste step is the part that breaks. You already have Zapier or n8n for CRM updates, ticket creation, and digests. What you need is a clean event from the page watcher that those tools can catch and route.

I work on Page Deltas, so keep that in mind if I mention Visualping below. Page Deltas watches public pages, filters changes with an AI brief, and can POST a signed JSON webhook when something matches. There's no native Page Deltas Zapier app. The path is a generic webhook channel into Zapier's Catch Hook or n8n's Webhook node, then whatever you already automate from there. This post shows that setup end to end.

Why a chat ping is not enough

Slack (or Teams, or Discord) is fine when one person needs to glance at a change. It falls short when the same event should land in three systems. Sales wants a CRM note on the account. Ops wants a ticket with the before and after screenshots. Leadership wants a weekly digest, not twenty noisy pings.

You can wire each of those destinations by hand, or you can treat the alert as one event and let Zapier or n8n fan it out. Page Deltas already sends Slack, Discord, Teams, email, and signed webhooks on every plan, including Free. If you only need a room, our Slack how-to is enough. This post is for the case where the alert has to drive a workflow.

Visualping publishes a large hub of Zapier and n8n recipes, and it includes n8n on all plans. On Visualping's Free tier you get 5 pages, 150 checks a month, and a 60-minute minimum interval, with webhooks available; Slack and Teams sit on Business. Page Deltas Free covers 10 monitored URLs, unlimited checks on a best-effort cadence, AI filtering and summaries, and Slack, Teams, Discord, email, and webhooks with no credit card. Pick based on whether you care more about pixel-region watching (Visualping) or AI briefs and free chat channels (us).

What the webhook looks like

Channels live at the organisation level. You can mark one as the default for new monitors, and any monitor can override that list. For automation, add a Generic webhook channel and paste the Catch Hook or n8n URL. Full field notes live in the channels docs.

When a filtered change fires, Page Deltas POSTs JSON like this:

POST <your URL>
Content-Type: application/json
X-Signature: sha256=<hex>
{
  "event": "change.detected",
  "monitor_id": "...",
  "monitor_url": "https://example.com/pricing",
  "monitor_name": "Competitor pricing page",
  "change_id": "...",
  "detected_at": "2026-06-01T12:00:00Z",
  "summary": "Pro plan increased from $29 to $39/month.",
  "before_screenshot_url": "https://.../before.png",
  "after_screenshot_url": "https://.../after.png",
  "dashboard_url": "https://app.pagedeltas.com/monitors/..."
}

summary is the plain-language line you'll map into ticket titles and CRM notes. The screenshot URLs and dashboard_url are useful as ticket attachments or Notion embeds. X-Signature is HMAC-SHA256 of the raw body with the channel secret, shown once when you create the channel. Hash the raw bytes before you parse JSON, or verification will fail.

Delivery is a single attempt per channel with no automatic retries. Make the receiver answer quickly, and for anything you can't miss, attach a second channel of a different type (webhook plus email works) so a brief Zapier outage doesn't hide the change.

Set up Page Deltas first

Do the watching side before you touch Zapier or n8n. Otherwise you'll debug empty Zaps against a monitor that never fires.

  1. Create a free account and open Channels. Add Slack or email if you still want a human glance, then add a Generic webhook channel. Leave the URL blank for a moment if you don't have the Catch Hook yet. You'll paste it in after the Zapier or n8n steps below.
  2. Create a monitor for the page you care about (pricing, changelog, careers, ToS, a vendor status page). Write a short brief that says what to alert on and what to ignore. The filters docs cover how the brief is applied. Without a tight ignore line, quiet pages still produce noise (timestamps, related posts, cookie banners).
  3. Attach the webhook channel to that monitor (or rely on the org default). Click Send test on the channel once the Catch Hook or n8n URL is saved, so you know the path works before a real change lands.
  4. Optionally keep Slack on the same monitor. Chat for people, webhook for machines. That split is usually clearer than asking Zapier to re-post into Slack.

The Free plan covers 10 monitored URLs (a sitemap counts as one), AI filtering and summaries, the REST API and MCP, unlimited team members, and 14 days of history. Paid plans raise the URL cap: Starter $29 for 150, Pro $79 for 1,000, Business $199 for 5,000, Scale $499 for 20,000, Enterprise custom. We only watch public pages today. Login-gated pages are on the roadmap. Check cadence is adaptive, and paid plans get priority when the queue is busy.

Catch it in Zapier or n8n

Both tools use the same Page Deltas Generic webhook channel. Only the receiver changes. There's still no native Page Deltas Zapier app, so Zapier starts from Catch Hook, and n8n starts from a Webhook node.

Zapier

  1. Create a Zap with Webhooks by Zapier as the trigger and choose Catch Hook. Copy the custom webhook URL Zapier shows you.
  2. Paste that URL into your Page Deltas Generic webhook channel and save. Click Send test in Page Deltas (or wait for a real change). In Zapier, click Test trigger and confirm the sample includes summary, monitor_url, and the screenshot fields.
  3. Add actions. Common ones: create a Jira or Linear issue with summary as the title and dashboard_url in the description; append a row to a Notion database; create or update a HubSpot or Salesforce note on the competitor account; send a digest email that batches several changes. Map fields from the Catch Hook sample rather than typing placeholders by hand.
  4. Turn the Zap on. Send one more test from Page Deltas and follow it through each action.

If you need signature checks, Zapier Code steps can HMAC the body. For stronger verification, prefer n8n or a small function in front of Zapier, because you need the raw body bytes.

n8n

  1. Add a Webhook node, set the method to POST, and activate the workflow so n8n gives you a production URL. Copy it into the Page Deltas Generic webhook channel (or a second webhook channel if Zapier and n8n should both receive the event).
  2. Send a test from Page Deltas. Confirm the Webhook node shows the JSON body and the X-Signature header.
  3. Optional but worth it: add a Code node that recomputes sha256= plus HMAC-SHA256 of the raw body with your channel secret and compares it to X-Signature with a timing-safe check. Reject mismatches before any CRM or ticket step runs.
  4. Branch with an IF or Switch on monitor_name or a substring of monitor_url if different pages should open different tickets. Then add Jira, Notion, email, or HTTP Request nodes the same way you would for any other webhook source.
  5. Save and keep the workflow active. Page Deltas won't retry a failed delivery, so make the Webhook node respond with 2xx quickly and push slow work to later nodes or a queue.

Self-hosted n8n is useful when the channel secret should never leave your network. Cloud n8n is fine for most marketing and RevOps flows. Either way, you're composing standard nodes. Nothing here depends on a Page Deltas-specific connector.

What breaks, and what to do instead

A few limits show up once this is live. New fields may appear on the payload over time, so ignore unknown keys instead of rejecting the whole event. Treat change_id as an idempotency key if your ticket tool might see a duplicate from a manual replay.

If Zapier or n8n returns non-2xx, Page Deltas marks that delivery failed and moves on. The monitor keeps running. Check the delivery-attempts log in the app when a workflow goes quiet. For pages you can't miss, keep email or Slack on the same monitor as a backup path.

AI filtering only helps if the brief is specific. A vague "tell me about pricing changes" still lets related-article sidebars through. Spend five minutes on the ignore list before you build a five-step Zap. And if the thing you care about is only visible after login, neither Page Deltas nor a webhook will see it yet.

Sibling tools in our family cover other alert shapes. KWatch.io is for keyword mentions across social and the web when the signal isn't a single URL. For a fixed public page that changes in place, stay on Page Deltas and automate from the webhook.

Start with one Zap or workflow

Pick one page and one destination. Competitor pricing into a Notion database, or a vendor status page into Jira, is enough to prove the path. Create the monitor, attach a Generic webhook, catch it in Zapier or n8n, and map summary plus dashboard_url. The Free plan includes 10 URLs, AI filtering, every alert channel, and API access, with no credit card. Start monitoring for free.

Julien, Product Manager at Page Deltas

How to automate website change alerts with Zapier or n8n · Page Deltas