https://youtu.be/Za2AUcBCsHs

Think of it like this: Instead of repeatedly polling the Notion API to check if anything has changed, Notion will tell you the moment something important happens.

— from the official Notion webhooks documentation

In short, Notion webhooks allow you to trigger automations immediately upon a specific event that happens in a Notion workspace, without having to use Database Automations or Buttons. So far, only polling was available via the Notion API — that's why this is an important and much-requested update. Webhooks (instant triggers) are less resource intensive and more precise than polling (constantly checking for changes).

P.S. Some events are aggregated rather than delivered immediately — here is the official documentation explaining this concept.

—

Before the launch of Notion Webhooks, you couldn't instantly trigger external automations without using database automation webhook requests or buttons that triggered an external webhook.

Now, Notion can send webhook requests automatically based on many events that happen in your Notion workspace. This means your automations will start immediately when something happens, eliminating the need for the polling trigger to check for database changes or having to create multiple Database Automations.

Below are the available webhook events you can subscribe to from any Notion workspace.

For high-frequency events like page.content_updated, Notion batches changes that occur within a short time window into a single webhook event. Events such as page.created, page.deleted, page.undeleted occur in quick succession, you may only receive the most meaningful result event -- or none at all if the state returns to its original one.

Event aggregration helps reduce redundant calls and improves reliability. Aggregated events may have a slight delivery delay (typically under one minute).

— from the official Notion webhooks documentation

How to setup Notion workspace webhooks

Here are the steps to set up workspace webhooks in Notion:

1. Create a webhook: you can create a webhook and subscribe to the desired events via the Integrations page. When you create a subscription, you will be asked to provide an HTTPS webhook URL and select all the events you want to subscribe to. Once done, select "Verify subscription".
2. Verify webhook: at this point, Notion will send a one-time POST request to your webhook URL containing a verification_token, which you can copy and paste in the Notion integration setup page for verification. You can resend the verification_token multiple times if needed. Once verified, you can't change the webhook URL. Instead, you would need to delete and recreate the subscription.
3. Validate payload: every time Notion sends a request to your webhook, it will include a header that you can use for validation/security purposes (this is not required but recommended). Read all the specifics here.
4. Testing: before testing, make sure your Integration has access to all the Pages and Databases you want to monitor. You can add Integrations to any Notion page/database via the dedicated menu on the three dots at the top right corner of the page/database. Read more here.

—

Here is a practical use case:

Say you want to track database schema changes because they may lead to errors or have been done by mistake. So you set up your automation accordingly:

1. You add a Webhook trigger — this will provide you with the URL that you can paste in the Notion webhooks configuration menu for validation.