I have a zap that gets triggered when an event from my google calendar is about to start. So far, so good. However, I noticed that events who once started and already have triggered the zap once, don’t trigger again after they have been moved to a new start time. So, once the event is “consumed”, it cannot trigger the zap again, event if it’s moved to the future.
I recognize that this behavior may be desirable in some cases, however I have a use case where I would prefer that the event would trigger again after it has been moved to the future and it’s new starting time arrives. Could this be added as an option to the trigger step? Besides this, it would be great if the documentation of the event trigger step would describe this behavior clearly, it took me some time to find this out, I assumed some bug at first.
Question
Google Calendar Event Start Trigger doesn't trigger for moved events
+12- Zapier Solution Partner
Hi
Event Start works as a polling trigger, and Zapier dedupes based on the event’s unique ID. Since the ID doesn’t change when you update the start time, Zapier treats it as the same event and won’t fire the trigger again once it’s already seen it.
If this behavior is important for your workflow, the best option would be to create a custom Google Calendar app where you can control how the trigger works.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.