I tried with Calendly and have this error. Anyone know how to fix it?
I run “Calendly” as a module only and got this error.
Thanks.
Check the input from the webhook is the data accurate?
Welcome to the Make community!
This looks like a bug on the backend of this module. Looks like Calendly renamed eventType to EventType, breaking the value as Make is still using lowercase e in eventType.
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. Make support has access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing potentially sensitive information about your account, scenario variables, and output bundles might not be advisable as it is a public forum.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free Make account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
Thank you so much. I am not sure how to debug this problem.
I was also thinking it might be a bug from Make’s end.
I will log a ticket now.
Hello everyone @here thank you very much for raising this in the community.
I just wanted to confirm that this is a bug on our end when making an API call. The issue has been escalated to our dev team for investigation.
In the meantime, we recommend using the ‘Make an API call’ module and passing the request as a JSON object to the following endpoint
/scheduling_links
We apologize for any frustration and disruptions this may have caused.
Thank you for your patience and understanding 
2 Likes