Hi,
I’m using your webhook that react the scheduling of my users.
I pre fill via the URL the name and email of the user.
But if one user decide to change the email for something else, eventually it can crash the app. I can find a way around with an “if email exist” statement, but if the user decide to put an already existing email that is not his, the webhook will still process it and change things in the database of the user’s mail used.
There should be a way to go around that.
Thank you
+1
I’ve been in touch with Calendly about this over recent months - because we’re in the same position as OP whereby we prepopulate the details in the booking page, and users sometimes change the email address during the booking process to emails that do not exist in our database, resulting in webhook failure.
To make matters worse, Calendly is unwilling to offer an alerting mechanism for webhook failures, so I had to build our own alerting mechanism, and I need to respond to all failures within 24 hrs otherwise the exponential failover kicks in after 24hrs and disables the webhook entirely.
The long and short of it is that Calendly have been completely unwilling to work with us on this, and the account manager is completely unresponsive.
Hugely disappointing experience. I’m three years into an enterprise agreement and I can’t see us renewing given Calendly’s unwillingness to respond to customer needs.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.