Notion Webhooks are finally here! In this short guide, you’ll learn everything you need to know about using Notion Webhooks to trigger external automations, what data you can send with them and what to be aware of when using Notion Webhooks. Whether you use Make.com, Relay.app, Zapier, N8N, Pipedream or another no-code automation tool, the addition of Notion Webhooks makes a lot of use cases much easier than before.
How to set up a webhook in Notion
Notion Webhooks are part of Notion’s built-in database automations. To create a webhook, you need to:
- go to the database that contains the information you want to send
- click on the little flash icon above the database to create a new automation
- select the events that should trigger the webhook
- choose the Send Webhook action
- specify where the webhook should go and what data should be sent
Alternatively, you can create a Database Button and choose the Notion Webhook action to send data whenever the button is clicked.
What data can you send with a Notion Webhook?
Notion Webhooks allow you to send the following custom data:
- custom headers with key / value pairs
- any property values from the database entry that triggered the automation
Besides, any Notion Webhook will always send the following information:
- the ID of the entry that triggered the automation
- the system information for database items (created time, created by, last edited time, icon, cover, parent and properties)
- the specific automation information (automation ID, action ID, event ID and number of attempts)
The properties and property values sent will be limited to the data that you choose during the Notion Webhook setup.
As of today, Notion Webhooks will always be sent as Post requests.
How can you trigger a Notion Webhook?
Notion Webhooks are available as database automation actions. That means, you can trigger them either via all available database automation triggers (for example a certain property change) or through Notion Buttons.
How to receive a webhook from Notion
How to receive a Notion Webhook in Make.com
In Make, create a new scenario and search for the Custom Webhook module.
Add a new webhook and give it a name for internal organisation.
Once you confirm the setup, you’ll receive a URL that you can paste into the Notion Webhook action to send data to Make.com.
How to receive a Notion Webhook in Relay.app
In Relay, create a new automation and look for the webhook action.
Relay will automatically generate a webhook for you that you can then paste into the Notion Webhook step.
How to receive a Notion Webhook in Zapier
Create a new Zap, click on the Trigger Module and search for Webhook.
Set up the trigger event for the Webhook as Catch Hook to automatically parse the data and click through the Configure step.
Once you’re on the Test part of the step, Zapier will show you a webhook URL that you can paste into the Notion Webhook setup.
How to receive a Notion Webhook in any tool
You know the drill by now – working with webhooks always follows the same steps.
- Your automation tool of choice needs to set up a URL to listen to an incoming webhook
- You create a database automation in Notion that will send data to this URL in a specific event
- Your automation tool listens to the incoming data and you can use it to trigger any additional automations
What actually is a webhook?
A webhook is like a digital message that automatically notifies one application when something interesting happens in another application. Think of it as setting up a direct connection between two apps – when something happens in the first app, it automatically sends a message (with data) to the second app.
For example, when someone updates a Notion database entry, a webhook can instantly notify your automation tool about this change. This is much more efficient than having your automation tool constantly check Notion for updates (imagine having someone repeatedly ask “Are we there yet?” versus just getting a notification when you arrive).
Webhooks are particularly useful because they:
- work in real-time, triggering actions immediately when something happens
- save resources by eliminating the need for constant checking between applications
- can carry detailed information about what exactly happened, allowing for precise automated responses
For non-technical users, the beauty of webhooks is that modern automation tools handle all the complex technical details. You just need to know how to connect point A (like your Notion database) to point B (your automation tool), and the webhook takes care of the rest. It’s like setting up a domino effect between your different tools and applications.
How to turn off Notion Webhooks
Notion Webhooks are available by default on all workspaces with database automations (i.e. all paid plans).
If you are on an Enterprise Plan, you can turn off webhooks for all users by going to your settings, then to connections and then changing the toggle on Allow webhooks in automations.
Are Notion Webhooks free?
Notion Webhooks are part of Notion Database Automations which are only available on paid plans. Sending a Notion Webhook doesn’t incur any additional cost, so the feature itself can be used for free (as long as you generally pay for your Notion account).
What can Notion Webhooks be used for?
Notion Webhooks can be used to trigger any type of automations for your systems. They are particularly useful if you use Notion for Business and want to connect your Notion system to the other apps in your tech stack.
Here are a few automation ideas:
- Inform your team in Slack whenever a project has been completed
- Trigger an AI web search whenever a new potential lead is added to your CRM
- Publish an article from Notion to Wordpress or Social Media
- Automatically create invoices when certain milestones are delivered
- Automatically create support tickets in your help desk when issues are logged in Notion
- Send meeting summaries to attendees when notes are completed in Notion
