This trigger burned through hundreds of tasks this billing cycle when no meaningful changes (for my use case) occurred to the event. I'm looking to only run the zap when a new event is scheduled or when the start date/time is updated for an existing event.
I’ve filtered out runs for recurring events using a filter, but since then the zap fired a ton of times for an event that had many guests on it. I believe it's firing when guests confirmation status changes.
Any suggestions?





