> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/calendly-integration-setup.md).

# Calendly Integration Setup

### Getting Started

Use this guide to connect Calendly to your BalkanID tenant. You will need a personal access token from Calendly and access to the Integrations section in BalkanID.

#### Requirements:

Before you begin, collect the following value from Calendly:

* **Personal Access Token**

{% hint style="info" %}
The personal access token must be generated by a Calendly **Owner** or **Admin**. Tokens created by a member with the User role cannot read organization-wide membership, and the integration will not be able to extract data.
{% endhint %}

### Configure Calendly within your BalkanID tenant

1. To create the Personal Access Token, sign in to Calendly as an Owner or Admin.
2. Navigate to **Integrations & apps** > **API & Webhooks**, then select **Generate new token** under Personal access tokens.
3. Enter a name for the token so you can identify it later, then select **Create token**.
4. Grant the token the scopes listed under [Integration Scopes](#integration-scopes) below. A newly created token has no API access until scopes are explicitly granted.
5. Copy the token and store it somewhere safe. Calendly displays it only once and cannot show it again after you close the dialog.
6. In BalkanID, go to the **Integrations** page and select **Add integration**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FGCYcbPPqjS2wlTICYWj3%2Fcalendly-add-integration.png?alt=media" alt="The BalkanID Integrations page with the Add integration button in the top right"><figcaption><p>Integrations</p></figcaption></figure></div>

7. Search for Calendly, select it, and click **Next**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FVyOImmgbu4FE8vDF0zB1%2Fcalendly-connect-application.png?alt=media" alt="The Connect a new application step with Calendly selected"><figcaption><p>Connect a new application</p></figcaption></figure></div>

8. Under **Select Extraction Type**, keep **Direct Configuration** selected and paste your token into the **Personal Access Token** field, then click **Next.**

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F98Esn6SZI2x4Dfk8Fgyv%2Fcalendly-direct-configuration.png?alt=media" alt="The Direct Configuration section showing the Personal Access Token field"><figcaption><p>Direct Configuration</p></figcaption></figure></div>

9. Fill **Optional Configuration**, if required.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FZbipc8nl8LTFl5YsVIaj%2Foptional-configuration.png?alt=media" alt="The Optional Configuration step showing Reviewer Settings and fulfillment options"><figcaption><p>Optional Configuration</p></figcaption></figure></div>

10. Once you have filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the Integrations page. When data is available, the integration Status column will read **Connected** and the integration Message will read **Data available**.

### Integration Scopes

| Read Only Scopes                                                                                                            | Lifecycle Management Scopes |
| --------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| **organizations:read** — Reads your organization, its members and their roles, and any pending invitations.                 | N/A                         |
| **groups:read** — Reads groups and group memberships. Groups are available on the Professional, Teams and Enterprise plans. | N/A                         |
| **users:read** — Reads the profile of the account that owns the token, which identifies the organization to extract.        | N/A                         |

### Keeping the connection active

Calendly revokes a personal access token when the account's email address, password, or sign-in method changes. If any of those change, generate a new token and update it in BalkanID. We recommend creating the token from a dedicated administrator account so that routine credential changes do not interrupt the integration.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/calendly-integration-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.