Calendly OAuth2 credential — “Please upgrade to Standard” error despite having Standard plan

[Funky_Cereal]

I am trying to connect Calendly to n8n cloud using OAuth2. I have a Calendly Standard plan (paid, confirmed active — next billing date June 26, 2026). I created an OAuth2 app in the Calendly developer console set to Production environment. The redirect URI, Client ID, and Client Secret are all confirmed correct and match exactly what n8n expects.

When I try to publish my workflow I get this error on the Calendly trigger node:

“Workflow could not be published. Error in node: Forbidden - perhaps check your credentials? Please upgrade your Calendly account to Standard.”

I cannot use API key authentication because Calendly deprecated that on May 31, 2025. OAuth2 is the only option available. My account IS Standard so I should not be getting this error.

error message:

Workflow could not be published. Error in node “New Calendly Booking — Alert Rashaad”: Forbidden - perhaps check your credentials? Please upgrade your Calendly account to Standard.

The Calendly trigger node is set to OAuth2, scope: user, event: invitee.created. The credential connects without error but the workflow fails to publish with the above message.

Share the output returned by the last node:

N/A — error occurs at publish/activation stage, not during execution.

Information on my n8n setup:

• n8n version: Cloud (funky-egos.app.n8n.cloud)
• Running via: n8n cloud
• Calendly plan: Standard (paid, active)
• OAuth app environment: Production

Has anyone successfully published a Calendly trigger workflow on n8n cloud recently after the API key deprecation? Is there something specific that needs to be configured in the Calendly OAuth app beyond Client ID, Secret, and redirect URI?

[achamm]

@Funky_Cereal does the email u OAuth’d through Calendly’s consent screen exactly match the email on the Standard plan? this error commonly fires when OAuth ended up authorizing a different Calendly account than ur paid one — happens if u have multiple Calendly accounts or hit the wrong Google login during the OAuth flow. quick check: in Calendly settings → Account, confirm the email there matches the email showing in n8n’s credential connection.

[tamy.santos]

hello, @Funky_Cereal, good morning!
I recommend recreating the Calendly OAuth application and making sure it includes the webhooks:write scope, in addition to the read scope necessary for invitee events. After that, I would reconnect the OAuth credential in n8n so that the token is generated again with the updated scopes.