What are the Best Practices for Connecting Notion and Pipedream and Handling Notion's Webhook Calls?

This topic was automatically generated from Slack. You can find the original thread here.

I’m looking for best practices connecting Notion and Pipedream. When Notion introduced the call of webhooks in their automations last year I thought I can replace all my “every 15 Min Notion polling trigger” with webhook-calls on edit. But I recognized, that Notion fires a webhook call on every keystroke in a field and also the case “some of these properties” changed is not really possible with Notion Automation. So I rolled back to “Polling on updates”.
Since I have a lot of different Notion trigger, mainly different property sets which fire if one of these properties changes I wonder if there is a more elegant and sustainable way of fulfilling these cases.
Do you have any ideas?

I guess renaming each trigger for each property set should help, yeah?

Hi Andrew, yes that helps to keep an overview. But my question was more like in an architectual way, e.g. just use one trigger and dispatch the pages/properties within the workflow.

Got it. You can use 1 trigger in many workflows, or use 1 workflow to trigger other workflows. I think the best way is to create individual triggers for each property set and then reuse them in your workflows when possible

ah ok, thank you!