Cancel Event on Calendly API

Hello how are you?!

I’m having a lot of trouble requesting a request to cancel a Calendly event via API on n8n. In the API documentation there is the possibility of importing the cUrl (Cancel Event | Calendly Public API), but even performing the import I get the following message “ERROR: The resource you are requesting could not be found” (a print of the output follows).

Here I am using a fixed UUID of a scheduled event in my calendar!

It is important to say that I contacted Calendly support asking if the API was working normally and they assured me that it was and sent me the following link to check the API:

Could someone help me with this request, please?!

{“status”:“rejected”,“reason”:{“message”:“404 - "{\"title\":\"Resource Not Found\",\"message\":\"The server could not find the requested resource.\"}"”,“name”:“Error”,“stack”:“Error: 404 - "{\"title\":\"Resource Not Found\",\"message\":\"The server could not find the requested resource.\"}"\n at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11)\n at IncomingMessage.emit (node:events:525:35)\n at IncomingMessage.emit (node:domain:489:12)\n at endReadableNT (node:internal/streams/readable:1358:12)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)”}}

n8n version: 0.212.0
Database: SQLite
Running n8n with the execution process: own(default)
Running via Docker

Hi @rfdepauli, I am sorry you’re having trouble. This appears to be an error coming from Calendly and I am not 100% sure why this would be thrown - your request appears to match what they expect.

Is this API request working for you outside of n8n? For example when using curl, Insomnia or Postman?

On another note, it seems you originally included your API token in your request. I’ve redacted your post to hide it, but you probably want to revoke it and create a new one for security reasons.

Thanks for the reply and for hiding the token, @MutedJam ! It really was my fault!

I managed to cancel an event through the API, but for that I needed to use a List Events request from a platform called to fetch the UUID of the scheduled event (Calendly API - NoCodeAPI api/). This information was previously expressed in the Calendly Trigger output, but that has changed. Also, on the credential quickly expires and the API request on n8n ends up giving an error. So I’d like to make the request described in the Calendly documentation (Calendly Developer), but I’m having trouble with it.

I contacted Calendly support and they informed me that probably n8n already changed API v1 to API v2. I’m a veterinarian, and I’m using n8n to create an automation on Whatsapp for attending and scheduling my appointments. I’ve already learned a lot of things that I never thought I’d be able to do, but when my n8n flows were working perfectly this change from API v1 to API v2 was made and all my flows stopped working! On the Calendly website itself, it is being informed that API v1 will stop working until 06/30/2023 and will be replaced by API v2.

Because of this, the Calendly Trigger output data has changed and is now limited, as it still uses the credential by API v1. Calendly support gave me all the information for creating a new API v2 credential such as Client Secret, UID (CLIENT ID), REDIRECT URI and WEBHOOK SIGNING KEY. However, I’m having a lot of trouble creating the Calendly credential on n8n via API v2.

Could you help me with this, please?! This is very important to me! :pray:

Hi @rfdepauli, thanks so much for sharing these details. n8n currently uses Calendly’s API v1, but there is an open pull request to get this updated to v2:

From checking the internal ticket for the review I can see our product team considers this to be a low priority issue. So I reckon this will take a while I am afraid :frowning:

Edit: After checking this with @Jon this request might actually get a review very soon, at which point you would be able to use Calendly’s API v2 webhooks through a trigger node :slight_smile:

How sad to know that this possibility does not exist yet, @MutedJam . The integration with Calendly via n8n is still limited until there is a solution!

Anyway, I’m glad to hear that there’s already an internal request for the Calendly Trigger update via API v2 with @Jon !

Is there any temporary alternative to perform this request with API v2 until this solution?