OAuth providers
Calendly
Set up Calendly OAuth for scheduling automation and event management
Overview
Section titled “Overview”Connect your users to Calendly for scheduling automation, event management, and availability tracking.
| Property | Value |
|---|---|
| Provider ID | calendly |
| Category | Productivity |
| PKCE | Supported |
| Token refresh | Automatic |
| Redirect URI | Shown in Developer Portal |
Step 1: Create a Calendly OAuth App
Section titled “Step 1: Create a Calendly OAuth App”Sign up for the Calendly Developer Portal
Go to developer.calendly.com and sign up with GitHub or Google. The developer account is separate from a regular Calendly user account.
Create an application
Open My OAuth Apps and click Create New App.
Configure the application
Choose:
- Application type (web or native)
- Environment — Sandbox for development (HTTP localhost allowed), Production for live data (HTTPS only)
Add the redirect URI
Add the Redirect URI from the Developer Portal to the Redirect URI field.
Get credentials
Copy the Client ID, Client Secret, and Webhook signing key. The secret and signing key are only displayed once.
Step 2: Add to Alter Vault
Section titled “Step 2: Add to Alter Vault”Open the Developer Portal
Go to portal.alterauth.com and navigate to the application.
Add Calendly provider
Go to OAuth Providers > Add Provider > Calendly.
Enter credentials
- Client ID: Paste your Calendly Client ID
- Client Secret: Paste your Calendly Client Secret
Select scopes
Choose the scopes the application needs.
Save
Click Save. The provider is now active.
Available Scopes
Section titled “Available Scopes”| Scope | Description |
|---|---|
default | Access to Calendly scheduling data including events, invitees, and availability |
- The Calendly developer account is separate from a regular Calendly user account — sign in with GitHub or Google.
- Use the Sandbox environment for development; HTTP localhost redirect URIs are allowed there. Production requires HTTPS.
- Calendly OAuth recommends PKCE with the S256
code_challenge_method(RFC 7636). - The Client Secret and Webhook signing key are revealed only at creation — save them immediately.