Notion webhooks
Test and debug Notion webhooksfor database and page changes
Capture database changes and page updates as they arrive, read the nested JSON and keep the tools that depend on your Notion workspace in sync.
How Notion webhooks work
| Where to configure it | Your connection's settings > Webhooks tab > + Create a subscription. The URL must be public and SSL; localhost is not reachable. |
|---|---|
| Verification step | Notion sends a one-time POST with a verification_token. Paste it into the Verify dialog to activate the subscription. |
| Signature header | X-Notion-Signature: sha256= followed by the HMAC-SHA256 of the request body, keyed with the verification_token. |
| Aggregated events | Some events, such as page.content_updated, are aggregated and can arrive a minute or two after the edit. |
Sources (checked November 2026)
See every Notion event your app receives
Notion webhooks power knowledge base sync, task automation and content workflows. When events fail to deliver, the tools that mirror your workspace fall out of date.
Hooklistener captures every Notion request with its payload and headers. Debug sync issues, inspect event data and use replay (Pro) to test your automations.
Notion webhook challenges
Complex data structures
Notion's nested blocks and properties are hard to read in a log line, so it is easy to map the wrong field.
Rate limit mysteries
API rate limits delay the follow-up calls your handler makes, and it is hard to tell whether the webhook or the API call was late.
Database sync failures
Property changes don't reach external systems, and nobody notices until a report is wrong.
How Hooklistener helps with Notion webhooks
Prettified Notion payloads
Read each Notion event as formatted JSON with its headers, so nested blocks and properties are easy to map before you write the sync code.
Request timing in the history
Every Notion request is kept with the time it arrived (history by plan), so you can tell whether the webhook was late or your handler's follow-up API call hit a rate limit.
Anomaly detection for database changes
Anomaly detection flags missing fields, changed field types and volume drops on the endpoint, so a renamed Notion database property shows up before an external report goes wrong.
Try it: point Notion at a free webhook URL or run a test with the webhook tester.
Notion automation workflows
Content publishing
Publish Notion pages to blogs, docs sites or knowledge bases when their status changes to published.
Task management sync
Keep Notion databases in sync with Jira, Asana or Linear, and check that no status change went missing.
Knowledge base search
Update search indexes in Algolia or Elasticsearch when pages change, triggered by events you have inspected.
Replay a failed webhook without re-triggering the provider
Once a delivery is captured, you can resend its exact headers and body to localhost, staging or production from the dashboard or through your coding agent over MCP, so the provider never has to fire a new event. Replay is on Pro and above. Read the replay guide.
Comparing webhook debugging tools?
See how Hooklistener stacks up against webhook.site, RequestBin, Beeceptor, Hookdeck and ngrok in the best tools to capture and inspect webhook payloads, or read the head-to-head pages for Hooklistener vs ngrok and Hooklistener vs Beeceptor.
Frequently asked questions
Does Notion send webhooks?
Notion integrations can send webhooks to a URL you configure. Hooklistener captures whatever reaches the endpoint, whichever integration sent it.
Can I read Notion's block structure?
Yes. Hooklistener prettifies the JSON body, so nested blocks, children and properties are easy to read.
Can I replay Notion events?
Yes. Replay is on Pro and above. Resend a captured event to localhost or staging while you test a sync change.
Can non-developers use this?
Yes. Send a shareable debugger link for a captured event so an ops teammate can see what Notion delivered.
Keep the tools around Notion in sync
Capture and inspect every Notion webhook so the systems that mirror your workspace stay current.