Google Calendar Event Ended now with Recording?

Hi ​@Reinvent 

Help us have more info by posting screenshots showing how your Zap steps are outlined and configured in EDIT mode.

Plus, post screenshots from the live Zap Runs showing proof that the same same Event Ended triggered multiple times. (DATA IN/OUT)

I'm examining only one step (the first one):

 

One example from April 16th where it came only one event:

 

Note that there is no attachments section. However, let's take the events I and J. As you can see, both refer to the same Google Calendar Event:

However, J - the "recording generated" event - has attachments (recording):

While I - the "calendar ended" event - hasnt:

​@Reinvent 

Post screenshots showing how Zap step 1 is configured in the CONFIGURE tab.

Help links for using Cal in Zaps: https://zapier.com/apps/google-calendar/integrations#help

About the help links I read them before the implementation and couldn´t find anything specifically related to this question (calendar x recording).

​@Reinvent 

Have you tried turning your Zap ON and testing live?

Then check your Zap Runs history details to see the DATA IN/OUT for each step to help you trace/troubleshoot.

https://zapier.com/app/history/

Hi ​@Troy Tessalone ,

Thanks for the suggestion, and apologies for being candid, but that doesn’t really address my question. My Zap is already turned on and running perfectly — I’m not looking to troubleshoot execution issues. What I’d like to understand is why the “Event Ended” trigger has changed its behavior: initially it only fired at the meeting’s end time, and now it also fires when the recording becomes available. Has there been a recent update to that trigger? If so, could you point me to the release notes or documentation covering this change?

Thanks!

​@Reinvent 

Can you provide screenshots of live Zap Runs that show the multiple triggering of the GCal Event Ended for the same GCal Event?

The screenshots you shared thus far are from the TEST tab within the Zap EDITOR, not from the Zap Runs: https://zapier.com/app/history/

Those records are examples to use to configure the Zap action steps, which can be different from the actual data that is processed thru live Zap Run.

I do not work for Zapier, so you can try opening a ticket with Zapier Support: https://zapier.com/app/get-help

Hi there, ​@Reinvent 👋

I just came across this and wanted to check how you’re getting on, as I couldn’t see any tickets open with our Support team about this. Were you able to get this sorted?

If not, I’d definitely recommend reaching out to our Support team so that they can investigate this further. It would be good to have them check whether this is caused by a bug, if it is they can open up a bug report which will flag the issue to our engineers to fix it.

As a workaround in the meantime, if the events only have an attachment when a recording is generated then you could potentially use a Filter to make sure the Zap only continues if the Attachments field Does not exist (meaning no values exists for that field). It won’t prevent it from triggering twice for the same event but should stop it from continuing to run, the second time it triggers for that event. You can learn more about how to set up filters here: Add conditions to Zaps with filters

Looking forward to hearing from you! 🙂