Has anyone else experienced their webhooks becoming inactive after a few days of non-activity? I’m trying to maintain an event-driven workflow that reacts to new files in a folder without incurring the cost of frequent polling. However, my webhook seems to lose its functionality during long idle periods.
Has anyone found a reliable method to keep webhooks alive or any configurations that could prevent them from going inactive? I’d love to hear about any workarounds or best practices you’ve implemented!
Yes, this can happen in Make. If a webhook stays unused for a long time, it may become inactive, especially if it’s not properly connected to an active scenario.
For a reliable setup, make sure the webhook is attached to an active scenario. If it’s already expired, create a new webhook and reconnect it.
For file monitoring, I’d also recommend using the storage provider’s native webhook/event system instead of polling every few minutes. This keeps the workflow event-driven and avoids unnecessary Make operations.
YES SIMON… you’re right that a webhook in Make can become inactive after a period of no use, particularly if it’s not associated with an active scenario. The key is ensuring the webhook remains linked to an operational scenario throughout its lifecycle. If you find it’s already expired, create a new webhook and reattach it to your intended scenario.
For monitoring files, it’s smarter to leverage the native webhook/event systems of your storage provider. This approach ensures your workflow stays event-driven and avoids heavy polling, which saves on unnecessary operations in Make.
Let me know if you’ve already tried this and if there’s any error message or behavior you’re still seeing!
