Push page changes into any tool.
Page Pulse sends a signed POST to your URL when a page changes, when a change scores notable or higher, and when its before and after results are in. Webhooks are free on every plan and on pay as you go.
- Three events:
change.detected,change.notable,outcome.ready - Signed with HMAC-SHA256 so you can trust the sender
- Works with Zapier, Make, n8n or your own server
{
"id": "evt_1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
"event": "change.notable",
"created_at": "2026-10-07T05:00:12+00:00",
"project": {
"uuid": "9b2f6c1e-4a7d-4f3b-9d8e-2c1a5b7e9f00",
"name": "acme.com",
"url": "https://acme.com"
},
"data": [
{
"change_id": 9921045,
"page_id": 48213,
"url": "https://acme.com/services/hydroseeding/",
"path": "/services/hydroseeding/",
"field": "Meta (title)",
"change_type": "edit",
"old_value": "Hydroseeding Services | Acme",
"new_value": "Hydroseeding in Denver, Fast Germination | Acme",
"detected_at": "2026-10-07T04:12:33+00:00",
"impact_band": "notable",
"impact_score": 64
}
]
}
Subscribe to the ones you need.
change.detected can be high volume on large sites. Most teams subscribe to change.notable and outcome.ready.
Every change
Any change on any tracked page, with noise screened out and a site-wide edit sent once with its page count: field, change type, old value, new value, page URL and time detected.
Changes that matter
Sent when the impact model scores a change notable, high or critical. Same fields plus impact_band and impact_score.
Results are in
Sent when a change finishes its measurement window: clicks and impressions before and after, lift, and a confidence band.
Verify every delivery in a few lines.
Each request carries X-PagePulse-Signature: sha256=<hex>, an HMAC-SHA256 of {timestamp}.{raw body} keyed with your endpoint secret. Reject anything older than five minutes.
| Header | Value |
|---|---|
| X-PagePulse-Event | The event name, for example change.notable |
| X-PagePulse-Timestamp | Unix time in seconds when the request was signed |
| X-PagePulse-Signature | sha256= followed by the hex HMAC-SHA256 of {timestamp}.{raw body} |
| User-Agent | PagePulse-Webhooks/1.0 |
import crypto from "node:crypto";
// raw = the request body exactly as received (a Buffer), not re-serialized JSON
function isValid(raw, timestamp, signature, secret) {
const expected = "sha256=" + crypto
.createHmac("sha256", secret)
.update(`${timestamp}.${raw.toString("utf8")}`)
.digest("hex");
const fresh = Math.abs(Date.now() / 1000 - Number(timestamp)) < 300;
return fresh && signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}
<?php
$secret = getenv('PAGEPULSE_WEBHOOK_SECRET');
$timestamp = $_SERVER['HTTP_X_PAGEPULSE_TIMESTAMP'] ?? '';
$signature = $_SERVER['HTTP_X_PAGEPULSE_SIGNATURE'] ?? '';
$raw = file_get_contents('php://input');
$expected = 'sha256=' . hash_hmac('sha256', $timestamp . '.' . $raw, $secret);
if (! ctype_digit($timestamp) || abs(time() - (int) $timestamp) > 300
|| ! hash_equals($expected, $signature)) {
http_response_code(401);
exit;
}
- Answer fast. Any 2xx within 10 seconds counts as delivered. Queue the work.
- Expect repeats. Delivery is at least once. De-duplicate changes by
change_id. - Hourly batches. Deliveries go out every hour and after the daily scoring run, up to 200 items per request.
- Retries for 72 hours. After 24 failed runs in a row an endpoint switches off until you turn it back on.
Zapier, Make or n8n in under ten minutes.
Signature checks need code, so no-code tools skip them. Keep the webhook URL private and subscribe only the events you need.
Zapier
Notable changes to a Slack channel.
- New Zap with the trigger Webhooks by Zapier → Catch Hook. Copy the URL.
- Create a Page Pulse webhook with that URL and the
change.notableevent. - Send a test event with
POST /webhooks/{webhook}/test. - Add Looping by Zapier over
data, then Slack → Send Channel Message with path, field and new value.
Make
Every outcome as a row in Google Sheets.
- New scenario starting with Webhooks → Custom webhook. Copy the address.
- Create a Page Pulse webhook with that address and
outcome.ready. - Send a test event so Make learns the payload shape.
- Add an Iterator on
data, then Google Sheets → Add a Row with URL, lift and confidence band.
n8n
Verified events into your own database.
- Add a Webhook node (POST) and copy its production URL.
- Create a Page Pulse webhook with that URL and the events you want.
- Add a Code node that checks
X-PagePulse-Signaturewith the Node sample above. - Split
datainto items and write them with a Postgres or Airtable node.
Create an endpoint with one call.
Webhooks are managed through the API. The response includes your signing secret, starting with whsec_. It's shown once, so store it right away.
curl -X POST https://app.pagepulse.dev/api/v1/webhooks \
-H "Authorization: Bearer $PP_TOKEN" -H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{"url": "https://hooks.example.com/pagepulse", "events": ["change.notable", "outcome.ready"]}'
Endpoints must be public https URLs. Up to 10 endpoints per organization.
Webhook questions, answered
Send your first webhook today.
Sign up with $2 free credit, no card needed. Add a site, point a webhook at Zapier to post in Slack, and see the first notable change.
Webhooks are free · $1 per 1,000 page checks