I have found a big issue with the “Updated Opportunity in Copper” Zapier link, and the problem seems to be on Copper’s side rather than Zapier’s. I suspect this applies to all the “Updated” zap hooks too.
When editing an opportunity record, each time a field is edited this counts as an “update”. This means editing even 2-3 fields can trigger half a dozen “update” events, and going through updating a whole record could mean 10-20 separate “updates” all within a few seconds of each other. I believe this is true for all content types.
That doesn’t sound like an issue until you get to Zapier and realise that every single one of these tiny changes is triggering a Zapier hook and burning through another bunch of tasks. I estimated that one Zap to update a Google sheet when an opportunity is updated could burn through our entire Zapier task allocation in just a few days from pretty light usage because Copper is triggering zap tasks for absolutely everything.
So is there a way to change this so that “update” triggers are only sent every 5 minutes? That way we can complete all the changes to all the fields and then Zapier will get the whole lot in one go?
(Zapier can’t do anything about this because the problem is being caused by Copper sending so many update actions, not their processing of them, and setting up filters would still burn through our task allocation. Adding a tag also won’t help because that would stop the records syncing after the first time, whereas we want to be able to update records on an ongoing basis.)