Notion sends page.created webhooks right away
TL;DR
On November 11, 2026, Notion started sending page.created webhook events right away, usually within a few seconds. The first page.properties_updated event for a page also goes out right away, and later property edits in the next minute are combined into one event. A connection that applies a template when it creates a page can see page.created before that template has finished.
- Status
- Live
- Released
- Plans
- Not specified
What changed
On November 11, 2026, Notion's developer changelog changed when two page webhook events are sent.
page.created now arrives right away, usually within a few seconds of the page being created. Before, Notion held that event for about a minute so later changes could be combined into it. The event aggregation section now says page.created is not aggregated. Changes made right after the page is created arrive as their own events.
The first page.properties_updated event for a page also arrives right away, when no other change to that page is waiting to be sent. That event starts a one-minute window. Property edits in the window are combined into one page.properties_updated event, which arrives about a minute after the first edit. The event-type table marks this event as aggregated after the first edit.
Other high-frequency events keep the older batching. page.content_updated is still aggregated by the page over about one minute, so about a minute can pass between the first content change and delivery. The same delivery page still says events should arrive within 5 minutes, and that most arrive within a minute. The November 11 note is about these two page events, not a new promise for every webhook type.
The changelog has no official image for this item.
Templates and the early page.created event
The changelog points to updated steps in Creating pages from templates for connections that apply a template while creating a page.
Notion sends page.created usually within a few seconds of the create-page call. The template usually has not finished, so the page is often still blank when that event arrives. When the template finishes, Notion sends page.content_updated. That event is aggregated, so it usually arrives about a minute after the template starts applying. Complex templates can take longer.
The guide's handler for that flow:
- On
page.createdfor the new page, call Retrieve block children. If the content is already there, continue. If the page is still blank, wait. - On
page.content_updatedfor that page, the template has finished applying. - A later
page.content_updatedcan still arrive after the handler has already continued. Ignore events for a page that is already processed. - There is no template-failure webhook or public job-status endpoint. Set a timeout, then retrieve the block children again. The guide says not to reapply the template automatically, because content already copied can be duplicated.
The November 11 changelog and the linked pages do not name a plan requirement. This timing change is separate from the connection Health tab, which reports recent API request failures and rate limits.
Why it matters
A connection that creates a page and then immediately listens for page.created can now react in seconds. It should not treat that event as proof that a template, or any edit made in the following seconds, is already included.
Property syncs can record the first edit immediately. Edits in the following minute still collapse into one event, so a handler that expects one webhook per property save will miss the in-between values. The delivery page still says events can arrive out of order, and that the webhook may not show the current page. Fetch the page from the API when the current value matters.
Frequently asked questions
When does a Notion page.created webhook arrive?
Usually within a few seconds of the page being created. As of November 11, 2026, Notion does not hold page.created for about a minute, and it does not fold later edits into that event.
Are Notion page property webhooks still combined?
The first page.properties_updated event for a page goes out right away if nothing else for that page is waiting. Later property edits in the next minute are combined into one event, which arrives about a minute after the first edit.
What webhook should I wait for after applying a Notion template?
Wait for page.content_updated if the page is still blank when page.created arrives. Content updates are still aggregated, so that event usually arrives about a minute after the template starts applying. Complex templates can take longer. The guide says to set a timeout, because there is no template-failure webhook.
Which Notion plans include faster page webhooks?
The November 11 changelog, the event aggregation section, and the templates guide do not say.