How Do You Handle Notion Triggers in Make.com?

Hey everyone,

I’ve been using Make.com for my Notion automations, but I’m running into an issue that’s making me consider switching to Zapier.

Right now, the only way I can check for new Notion database items in Make is by using the “Watch Database Items” trigger. The problem? It checks every minute, meaning my scenario runs are skyrocketing, and I keep having to upgrade. (I know I can increase the time in between runs, but this is not scalable as we are onboarding new clients)

On Zapier, there’s a direct “New Database Item” trigger, which only fires when an item is actually added—this is way more efficient.

Does anyone have a better workaround in Make to avoid excessive executions?

Hi @Hugo_Dupont,

Within Notion, you can set a database automation with ‘any property edited’ and/or ‘page added’ as trigger and send a webhook as action. If you use the Custom Webhook function of Make, I believe you can achieve what you want.

https://www.make.com/en/help/tools/webhooks

Let me know if this works for you!

Cheers,
@Henk-Operative

1 Like