Calendly Trigger node returns ‘resource not found’ when using Personal Access Token credential on version 2.13.3. Also returns ‘required_scopes’ error with OAuth2. All scopes are correctly set and I am on a Standard (paid) plan Is there a fix or workaround?"
@TanyaRamesh the PAT path is completely broken — the node still sends requests to calendly.com/api/v1/hooks which Calendly shut down, that’s your “resource not found”. It’s a known bug: Calendly: Personal Access Token auth broken - routes to deprecated v1 API · Issue #27788 · n8n-io/n8n · GitHub. For OAuth2 make sure you have both webhooks:write adn the matching read scope for each event family you subscribe to (e.g. default:read for invitee events). If that still fails, use a generic Webhook node and create the subscription via HTTP Request node hitting https://api.calendly.com/webhook_subscriptions with a Bearer token directly
If you’re encountering issues retrieving event types in your Calendly node, it might be a configuration detail rather than a bug now.
We are currently running this integration on self-hosted v1.27.7, and it is performing reliably. We encountered a similar error recently and found that the solution was related to API permissions.
The Fix: Update Your Scopes
To resolve this, ensure you have added the users:read scope within your Calendly App configuration.
Why this matters: The n8n Calendly node often needs to retrieve specific user information as a dependency before it can successfully fetch the available event_type data. Without the users:read permission, the initial handshake fails, leading to the error you’re seeing.