help to book appointment using n8n

Hi ​@iskonaamdu21558 - Thanks for reaching out!

I haven’t seen many people utilizing n8n for their Calendly integrations. More commonly these are setup through Zapier or make.com. which we do have some documentation for.

If you’d like to use n8n, we have a getting started guide with our API that you can read here: https://developer.calendly.com/getting-started

Let me know if you have any questions!

Hi ​@iskonaamdu21558 — this functionality is coming soon! We’re building a new Scheduling API that will let you schedule meetings on an invitee’s behalf, similar to selecting a time and filling out the form on the Calendly booking page. To be notified when it goes live, sign up for a developer account at developer.calendly.com which will also subscribe you to our developer newsletter.

​@MikeKimelblat how can I know when this is available? can i subscribe to product updates newsletter or something?

Hi ​@Faiyaz! To be notified when it goes live, sign up for a developer account at developer.calendly.com which will also subscribe you to our developer newsletter.

Thanks ​@David! You can also now subscribe to the developer newsletter directly here: https://calendly.com/landing/api-updates 

Hi ​@Faiyaz and ​@iskonaamdu21558 ​ - this is now available! The API documentation for this endpoint can be found here: https://developer.calendly.com/api-docs/p3ghrxrwbl8kqe-create-event-invitee.

Hey, I’m trying to use new Invitee API:

https://developer.calendly.com/api-docs/p3ghrxrwbl8kqe-create-event-invitee

I created new OAuth App and logged in via and acquired Bearer token.

https://developer.calendly.com/api-docs/be9b32ef4b44c-get-access-token

But when I’m trying to use Bearer token, Invitee API still throws an error 401:

{
  "title": "Unauthenticated",
  "message": "The access token is invalid"
}

Hey ​@MikeKimelblat , could you please look into it?

Hi ​@Nikolai - if you are just testing things out, I would recommend creating an account on calendly.com and using a Personal Access Token (PAT). Adding ​@Austin and ​@Cameron from our dev support team here as well who will be best to assist you with getting up and running.

Hey ​@Nikolai I work on our Developer Support team here at Calendly and I’ve helped several of our customers get unblocked from authentication errors using N8N. Unfortunately there doesn’t seem to be much we can do on our side specifically, and N8N should be aware of some sort of issue with the way they store and utilize the PAT during their requests. In all of my past cases, our customers had success reaching out directly to N8N support to receive guidance on how to make sure it is being used in the correct format. 

Would you be able to share what your findings are once they resolve it for you? I’d love to log things internally so we can assist more of our customers in the future.