Skip to main content

​
Overview

With the Calendly integration, your voice agent can check available slots for your Calendly event types and book appointments directly. Calendly is a pure booking tool: the agent queries available slots and books the appointment chosen by the caller for the configured event type. Unlike the Outlook integration (OAuth only), Calendly offers two connection methods: the recommended OAuth flow and a personal access token (PAT). You connect Calendly once and then create the desired appointment tools from that connection.
Security: With the OAuth flow, you are redirected to Calendly to confirm access. The credentials are stored encrypted on the server and are only accessible to your account.

​
Setting up the integration

  1. Open the Tools page in the sidebar
  2. Click Create tool and select Calendly
  3. In the dialog, choose the connection method - Connect with Calendly (OAuth, recommended) or Personal access token

​
Connect with Calendly (OAuth)

Recommended. OAuth grants restricted access that can be revoked at any time, with rotating tokens.
  1. Select Connect with Calendly and click Connect Calendly - a new tab opens with the Calendly consent screen
  2. Follow Calendly’s OAuth flow and confirm the requested access
  3. After consenting, you automatically return to the Tools page and can select the event types

​
Personal access token (PAT)

For cases where OAuth is not an option (e.g. internal policies). Select Personal access token in the dialog and follow these steps:
  1. Sign in to Calendly and open Integrations & Apps > API and Webhooks (calendly.com/integrations/api_webhooks).
  2. Under Personal Access Tokens, click Generate New Token.
  3. Give the token a name, for example “AI Pro voice assistant”, and click Create Token.
  4. Copy the token immediately - Calendly shows it to you only once.
  5. Paste it into the Access token field below and click Connect.
This token grants full access to your Calendly account and does not expire. However, you can revoke it at any time on the same Calendly page. If you prefer restricted, easily revocable access, use “Connect with Calendly” (OAuth).

​
After connecting

Regardless of the connection method, the next steps are the same:
  1. Select one or more event types to create for the connected account
  2. Enter a default booking email - this is required for bookings, since an email address cannot be reliably captured by voice. Calendly sends its confirmation to this address
  3. Click Create
  4. Open the desired voice agent and switch to the Tools tab. Enable the Calendly tools for this agent there
Shared tools: Like all tools, the Calendly tools are available globally once created. You only need to enable them per voice agent in the Tools tab. Learn more under Tools.

​
Available tools

Up to two tools are created when connecting:

​
calendly_get_availability

Checks available slots for the configured Calendly event type. Typical use: the caller asks about available appointments before booking.

​
calendly_book_appointment

Books an appointment for the configured Calendly event type. Typical use: the caller has chosen an available slot and the appointment is booked.
Not tool parameters: Phone number and email are not tool parameters - the number comes from the call, the email from the stored default booking email.
Typical flow: Combine both tools - the voice agent first calls calendly_get_availability to list available slots, then books the appointment chosen by the caller with calendly_book_appointment (with the start time taken over unchanged).

​
Multiple event types

If the tool is configured with more than one Calendly event type, an additional required parameter event_type is injected into both schemas. With a single event type it is omitted - the event type is then bound server-side.
Booking not possible: For event types with required custom questions, callers would have to answer mandatory questions that the assistant cannot capture yet - bookings therefore fail. For bookings, use an event type without mandatory questions; availability checks still work. Such event types are flagged on the setup page.