Webhook getting inactive after a few days non running

Questions
1

:bullseye: What is your goal?

get instant, event-based triggering for new files in a folder without the operation cost of frequent polling or the risk of a webhook going inactive during long idle periods.

:thinking: What is the problem & what have you tried?

Hi guys,

I have a scenario that could benefit from a webhook instead of polling. Right now, it’s triggered by a watcher that checks every 15 minutes, but that’s inefficient (it burns 4 operations per hour even though the scenario sometimes doesn’t run for months at a time).

The trigger is a new file landing in my meeting recordings folder, and this scenario is critical: I need it to fire as soon as a new file arrives, not on a delay. So I still need something “always on” and listening.

I know I could use “Run on demand,” but that requires me to manually go into Make and launch it each time, which defeats the purpose of automatic triggering.

Is there a way to get instant, event-based triggering here without the operation overhead of frequent polling, and without the risk of it going inactive/disabled during long idle stretches? Any advice appreciated!

3

Hey there,

Is that in Google drive? You can have an app script watch for new files and have it call a webhook one one is found.

4

Hello @Stoyan_Vatov , yes I have 2 with similar needs;

  • one is in a specific folder of a Google drive - generated by Gemini after a Meet recording, filtering with a keyword in the title
  • the other one is a Google invitation created by me, filtering by a keyword in the title invite and a specific key in the body

Just tapping your solution and I found that. Can you confirm that the following is what you had in mind?

Google Apps Script + time-driven trigger + webhook

  • You write a small Apps Script attached to your Drive folder
  • Set a Google-side trigger (e.g. onChange or a time-driven trigger checking every few minutes) that watches for new files in that folder
  • When a new file is detected, the script does an HTTP POST to your Make custom webhook URL, passing along file info (ID, name, link, etc.)
  • Your Make scenario just listens on that webhook — no polling operations consumed on the Make side, and since Apps Script is calling it periodically (even if just to check), you avoid the “webhook inactive” issue since it’s getting hit regularly

Thanks a mill :folded_hands:

5

Yeah, I have mine set to check every minute to simulate near instant webhook when a file is added.

7

Thank you @Temi_Josh

Indeed, I ran an App script and added a Webhook, first module of my scenario.

Seems like it resolve now the problem.

Thanks a mill for your help both

Diane