> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/sales/calendly.md).

# Calendly

Calendly is a scheduling automation platform that lets individuals and teams manage availability, book meetings, and track scheduled events. Connecting Calendly to Coupler.io lets you export your scheduling data — events, invitees, availability, and more — to any destination automatically, without writing a single line of code.

**Why connect Calendly to Coupler.io?**

* Pull scheduled events, routing forms, and availability data into Google Sheets, Excel, BigQuery, or Looker Studio for reporting
* Send Calendly data to AI tools like ChatGPT, Claude, or Gemini to analyze booking trends or summarize activity
* Combine data from multiple Calendly users or event types using Append or Join transformations
* Keep your reports fresh on a recurring schedule — daily, hourly, or on a custom interval

## Prerequisites

* A Calendly account (Teams or higher plan recommended for organization-level entities)
* Admin or member access to the Calendly organization you want to pull data from
* A Coupler.io account (free plan available)

## Quick start

{% hint style="success" %}
If you want a full picture of scheduling activity, start with **Report: Events with invitees** — it combines event details and attendee information in a single export.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** From your Coupler.io dashboard, click **Add data flow**. Search for Calendly and select it as your source.
{% endstep %}

{% step %}
**Authorize your Calendly account.** Click **Connect** and sign in to Calendly via OAuth. Make sure you're logged in to the correct Calendly account (personal or shared organization) before authorizing — Coupler.io will connect to whichever account is active in your browser.
{% endstep %}

{% step %}
**Select a data entity.** Choose the entity you want to export — for example, **Report: Events with invitees**, **Scheduled events for organization**, or **Routing forms**. See the table below for a full list.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land: Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual run. Once it completes successfully, your data will appear in the destination you selected.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                            | What it contains                            |
| --------------------------------- | ------------------------------------------- |
| Scheduled events for organization | All booked events across your org           |
| Scheduled events for user         | Booked events for a specific user           |
| Event types for organization      | All event type configurations in your org   |
| Event types for user              | Event types belonging to a specific user    |
| List of users for organization    | All members in your Calendly organization   |
| Available time for user           | Availability windows for a specific user    |
| Busy time for user                | Blocked/busy time slots for a specific user |
| Routing forms                     | All routing forms in your organization      |
| Report: Events                    | Flat report of all events                   |
| Report: Events without teams      | Events excluding team-based ones            |
| Report: Events with invitees      | Events joined with invitee details          |
| Report: Questions and answers     | Invitee responses to booking questions      |
| Report: User availability         | Availability summary across users           |


---

# 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.coupler.io/sources/category/sales/calendly.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.