That said, to actually be able to use that to cancel an event, you need to isolate that using something like the text parser in make. This pattern scheduled_events/([^']+) should isolate just the UUID of the scheduled event for you.
It appears like this is a bug in how Make is forming its API calls to Calendly, because the exact same API call in both Postman and on Calendly’s API site are working 100% perfectly.
It’s only when using Make’s “Calendly - Make An API Call” module does the error pop up.
@vendy@Michaela I’ve opened a support ticket on this problem — can this please be escalated to the Make engineers who are working on the Calendly modules?
I just realized that I can workaround this bug by using Make’s generic “HTTP — Make An API Call” module, but it would be great if Make could fix the Calendly modules!
Also, while we’re on the topic, it would be totally awesome if Make could create a native “Cancel an Event” module for Calendly (and support more of Calendly’s API, in general).
It’s great to hear that you opened a ticket regarding this issue. Our support team has all the tools to properly investigate this and, if necessary, escalate it to our developers. Please feel free to continue the conversation in your ticket.
I’m sure many other users would benefit from having a dedicated “Cancel and Event” Calendly module! I see that you’ve already submitted your idea to our Idea Exchange, which is fantastic.
I’m including a link to your suggestion here so that other community members can potentially upvote Calendly - Cancel Event.
Hey Scott! Really glad you got it all working! If you run into any additional issues with calendly or in general, feel free to let me know. Always happy to help!
That looks like a new question, could you please create a separate topic for this?
While it’s tempting to continue an existing thread, a more effective approach would be to start a new topic. It helps other community users to respond to your query, and keeps our space organised for everyone. If you start a new conversation you are also more likely to get help from other users. You can refer others back to a related topic by including that link in your question. Thank you for understanding and keeping our community neat and tidy.
The “New Topic” link can be found in the top-right of the header:
The problem that you’re having is because Make’s Calendly module entitled “Make An API Call” is broken and will NOT work for any API calls to Calendly.
I have reported this bug to the Make support team, but they have not yet fixed this bug in Make.
In the meantime, you will need to use the generic HTTP module to cancel your Calendly events.
(I am not at my computer right now — I am typing this on my phone — so I can’t provide you with a screenshot at the moment, but will upload one later today.)
Below are 2 screenshot examples of how you would cancel a Calendly event in Make using Make’s HTTP module.
Unfortunately, using the HTTP module is currently the ONLY way that you can cancel a Calendly even in Make, due to several different bugs in Make’s Calendly modules.
(Note that you would use your own bearer key for the authorization. You wouldn’t use the fake bearer key that I typed in below.)
If you have an authorisation header like that, may I suggest you use the HTTP Make an API Key Auth Request module?
This allows you to store the credentials securely, and also allows you to reuse the same key in another HTTP module without having to set it up/type it in again.
Also another benefit is that keys don’t get exported in scenario blueprints, while plaintext fields in module fields do.