Let\u2019s get started! \ud83e\udd29<\/p>\n\n\n
- What Are Notion Webhooks and How Do They Work?<\/a><\/li>
- What are the Prerequisites and Access Requirements?<\/a><\/li>
- How to Set Up Notion Webhooks: Steps to Create and Configure<\/a>
- Step #1: Prepare a webhook URL (public + HTTPS)<\/a><\/li>
- Step #2: Create or pick a Notion integration and give it access<\/a><\/li>
- Step #3: Create the webhook subscription in Notion<\/a><\/li>
- Step #4: Capture and apply the verification token<\/a><\/li>
- Step #5: Implement basic endpoint behavior<\/a><\/li>
- Step #6: Validate payloads with the signature header<\/a><\/li>
- Step #7: Test the full flow end-to-end<\/a><\/li><\/ul><\/li>
- Troubleshooting Common Notion Webhook Errors<\/a><\/li>
- Notion Webhooks Integration Examples and Common Use Cases<\/a><\/li>
- What are the Limitations of Notion Webhooks?<\/a><\/li>
- How to Disable or Remove a Notion Webhook<\/a><\/li>
- Implementing Workflow Automation With ClickUp<\/a>
- Automate repetitive work<\/a><\/li>
- Find, summarize, and act faster<\/a><\/li>
- Integrate with your tech stack<\/a><\/li>
- Find the right info instantly<\/a><\/li><\/ul><\/li>
- FAQs<\/a><\/li><\/ul>\n\t\t\t<\/div>\n\t\t<\/div><\/div>\n\n\n
What Are Notion Webhooks and How Do They Work?<\/h2>\n\n\n
\nNotion webhooks are a real-time communication method that lets your workspace automatically notify another system when specific events occur. This can include triggers, such as creating a new page, updating a property, or modifying a database entry.<\/p>\n\n\n<\/div>\n\n
\n![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2025\/08\/image-599.png\")
via Notion<\/a><\/figcaption><\/figure><\/div>\n\n\n But how do they work? Here\u2019s a concise explanation of webhooks in practice: <\/p>\n\n\n\n
- \n
- Provide Notion with an endpoint <\/strong>(a unique URL) where updates will be sent <\/li>\n\n\n\n
- Instruct the platform of the changes <\/strong>to track, such as database updates, new pages, or property edits<\/li>\n\n\n\n
- Let Notion send requests automatically<\/strong> whenever one of those events occurs in your workspace<\/li>\n\n\n\n
- Receive details of the change,<\/strong> including what happened, when it happened, and which object was affected<\/li>\n\n\n\n
- Process the incoming data<\/strong> by triggering an automatic notification, updating another database, or starting an automation in a different platform<\/li>\n<\/ul>\n\n\n\n
Because custom webhooks are event-driven, updates occur only when changes happen, making them faster and more efficient than polling methods.<\/p>\n\n\n
\n\ud83d\udcda Glossary: <\/strong>HTTP refers to the HyperText Transfer Protocol. It\u2019s the foundation of data communication on the web, allowing web browsers and servers to talk to each other.\u00a0Whenever you open a website, your browser sends an HTTP request to a server, and the server responds with the content (like HTML, images, or videos).<\/p>\n\n\n<\/div>\n\n\n
What are the Prerequisites and Access Requirements?<\/h2>\n\n\n\n
Before you can start using Notion webhooks, there are a few things you need to have in place to make sure the setup works smoothly.<\/p>\n\n\n\n
Let\u2019s take a look. \ud83d\udc47<\/p>\n\n\n\n
1. Notion account and integration <\/h3>\n\n\n\n
You must have a Notion account with access to the workspace where the webhook will be used. <\/p>\n\n\n\n
Create a new integration or use an existing one in Settings & Members \u2192 Integrations<\/strong>. Share the integration with the specific pages or databases you want to monitor so it can access the relevant data.<\/p>\n\n\n\n
2. Public, secure webhook URL<\/h3>\n\n\n\n
Provide a publicly accessible, HTTPS<\/strong> endpoint where Notion can send webhook event data. Localhost or unsecured HTTP URLs are not supported.<\/p>\n\n\n
\n\ud83e\udd1d Friendly Reminder: <\/strong>Always protect your endpoints with HTTPS and validate SSL certificates to keep data safe in transit.<\/p>\n\n\n<\/div>\n\n\n
4. Verify token and event triggers<\/h3>\n\n\n\n
When you create a webhook subscription, Notion sends a one-time verification token to your endpoint. Respond with this token to confirm and activate your subscription.<\/p>\n\n\n\n
After this, you get to define which events should trigger the webhook (e.g., page creation, property edits, database updates).<\/p>\n\n\n
\n\ud83d\udca1 Pro Tip: <\/strong>Monitor successes and failures with detailed API documentation<\/a>. You\u2019ll only thank yourself while debugging if you have accurate logs. You also want to add trigger events, the payload structure, and example responses.<\/p>\n\n\n<\/div>\n\n\n
5. Permissions<\/h3>\n\n\n\n
Ensure your integration software<\/a> has the correct read or write permissions for the pages or databases being monitored. Without these permissions, the webhook will not receive updates.<\/p>\n\n\n\n
6. Workspace access level<\/h3>\n\n\n\n
Typically, you must be a workspace owner or admin to create and manage webhook integrations<\/a>.<\/p>\n\n\n\n
Keep this in mind: <\/p>\n\n\n\n
- \n
- Use either a custom server or a no-code\/low-code tool<\/strong> (like Make.com or Zapier) to handle incoming JSON payloads from Notion<\/li>\n\n\n\n
- For added security, verify the \u2018X-Notion-Signature\u2019 header<\/strong>. This is a cryptographic hash generated by Notion using your verification token, letting you confirm the request came from the platform and wasn\u2019t altered in transit<\/li>\n<\/ul>\n\n\n
\n\ud83d\udcd6 Also Read: <\/strong>Zapier vs. IFTTT<\/a><\/p>\n\n\n<\/div>\n\n\n
How to Set Up Notion Webhooks: Steps to Create and Configure<\/h2>\n\n\n\n
Here\u2019s a step-by-step guide to set up Notion webhooks. It\u2019ll walk you through creating webhook URLs, configuring your Notion integration, and testing your webhook for seamless automation. \ud83d\udda5\ufe0f<\/p>\n\n\n\n
Step #1: Prepare a webhook URL (public + HTTPS)<\/h3>\n\n\n\n
Decide where Notion will send events. You can create a webhook trigger in a no-code platform (such as Make, Zapier, n8n, or Pipedream) that provides a public URL. <\/p>\n\n\n\n
The other option is to set up a simple HTTPS endpoint on your server that accepts POST requests and returns a 200 OK response.<\/p>\n\n\n
\n![\"Webhook](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2025\/08\/image-600.png\")
Make your URL publicly reachable over HTTPS, as local or http:\/\/ endpoints will not work<\/em><\/figcaption><\/figure><\/div>\n\n \n\ud83d\udca1 Pro Tip: <\/strong>Webhooks don\u2019t always deliver. Add retry logic (such as exponential backoff) so that nothing gets missed.\u00a0<\/p>\n\n\n<\/div>\n\n\n
Step #2: Create or pick a Notion integration and give it access<\/h3>\n\n\n\n
Open Notion > Settings & Members <\/strong>> Integrations<\/strong>. Then, create a new integration (or select an existing one) and grant it the necessary scopes (read\/write, as required).<\/p>\n\n\n
\n![\"Focus](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2025\/08\/image-601-1400x875.png\")
Share the integration with the specific pages or databases you want the webhook to monitor<\/em><\/figcaption><\/figure><\/div>\n\n\n Step #3: Create the webhook subscription in Notion<\/h3>\n\n\n\n
In the integration\u2019s Webhooks<\/strong> tab, click + Create a subscription<\/strong>. Paste the webhook URL you prepared, select the event types to subscribe to (e.g., page created, page updated, database schema changed), and save.<\/p>\n\n\n\n
You can update the event types your subscription receives at any time. However, once the webhook URL has been verified, it cannot be changed. If you want to use a different URL, you\u2019ll need to create a new subscription.<\/p>\n\n\n
\n![\"Testing](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2025\/08\/image-602-1400x968.png\")
Create test webhooks for different events and finalize important ones <\/em><\/figcaption><\/figure><\/div>\n\n\n Step #4: Capture and apply the verification token<\/h3>\n\n\n\n
When you create the subscription, Notion sends a one-time POST<\/strong> to your webhook URL with a JSON body containing a verification token.<\/p>\n\n\n\n
Your endpoint must inspect the request, extract that verification token, then paste it (or enter it) in the Notion integration UI under Webhooks \u2192 Verify<\/strong> to activate the subscription.<\/p>\n\n\n
\n![\"Verify](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2025\/08\/image-603-1400x976.png\")
Activate your subscription to start receiving events instantly once verification is complete<\/em><\/figcaption><\/figure><\/div>\n\n\n Step #5: Implement basic endpoint behavior<\/h3>\n\n\n\n
Ensure your endpoint reliably performs three tasks: <\/p>\n\n\n\n
- \n
- Accepts POST requests<\/li>\n\n\n\n
- Responds with a quick 200 OK on receipt<\/li>\n\n\n\n
- Logs the raw request body for debugging purposes.<\/li>\n<\/ul>\n\n\n\n
Treat the webhook payload as a signal. It contains event type, timestamp, and minimal object IDs. If you need full content, fetch it from the Notion API using the IDs in the payload. Also, handle retries and rate limits gracefully (Notion has incoming webhook request limits).<\/p>\n\n\n\n
Step #6: Validate payloads with the signature header<\/h3>\n\n\n\n
Notion includes an X-Notion-Signature<\/strong> header with each webhook POST. For production systems, recompute the signature on your side (use HMAC-SHA256 on the raw request body with the verification token as the secret). <\/p>\n\n\n\n
Then, compare it to the header using a timing-safe comparison. If they match, the event is authentic; if not, discard it and log the discrepancy.<\/p>\n\n\n\n
Notion\u2019s docs include sample code for this in multiple languages. If you use a no-code platform, you may not be able to run this check. While the webhook will still function, signature validation is strongly recommended for production environments.<\/p>\n\n\n\n
Step #7: Test the full flow end-to-end<\/h3>\n\n\n\n
The final step is to verify all that you\u2019ve done: <\/p>\n\n\n\n
- \n
- Trigger a subscribed event in Notion (e.g., create or update a page)<\/li>\n\n\n\n
- Confirm your endpoint received a POST with the expected JSON and returned 200 OK<\/li>\n\n\n\n
- Ensure the signature check passes after you verify signatures<\/li>\n\n\n\n
- Paste the verification token into Notion and finish verification, then repeat the test<\/li>\n<\/ol>\n\n\n\n
\ud83d\udd0d Did You Know? <\/strong>Unix pipes<\/a> were born in 1973. It was a simple idea of connecting a program\u2019s output (STDOUT) to another program\u2019s input (STDIN) that became one of the most powerful constructs in computing.<\/p>\n\n\n<\/div>\n\n\n
Troubleshooting Common Notion Webhook Errors<\/h2>\n\n\n\n
When a Notion webhook isn\u2019t delivering events as expected, the issue often involves configuration, permissions, or event timing. <\/p>\n\n\n\n
Below are the most frequent causes and how to resolve them. \ud83d\udc81<\/p>\n\n\n\n
1. Check integration access permissions<\/h3>\n\n\n\n
Webhook events are only triggered for content your integration can access. If the event source is in a private page, database, or workspace section your integration isn\u2019t connected to, Notion won\u2019t send the event.<\/p>\n\n\n
\n\ud83d\udccc Example:<\/strong> A page created inside a private workspace folder won\u2019t trigger the webhook unless the integration is explicitly granted access.<\/p>\n\n\n<\/div>\n\n\n
2. Verify required capabilities<\/h3>\n\n\n\n
Some webhook event types require specific capabilities enabled in your integration settings.<\/p>\n\n\n\n
Without the right capability, events won\u2019t be delivered even if the integration has access to the page or database. You can adjust these in the Capabilities<\/strong> section of your integration settings.<\/p>\n\n\n
\n\ud83d\udccc Example:<\/strong> To receive \u2018comment.created\u2019 events, the integration must have the Comment read<\/strong> capability enabled.<\/p>\n\n\n<\/div>\n\n\n
3. Understand aggregated event timing<\/h3>\n\n\n\n
Certain events, such as page.content_updated<\/strong>, are aggregated before being delivered to avoid flooding your endpoint with multiple updates during rapid changes (e.g., typing, formatting, or rearranging blocks).<\/p>\n\n\n\n
If you need near-instant feedback for testing, start with non-aggregated events, such as comment.created <\/strong>or page.locked.<\/strong><\/p>\n\n\n
\n\ud83d\udccc Example:<\/strong> If a user edits a page title three times in quick succession, Notion sends a single aggregated event instead of three separate ones.<\/p>\n\n\n<\/div>\n\n\n
4. Confirm subscription status<\/h3>\n\n\n\n
Even if permissions and capabilities are set correctly, events won\u2019t reach your endpoint unless the webhook subscription is active.<\/p>\n\n\n\n
Check the Webhooks<\/strong> tab in your integration settings to ensure the subscription is:<\/p>\n\n\n\n
- \n
- Active<\/li>\n\n\n\n
- Not paused<\/li>\n\n\n\n
- Not pending verification<\/li>\n\n\n\n
- Not deleted<\/li>\n<\/ul>\n\n\n\n
If the subscription is inactive or in a pending state, events won\u2019t be delivered.<\/p>\n\n\n
\n\ud83d\udccc Example:<\/strong> If you created a webhook but forgot to complete the verification step, the subscription will remain pending, and your endpoint won\u2019t receive any events.<\/p>\n\n\n<\/div>\n\n\n
Notion Webhooks Integration Examples and Common Use Cases<\/h2>\n\n\n\n
Here are some workflow automation examples<\/a> of connecting Notion webhooks in action that go well beyond the usual \u2018send an email notification.\u2019 <\/p>\n\n\n\n
These will show how you can tailor and trigger automations to real team workflows:<\/p>\n\n\n\n
1. Email threads managed inside Notion<\/h3>\n\n\n\n
You can transform Notion into a lightweight customer support hub using webhooks, your backend, and email. <\/p>\n\n\n\n
Whenever a new email arrives, it automatically creates a new page in a Notion database, entirely replicating the email thread in the page\u2019s comment section. You can reply directly from comments, and starting a reply with \u2018#\u2019 sends the response out via email.<\/p>\n\n\n
\n\ud83e\udde0 Fun Fact: <\/strong>The term \u2018webhook\u2019 was coined in 2007 by Jeff Lindsay<\/a>, based on the programming concept of a \u2018hook.\u2019<\/p>\n\n\n<\/div>\n\n\n
2. QR code-driven inventory workflow<\/h3>\n\n\n\n
Another setup uses webhooks with Firebase functions to automate a QR-based inventory system. After creating or updating a part entry in Notion, the webhook runs server-side logic to generate a QR code.<\/p>\n\n\n\n
That code is printed, scanned via a web app, and then time-stamped back into Notion to reflect the part\u2019s status, whether it\u2019s in the warehouse, out for delivery, or shipped.<\/p>\n\n\n\n
3. Automate timesheets from Notion entries<\/h3>\n\n\n\n
With webhooks, you can automatically track work hours and log them into a timesheet tool whenever your Notion workspace is updated. <\/p>\n\n\n
\nFor example, if your team records task start and end times in a Notion database, a webhook can trigger an automation that pushes those values into a timesheet or payroll system.<\/p>\n\n\n<\/div>\n\n\n
4. Social media scheduling from Notion<\/h3>\n\n\n\n
You\u2019re drafting social posts in Notion. You write your caption, drop in a media URL, set a publishing time, and mark the status as \u2018Ready to Publish.\u2019<\/p>\n\n\n\n
This is when a webhook takes over, sending that data to your workflow automation software<\/a>. Next, it delays until the scheduled time, then posts for you on Instagram, Facebook, and LinkedIn.<\/strong><\/p>\n\n\n
\n\ud83d\udcee ClickUp Insight:<\/strong> Only 10% of our survey respondents regularly use automation tools and actively seek new opportunities to automate.<\/p>\n\n\n\n
This highlights a major untapped lever for productivity\u2014most teams are still relying on manual work that could be streamlined or eliminated.<\/p>\n\n\n\n
ClickUp\u2019s AI Agents<\/a> make it easy to build automated workflows, even if you\u2019ve never used automation before. With plug-and-play templates and natural language-based commands, automating tasks becomes accessible to everyone in the team!<\/p>\n\n\n\n
\u00a0\ud83d\udcab Real Results: <\/strong>QubicaAMF cut reporting time by 40% using ClickUp’s dynamic dashboards and automated charts\u2014transforming hours of manual work into real-time insights.<\/p>\n\n\n\n
Automate your workflow with ClickUp<\/a><\/div>\n\n\n<\/div>\n\n\nWhat are the Limitations of Notion Webhooks?<\/h2>\n\n\n\n
Although Notion webhooks allow for real-time updates and automation, they\u2019re not without constraints. Understanding these limitations helps you design workflows that remain reliable, efficient, and cost-effective.<\/p>\n\n\n\n
Here are some common ones: <\/p>\n\n\n\n
- \n
- Unavailable for workspaces<\/strong>: Webhooks aren\u2019t supported at the workspace level, so you\u2019ll need to manage them at the individual integration or database level instead<\/li>\n\n\n\n
- Sparse payloads:<\/strong> Notion sends only minimal data like IDs and timestamps, not full content or property values, so you’ll need to fetch those details separately<\/li>\n\n\n\n
- Delayed or missing events:<\/strong> Webhook delivery isn’t always instant. Aggregation, delays up to several seconds, or missing events during rapid updates can occur<\/li>\n\n\n\n
- API rate limits:<\/strong> You\u2019re limited to ~3 API calls per second (around 2,700 every 15 minutes); burst usage can lead to errors or throttling<\/li>\n\n\n\n
- Size constraints:<\/strong> Requests exceeding 1,000 blocks or payloads larger than 500 KB, and oversized property values can trigger validation errors<\/li>\n\n\n\n
- Consistency issues:<\/strong> Webhook events may arrive out of order or with stale data, so always use timestamps and fetch the current state via the API<\/li>\n\n\n\n
- Action-level limitations:<\/strong> You can only set up to five webhook actions per automation, and only HTTP POST requests are supported. Plus, you can only send database page properties, not full page content<\/li>\n<\/ul>\n\n\n
\n\ud83d\udd0d Did You Know? <\/strong>Pingbacks<\/a> on blogs were an early cousin of webhooks. Of course, webhooks are far more flexible, letting you send any arbitrary event data to any URL handler.<\/p>\n\n\n<\/div>\n\n\n
How to Disable or Remove a Notion Webhook<\/h2>\n\n\n\n
Disabling or removing a Notion webhook can be necessary when you no longer need the integration or want to prevent unnecessary event deliveries. It\u2019s also imperative when you need to enforce stricter security and compliance policies. <\/p>\n\n\n\n
Depending on your permissions and workspace plan, you can either stop webhook functionality at the workspace level or delete the webhook subscription entirely.<\/p>\n\n\n\n
Let\u2019s look at how: <\/p>\n\n\n\n
1. Disabling webhook actions in an Enterprise workspace<\/h3>\n\n\n\n
If you\u2019re a workspace owner on Notion\u2019s Enterprise Plan, you can globally disable webhook actions for your entire workspace. This ensures that no member, regardless of role, can set up new webhook-based automations.<\/p>\n\n\n\n
Here are the steps to disable webhook actions in an Enterprise workspace:<\/p>\n\n\n\n
- \n
- Go to Settings<\/strong> in your sidebar<\/li>\n\n\n\n
- Open the Connections<\/strong> tab<\/li>\n\n\n\n
- Toggle off Allow webhooks in automations<\/strong><\/li>\n<\/ol>\n\n\n\n
Once disabled, the Send webhook<\/strong> action will no longer be available in the automation builder for any member in the workspace. This change takes effect immediately and applies to all automations, regardless of who created them.<\/p>\n\n\n
\n\ud83e\udde0 Fun Fact: <\/strong>Before webhooks<\/a>, the web relied on polling; feeds and APIs weren\u2019t really \u2018pushing\u2019 data to you. Instead, your app had to repeatedly check (\u2018poll\u2019) for changes, often wasting resources.<\/p>\n\n\n<\/div>\n\n\n
2. Removing an existing webhook subscription<\/h3>\n\n\n\n
If you simply want to stop receiving webhook events without disabling the entire webhook feature, here\u2019s how to do it: <\/p>\n\n\n\n
- \n
- Navigate to your integration settings in the Notion Developers dashboard<\/strong><\/li>\n\n\n\n
- Locate the active webhook subscription under the Webhooks<\/strong> tab<\/li>\n\n\n\n
- Choose Delete<\/strong> or Deactivate<\/strong> to remove the subscription<\/li>\n<\/ol>\n\n\n\n
Removing a subscription will stop event deliveries to the specified endpoint, but won\u2019t affect other webhook configurations in the same workspace.<\/p>\n\n\n\n
Implementing Workflow Automation With ClickUp<\/h2>\n\n\n\n
ClickUp<\/a> is the everything app for work<\/em> that combines project management, knowledge management, and chat\u2014all powered by AI that helps you work faster and smarter. <\/p>\n\n\n\n
Building on what you\u2019ve just mastered with Notion webhooks, let\u2019s explore how ClickUp takes automation and productivity to the next level. The Notion alternative<\/a> is especially useful if you\u2019re looking to trigger smarter workflows, surface instant insights, or automate context-aware tasks across your workspace. <\/p>\n\n\n\n
Here\u2019s how. \ud83d\udc40<\/p>\n\n\n\n
Automate repetitive work<\/h3>\n\n\n\n
- Locate the active webhook subscription under the Webhooks<\/strong> tab<\/li>\n\n\n\n
- Open the Connections<\/strong> tab<\/li>\n\n\n\n
- Sparse payloads:<\/strong> Notion sends only minimal data like IDs and timestamps, not full content or property values, so you’ll need to fetch those details separately<\/li>\n\n\n\n
- Unavailable for workspaces<\/strong>: Webhooks aren\u2019t supported at the workspace level, so you\u2019ll need to manage them at the individual integration or database level instead<\/li>\n\n\n\n
- For added security, verify the \u2018X-Notion-Signature\u2019 header<\/strong>. This is a cryptographic hash generated by Notion using your verification token, letting you confirm the request came from the platform and wasn\u2019t altered in transit<\/li>\n<\/ul>\n\n\n
- Instruct the platform of the changes <\/strong>to track, such as database updates, new pages, or property edits<\/li>\n\n\n\n
- Find, summarize, and act faster<\/a><\/li>
- Step #2: Create or pick a Notion integration and give it access<\/a><\/li>
- What are the Prerequisites and Access Requirements?<\/a><\/li>
![\"ClickUp](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2025\/08\/image-604.png\")