We are building a scheduling app. A user is able to schedule an event and we send out an email notification 30 mins before the event start time. When a new event is created, we create a Zap with delay until set to 30mins before event start. This works great.
However, when a user deletes or modifies the event 30 mins before the event start, we need to delete the delayed task so that the email is no longer sent. How is this possible ?
Also, is there a better approach to handle this use case ?
+14
What scheduling app are you using? (e.g. Calendly)
What calendar app are the events logged in? (e.g. GCal)
This probably needs to be split into separate Zaps.
We are any third party scheduling app or calendar. We are trying to achieve some minimal scheduling capability within out current app that is built on Adalo.
+14
Ideally there are separate webhooks fired for each type of event.
Example: Appointment Created, Appointment Canceled, Appointment Rescheduled.
Check out other Calendar apps such as Calendly, Acuity, etc.
I’m trying to figure out the same thing…
The trigger would be that a meeting is canceled in ScheduleOnce (that’s easy), but then how does Zapier delete that specific Waiting task (created by a Delay), so that the email pre-meeting does not get sent out??
+14
You can’t delete a pending delayed Task.
Better to structure separate Zaps in this case.
I’m trying to figure out the same thing…
The trigger would be that a meeting is canceled in ScheduleOnce (that’s easy), but then how does Zapier delete that specific Waiting task (created by a Delay), so that the email pre-meeting does not get sent out??
Hi,
you solve it?
I have the same situation
+9
Hey
Just wanted to circle back on this thread. To acknowledge Troy’s suggestion, some scheduling apps have available triggers such as Appointment Created, Appointment Canceled, and Appointment Rescheduled.
If you don’t have those capabilities and you are utilizing Google Calendar, you may be able to utilize the “Find Event” action after the delay followed by a Filter step to check if the event still exists. The Filter condition would be something along the lines of “If > Event ID > Exists”. If it does, the Zap will take the next step of sending out the message.
Does that help with what you’re looking to achieve here? What other questions/issues are coming up for you around this? Let us know and we’d be happy to continue guiding y’all in the right direction here!
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
