Title: Zapier triggers for individual appointments: created, updated and deleted, including ones generated by recurring services
The problem
ZenMaid’s Zapier triggers cover recurring services (created, updated, cancelled), but nothing fires for the individual appointments a recurring service generates. For a business where about a third of cleanings are recurring visits, those visits never reach Zapier. We can only see them through a manual CSV export, so any automation built on Zapier is incomplete.
What we need
Appointment Created, firing for every new appointment, including ones generated from a recurring service.
Appointment Updated, firing when an appointment’s date, time, price, cleaner or paid status changes. Today only the status trigger exists, and it doesn’t fire when a visit is moved.
Appointment Deleted. Skipping a recurring visit is done by deleting the appointment. That is not a status change, so nothing fires today and the visit just disappears from every data source.
A payload that includes the appointment ID, the recurring service (subscription) ID, date and time, price, paid flag and status, so we can match appointments to invoices and payments.
Why it matters
Without these, you can’t keep an accurate list of scheduled cleanings, reconcile invoices and payments against what was actually scheduled, or notice skipped or moved visits. The only workaround is a manual export, and ZenMaid has no scheduled export.
Related: an Open API with webhooks for appointment events would also solve this, so we’d happily use that instead when it’s available.
Pending