Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hello, 

A few hours ago, all of our Zaps that are triggered via Acuity Scheduling started crashing. We have 8 or so calendars connected through different zaps. When an appointment is submitted: 1) The data is missing. 2) Regardless of which calendar you submit the appointment, all zaps fire and return errors. The expected action is just for the correct zap to fire (the one with the calendar where the appointment was submitted). 
Anyone else experiencing this issue right now?

YES. I experienced the same thing yesterday and I couldn’t find anything about it until I found your post. I unfortunately don’t have a solution, we’re currently looking into it internally. I emailed Zapier and hopefully their support gets back to us / replies here.

In short -- for us, it didn’t matter what appointment was scheduled on what calendar. The zaps ran anyway regardless of the calendar or appointment type configured within the zap. If Zapier couldn’t find a match with its given configuration, it dumped out whatever non-dynamic placeholder messaging we have it connect to in our Slack (that’s our next step: Acuity appointment scheduled → Slack channel notification). We have multiple zaps set up like this, so a lot was triggered and came through Slack. I have to disable all of our Acuity → Slack zaps until we can figure out a solution.

Hi there, ​@LongTail and ​@thomai! 👋

I did some checking and ​@LongTail, I see you also reached out to our Support team who identified that you were running into a bug was affecting the New Appointment, Appointment Cancelled, Appointment Rescheduled and New Product Order Acuity Scheduling triggers—which has since been resolved. 🎉

The issue was caused by a missing header in the webhooks that were sent to Zapier. This meant that while the Zaps did run, some data from the trigger step was missing. As you both noticed, the subsequent actions still processed but were missing data from the Acuity Scheduling triggers. The impact appears to have been limited to the period between 2025-03-27 23:30 UTC and 2025-03-28 11:00 UTC  so we recommend reviewing any Zap runs during that time that may have been affected. Acuity has resolved the issue moving forward, but unfortunately the data from past runs during that window can’t be recovered. Due to the missing headers and the risk of triggering duplicate actions, we’re unable to reprocess those Zap runs.

Really appreciate your patience while this was being resolved. Please do keep an eye on things and if you spot any further issues, do let us know! 

Terms & ConditionsAccessibility statement