# Calendly

![calendly_logo_horizontal_color.png](https://assets.relyanceuat.xyz/images/docs/34562864010509/34562864009741.png)
Calendly is a modern availability and booking application used to schedule meetings, appointments, and events. Its goal is to eliminate the problematic back-and-forth for individuals and organizations when trying to nail down times. When connecting is easy, your teams can get more done.

In order to integrate Calendly with Relyance AI you will need to create a Calendly **Personal Access Token**.

**In Calendly:**

1. Login to your Calendly account.
2. Navigate to the page: [https://calendly.com/integrations](https://calendly.com/integrations)
3. Here you will select the **API & Webhooks** tile
4. This will bring you to where your personal access tokens are stored.
5. Select **Generate New Token**.
6. Give the token a meaningful name and select **Create token**.

![Calendly-new.png](https://assets.relyanceuat.xyz/images/docs/34562864010509/34562864009869.png)

![Calendly-3.png](https://assets.relyanceuat.xyz/images/docs/34562864010509/34562816729997.png)

**In the Relyance AI application:**

1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Calendly** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, Please choose the authentication method as **Custom** and provide the following information retrieved from the **In Calendly** section and click on **Authenticate**.
10. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g.,Very Low) offer more coverage but may produce false positives, while higher sensitivity (e.g., very High) provides greater accuracy but less coverage.
11. Review the configuration summary from the **Completion** section and click on **Finish.**
12. Confirm the integration Status reflects **Connected.**

![Screenshot 2025-11-04 144454.png](https://assets.relyanceuat.xyz/images/docs/34562864010509/40851963402509.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562864010509/34562921396749.png)

![Screenshot 2025-11-04 144609.png](https://assets.relyanceuat.xyz/images/docs/34562864010509/40851914456461.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562864010509/34562921397773.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34562864010509/34562921397901.png)

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "calendly" {
  vendor = "calendly"
  name   = "<your connection name>"

  auth = {
    method = "access-token"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      access_token = var.calendly_access_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->