Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Create a Calendly developer account: Go to https://developer.calendly.com, sign in with your Calendly account, and create a developer account if you don’t have one.
  2. Create an OAuth app: Create a new OAuth application, choose the environment (sandbox or production), and set the redirect URI to your callback (e.g. https://your-app.example.com/api/auth/calendly/callback).
  3. Set environment variables: Copy the Client ID and Client Secret into your .env as CALENDLY_CLIENT_ID and CALENDLY_CLIENT_SECRET.
  4. Verify access: Connect your Calendly account and run the Get Current User tool - note the returned user and organization URIs, which the list tools take as parameters.

​
Provider notes

  • Calendly OAuth does not use granular scopes - an access token can access everything the user can
  • A free Calendly account works for testing; event cancellation requires the connected user to own the event
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as calendly__get_current_user with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.