Exactly. The trigger fires from the gCal side when the upstream calendar is changed, which means the downstream gets updates quicker. No worries if you don't merge. I sent the PR as a courtesy to let you know that I appreciate what you've built, and to let you know that there's additional functionality supported in case you want to revisit your code - but I also realize that most of us create automation with the hope that we will never again have to think about it. With update latency handled by the push trigger, I also added logic in my deployment to widen the time-based trigger frequency up to 12hr. Periodic polling is still a good idea in case the push trigger doesn't fire, but every few hours is (IMHO) more than sufficient as a redundant sweep. Unfortunately the update trigger doesn't carry specific info: it is only a notification that a change happened somewhere, but that makes it perfect to replace a periodic poll. Interestingly, MS O365 does a much more thorough job of triggers with their Power Automate service, but the trade-off is that their only UI is a click/drag "no-code" web IDE, both for editing and for logging. Cheers, -Jim