At a glance
- Availability: Experimental (how to enable).
- Auth: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Docs: https://developer.calendly.com/api-docs
Credentials
Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.Setup
- 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.
- 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).
- Set environment variables: Copy the Client ID and Client Secret into your .env as CALENDLY_CLIENT_ID and CALENDLY_CLIENT_SECRET.
- 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.
- 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
Tools
Example prompts
- List my upcoming Calendly events with their times and invitees.
- Show my active Calendly event types and their scheduling URLs.