Webhooks
Have PagePot call your URL whenever something changes in a project.
A webhook tells another system about changes as they happen: for example, rebuilding Jenny's staging site whenever a page's content changes, or updating a project tracker when a page is approved. Webhooks are on the Team and Agency plans; Project managers set them up.
Add a webhook
In the project's Settings → Integrations → Webhooks, enter the Endpoint URL (it must be https:// and public) and choose the Events:
| Events | Sent when |
|---|---|
| Sitemap and pages | Pages are added, moved, renamed, deleted or restored, or translated |
| Content | Blocks, SEO or metadata are saved (at most once a minute per page) |
| Workflow | Status or due-date changes on pages and diagrams |
| Assignments | Page assignees change |
| Comments | Comments and replies on pages and diagrams |
| Suggestions | Suggested edits are made or reviewed |
| Project | Project details or languages change, site imports |
Click Add webhook. Copy the signing secret that appears: it's shown only once. A project can have up to 10 webhooks. Changes to team members, sharing, integrations and settings are never sent.
What PagePot sends
A POST with a JSON body like this:
{
"id": "01a0f0c8-…",
"event": "page.status_changed",
"occurredAt": "2026-09-30T04:12:00.000Z",
"projectId": "01a0f0df-…",
"pageId": "01a0f0e1-…",
"target": { "type": "page", "id": "01a0f0e1-…" },
"actor": { "id": "…", "name": "Marco Diaz", "via": "app" }
}
It says what happened, not the new content: use the API to read the details. actor.via is api for changes made with an API key and mcp for changes made by an AI agent.
Each request has these headers:
PagePot-Event: the event, for examplepage.status_changed, orpingfor a test.PagePot-Delivery: a unique id for the delivery.PagePot-Signature:t=<timestamp>,v1=<signature>.
Check the signature
Make sure a request really comes from PagePot: compute an HMAC-SHA256 of <timestamp>.<raw body> with your signing secret and compare it with v1. Reject old timestamps (older than five minutes, say).
import { createHmac, timingSafeEqual } from 'node:crypto';
function isFromPagePot(header, rawBody, secret) {
const { t, v1 } = Object.fromEntries(
header.split(',').map((part) => part.split('=')),
);
const expected = createHmac('sha256', secret)
.update(`${t}.${rawBody}`)
.digest('hex');
const fresh = Math.abs(Date.now() / 1000 - Number(t)) < 300;
const given = Buffer.from(v1 ?? '');
return (
fresh &&
given.length === expected.length &&
timingSafeEqual(Buffer.from(expected), given)
);
}
Deliveries and failures
Answer with any 2xx status to confirm a delivery. Redirects count as failures. If your endpoint fails or takes longer than 10 seconds, PagePot tries again after 1, 5 and 30 minutes, then 2, 6 and 12 hours, keeping deliveries in order. If the last try fails, the webhook is paused and Project managers are notified; fix the endpoint and switch it back on.
For each webhook, Events and deliveries shows the recent deliveries and their results. Send test sends a ping event. New secret replaces the signing secret (the old one stops at once). Switch Active off to pause a webhook, or Delete it.