> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telli.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Calendly

> Connect Calendly to telli so agents can check availability, book meetings, and fill Calendly booking questions during calls.

<img src="https://mintcdn.com/telli/B1-jcrEXZ5AA-uwV/images/integrations/telli-calendly-light.svg?fit=max&auto=format&n=B1-jcrEXZ5AA-uwV&q=85&s=9ef8a6d8fe8431c90aa9bca5b1a2bc08" className="block dark:hidden" alt="telli + Calendly integration" width="1200" height="360" data-path="images/integrations/telli-calendly-light.svg" />

<img src="https://mintcdn.com/telli/B1-jcrEXZ5AA-uwV/images/integrations/telli-calendly-dark.svg?fit=max&auto=format&n=B1-jcrEXZ5AA-uwV&q=85&s=e7babb771fb42f3371dfa2fa995de27c" className="hidden dark:block" alt="telli + Calendly integration" width="1200" height="360" data-path="images/integrations/telli-calendly-dark.svg" />

## Overview

Calendly is configured per agent so each workflow can use the right event type, booking link, and booking-field mapping.

This works well when different agents book different meeting types or route to different teams.

## Before you start

* A telli agent that should book appointments
* A Calendly account and event type
* A Calendly API key with at least `users:read`, `organizations:read`, `event_types:read`, `availability:read`, and `scheduled_events:write`

<Note>
  Booking through the Calendly API requires a paid Calendly plan. Booking is not possible via the API on the Free plan, even with the
  correct API key scopes.
</Note>

## Set up Calendly in telli

<Steps>
  <Step title="Open the agent">Open the agent you want to configure in telli.</Step>
  <Step title="Choose Calendly">In **Calendar Integration**, select **Calendly**.</Step>

  <Step title="Add your Calendly credentials">
    Create a Calendly API key with at least `users:read`, `organizations:read`, `event_types:read`, `availability:read`, and
    `scheduled_events:write`, then add it and select the Calendly event type that should be used for bookings.
  </Step>

  <Step title="Configure booking fields">
    Open the settings for the selected event type and map the booking questions you want telli to fill automatically.
  </Step>

  <Step title="Save the agent">Save the agent so telli can use the selected Calendly setup during calls.</Step>
</Steps>

## Booking fields

When connecting Calendly, you can configure booking fields to automatically fill the custom questions on your Calendly event type during booking.

Each booking field maps a Calendly question to a value source.

| Type                 | Description                                                                          | Example                                    |
| -------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------ |
| **Constant**         | A fixed value, always the same                                                       | Brand name, company name                   |
| **Contact property** | Resolved from the contact's data. If not available, the agent asks the caller for it | Phone number, email, first name            |
| **System variable**  | Resolved from internal system data using a path expression                           | Contact ID, timezone                       |
| **LLM parameter**    | Collected by the agent during the conversation                                       | Reason for appointment, preferred language |

## How it works

* telli uses the configured Calendly event type for that agent
* Booking fields are resolved automatically during booking
* Contact properties and constants are filled without extra conversation
* LLM parameters prompt the agent to collect missing information from the caller

<Note>
  Every required custom question on your Calendly event type must have a corresponding booking field configured, otherwise the booking will
  fail. Optional questions without a mapping are skipped.
</Note>