Best answer

why is my zap using so many tasks?

  • 30 August 2021
  • 4 replies

I created a zap to add an additional attendee to every new Google Calendar event. The zap worked fine. Unfortunately, the zap used > 1,000 tasks per day. I ran out of tasks now and I need to pay to upgrade to a better plan :( Before I do so, I would like some help to figure out why it used so many tasks. I have certainly not added thousands of new events to the calendar.

The trigger is “New or Updated Event in Google Calendar.” The action is “Add Attendee/s to Event in Google Calendar.” In the “Set up Action” section I selected the same calendar as in the one in trigger. For the “Event” field I selected “Custom” then I selected “1. ID 099rjt4hrulvb0pa2o700kutk.” 

I was particularly puzzled by the 099rjt4hrulvb0pa2o700kutk string as it looked as if it would be a specific event. That said, the zap worked, so I think that part might be ok. 

Can someone helped me figure out how to prevent this zap from hogging resources?




Best answer by christina.d 30 August 2021, 22:14

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Userlevel 7
Badge +14

Hi @andresmh 

The trigger is “New or Updated Event in Google Calendar.”

You essentially created an infinite loop:

Everything the Zap action ran, it’s updating the GCal Event, which is then retriggering the Zap.

Userlevel 7
Badge +9

Thanks for reaching out, @andresmh! Troy is correct and that is an excellent resource to check out for learning about Zap loops. That said, it looks like you were able to chat with my teammate Cameron in support too, which is perfect. I wanted to post their response here just in case it helps others. 🙂

I've reviewed your Zap and can see that it was originally using the Google Calendar > Event Updated trigger which created a Zap loop. A Zap loop occurs when an action in a Zap causes the same (or another) Zap to trigger endlessly.
In this case, every time your Zap added an attendee to an event this caused the same Zap to trigger due to the event being updated. I can see the Zap has been updated to instead trigger from new events which should resolve the Zap loop and allow the Zap to only trigger on newly created events.


Thank you all!

Userlevel 6
Badge +6

Hello @andresmh ,


Troy and Zapier team have already answered to your query. I can give a solution on how you can save tasks Your current Zap is New/Update in Calender Event → Add Attendees in Calender Invite


You can add 1 more step in the end of adding attendees in Storage By Zapier. Whenever the Calender invite updates, we will search for a value in Storage by Zapier and Check if new attendees are same as that of previous.


The updated Zap will be below - 


New/Update in Calender Invite → Search Attendees in Storage by Zapier → Filter (Attendees in Trigger) not Equals (Attendees in Storage by Zapier) → Add attendees in Google Calender