> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/calendly.md).

# Calendly

## OAuth app properties

| Property                | Value                                                                                                                    |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Multi-tenant**        | **Yes.** One app gets a token for each Calendly user who authorizes it. Use a **Production** app for real customer data. |
| **Vendor review**       | **None.**                                                                                                                |
| **Review time**         | Not applicable.                                                                                                          |
| **Users before review** | No limit.                                                                                                                |
| **App owner**           | A Calendly developer account, separate from a Calendly user account.                                                     |
| **Regions**             | One app works worldwide.                                                                                                 |
| **Client secret**       | No expiry documented. It is shown only once and cannot be viewed again, also when you edit the app.                      |
| **Rate limits**         | No per-app limit published. Token requests: at most 8 per user per minute.                                               |
| **Checked**             | 2026-11-13                                                                                                               |

**Limitations**

* A refresh token is single use (enforced from 2026-08-31). Each refresh returns a new one; reusing an old one fails with `invalid_grant` and the user has to connect the account again.
* A connected account also stops working when the user changes their Calendly login email, password or login method, because Calendly then revokes the tokens.
* A new app has no API access until scopes are selected; select at least one when you create the app. The connector does not send a scope parameter, so select the scopes the components need in the app.
* A few API endpoints work only for Calendly Enterprise accounts. An organization-scope webhook needs a user who is an organization admin or owner.

Sources: [Creating an OAuth app](https://developer.calendly.com/docs/authentication/creating-an-oauth-app), [Scopes](https://developer.calendly.com/docs/authentication/scopes), [Refresh token rotation](https://developer.calendly.com/refresh-token-rotation-guide), [FAQ](https://developer.calendly.com/frequently-asked-questions). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Calendly – Connector Configuration

### Step 1: Create a Developer Account & First Application

* Create a Calendly Developer account: [Create a Developer Account](https://developer.calendly.com/create-a-developer-account)
* Go to [Calendly Console Apps](https://developer.calendly.com/console/apps) and sign up.

> ⚠️ **Note**: This is **not** your Calendly user account. It’s a separate developer account.

***

### Step 2: Register Your OAuth Application

1. **Create a new OAuth application**:
   * Provide a **name** for your application.
   * Select the **kind of application**:
     * Web
   * Select your **environment**:
     * Sandbox (recommended for development)
     * Production (use when going live with customer data)

***

### Step 3: Set Redirect URI

* **Sandbox**: HTTP with `localhost` domain allowed\
  Example:

  ```http
  http://localhost:1234
  ```
* **Production**: Must use HTTPS.

👉 You can add multiple redirect URIs, separated by commas.\
👉 For Appmixer, set the redirect URI to:

```http
https://[YOUR_API_BASE]/auth/calendly/callback
```

Example:

```http
https://api.appmixer.com/auth/calendly/callback
```

![alt text](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-54fd09de2780f36b360c837dd1171031ff18e06f%2FcalendlyImage-1.png?alt=media)

***

### Step 4: Copy Your Credentials

Once the app is created, you’ll see:

* **Client ID**
* **Client Secret**

⚠️ **Important**: These values will only be shown once. Copy them immediately!

***

### Step 5: Edit Your Application

* To edit an existing OAuth app in Calendly:
  * Click the menu icon → **Edit**.
* Editable attributes:
  * Application Name
  * Kind of App
  * Environment Type
  * Redirect URI

⚠️ **Note**: Client Secret and Webhook Signing Key **cannot be retrieved again** after creation.

## Backoffice configuration

Configuration ID: `appmixer:calendly` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Client ID of the Calendly OAuth app registered above. Not needed when Calendly is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client secret of the same app. Not needed with the Auth Hub.

![alt text](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-8639225a4d06482d73175ce1690db20e802f4311%2FcalendlyImage.png?alt=media)

![alt text](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-210dd617862824286645a9c4a3d6277d248f8e88%2FcalendlyImage-2.png?alt=media)

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:calendly -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/calendly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
