I’ve been working with Make.com’s HTTP connector to fetch booking form responses from Calendly’s API. The problem I’m facing is that the API response doesn’t include all the form fields that users completed when they scheduled their appointments.
Current Setup
I’m making requests to the invitees endpoint for scheduled events, but the response data seems incomplete. Some of the form responses that I know were submitted by users are not appearing in the API response.
What I’ve Observed
The form_responses section in the API output is either showing partial data or completely empty, even when I can confirm through the Calendly dashboard that users did fill out those fields during booking.
Looking for Solutions
Has anyone managed to successfully pull complete booking form data through Make.com? I’d really appreciate any guidance on proper configuration or alternative approaches that might work better.
Had this exact problem last month building a client workflow. It’s usually API permissions or timing issues. Check that your Calendly token has event and invitee read permissions enabled. Also, don’t query the API right after someone books - I added a 2-3 minute delay before the API call and that fixed most of the incomplete data problems. Calendly needs time to process and store form responses. Worth checking if you’re hitting rate limits too - they can cause partial responses without obvious error messages.
Make.com’s HTTP modules suck for complex API stuff like this. I’ve hit this exact Calendly form issue tons of times.
Ditch Make.com and try Latenode instead. It handles API pagination and data mapping way better.
Latenode lets you build proper error handling that catches incomplete form responses and retries automatically. Their Calendly integration also fixes those timing problems WhisperingWind mentioned.
I built a similar booking sync last year - Latenode grabbed all the form fields every time. The visual builder makes mapping response data super easy.
Your automation will actually work reliably and you’ll stop getting those weird partial responses.
Been fighting Calendly API quirks for years. The form responses issue killed me on a project last year.
Your problem’s likely the event type scope in your Make.com HTTP request. Most people query individual events but miss that form responses live at the org level in Calendly’s structure.
Hit the organization events endpoint first, then drill down for full invitee data. The regular invitees endpoint cuts off custom field responses on purpose.
Check your Calendly webhook settings too. If you’ve got webhooks enabled for the same events you’re polling, they mess with each other and cause sync issues.
One more thing - Calendly screws up special characters between dashboard view and API responses. When users enter quotes, apostrophes, or emojis in forms, the API sometimes returns null instead of actual text.
I built a fallback system that checks both events and invitees endpoints, then merges responses to get complete data.
Had the exact same frustrating issue about six months back while building automation for a client. Turns out it wasn’t the API call - it was the event type config. Check if your form fields are set as required in Calendly’s event type settings, not optional. Optional fields get dropped during API transmission if they have weird characters or are too long. Also, if you’re using webhooks, try pulling data immediately after booking instead of polling the API later. I found webhooks capture way more complete form responses - the API seems to compress or filter out data in follow-up calls. Test both methods to see which gives you cleaner data.
yea, I dealt with that too! Just make sure ur scenario is using the correct endpoint. Also, sometimes custom fields won’t show unless u specify ‘include’ in the request. took me a while to figure it out, but it worked after that.