I created a Zap that adds a new entry to a Notion database whenever a customer books an appointment. It was working fine but now several fields are being missed - even though it works on a test run. I’m not sure how to troubleshoot this?!
Best answer
Acuity to Notion Zap missing fields on live runs
Best answer by Fabi.SPL
the thing that'll tell you the answer in about two minutes: don't trust the test run at all, go into zap history and open one of the real runs that came out incomplete.
the test button doesn't pull a live booking, it replays a stored sample that zapier grabbed from acuity when you first set the trigger up. so a green test only means "this works on that one old booking," not "this works." that's exactly why it looks fine and the real ones aren't.
in the history, click into a run, then the notion step, and look at data in. that one screen splits your problem in half. if the field is already blank there, acuity never sent it and it's an upstream problem. if the field has a value in data in but it's not on the notion page, then notion rejected it and it's a mapping or field type problem.
if it's blank coming in, my money's on the acuity intake questions. those come through keyed per form, so a booking for a different appointment type doesn't have the same fields in the payload at all, and zapier quietly writes nothing instead of erroring. same deal if someone leaves an optional question empty. that's usually what the "several fields" thing turns out to be, it's not random, it's one category of booking.
if it's populated coming in but not landing, check the type on the notion side. dates arriving as text, numbers arriving as strings, and a select field getting a value that doesn't match an existing option are the three that get dropped silently rather than failing loudly.
were the incomplete ones all the same appointment type? if so that pretty much confirms it.
the thing that'll tell you the answer in about two minutes: don't trust the test run at all, go into zap history and open one of the real runs that came out incomplete.
the test button doesn't pull a live booking, it replays a stored sample that zapier grabbed from acuity when you first set the trigger up. so a green test only means "this works on that one old booking," not "this works." that's exactly why it looks fine and the real ones aren't.
in the history, click into a run, then the notion step, and look at data in. that one screen splits your problem in half. if the field is already blank there, acuity never sent it and it's an upstream problem. if the field has a value in data in but it's not on the notion page, then notion rejected it and it's a mapping or field type problem.
if it's blank coming in, my money's on the acuity intake questions. those come through keyed per form, so a booking for a different appointment type doesn't have the same fields in the payload at all, and zapier quietly writes nothing instead of erroring. same deal if someone leaves an optional question empty. that's usually what the "several fields" thing turns out to be, it's not random, it's one category of booking.
if it's populated coming in but not landing, check the type on the notion side. dates arriving as text, numbers arriving as strings, and a select field getting a value that doesn't match an existing option are the three that get dropped silently rather than failing loudly.
were the incomplete ones all the same appointment type? if so that pretty much confirms it.
+11- Community Manager
So glad you got it sorted
Hope you both have a great rest of your week!
The Zappy Awards are back
We're celebrating the Zapier builders making AI transformation happen. Winners get a published story on zapier.com, a trophy, $5,000 cash, and a feature at ZapConnect. Nominate yourself or a peer by July 24th, 2026.
Log in to the Community
No account yet? Create an account
Use your Zapier credentials
Log in with ZapierEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.