> 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

Export Calendly scheduled events, event types, and availability data to Google Sheets, BigQuery, or Looker Studio via Coupler.io.

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 %}

## Calendly data overview

Calendly exposes scheduling data across three broad categories: **event and booking data**, **availability data**, and **organization management data**. Reports are pre-joined views that combine multiple entities for easier analysis.

## Entities and reports

| Entity                            | Level | Date range filter |
| --------------------------------- | ----- | ----------------- |
| Scheduled events for organization | Org   | No                |
| Scheduled events for user         | User  | No                |
| Event types for organization      | Org   | No                |
| Event types for user              | User  | No                |
| List of users for organization    | Org   | No                |
| Available time for user           | User  | Yes               |
| Busy time for user                | User  | Yes               |
| Routing forms                     | Org   | No                |
| Report: Events                    | Org   | Yes               |
| Report: Events without teams      | Org   | Yes               |
| Report: Events with invitees      | Org   | Yes               |
| Report: Questions and answers     | Org   | Yes               |
| Report: User availability         | User  | Yes               |

## Scheduled events

#### Key fields

| Field                 | Description                     |
| --------------------- | ------------------------------- |
| `uri`                 | Unique identifier for the event |
| `name`                | Event type name                 |
| `status`              | Active, canceled, etc.          |
| `start_time`          | Scheduled start (UTC)           |
| `end_time`            | Scheduled end (UTC)             |
| `event_type`          | Link to the event type record   |
| `location`            | Meeting location or video link  |
| `created_at`          | When the event was booked       |
| `updated_at`          | Last modification timestamp     |
| `cancellation_reason` | Reason if canceled              |

## Event types

#### Key fields

| Field            | Description                          |
| ---------------- | ------------------------------------ |
| `uri`            | Unique identifier for the event type |
| `name`           | Display name of the event type       |
| `duration`       | Meeting length in minutes            |
| `kind`           | Solo, group, round robin, etc.       |
| `slug`           | URL slug used in booking links       |
| `active`         | Whether the event type is enabled    |
| `scheduling_url` | Public booking URL                   |

## Invitees (via Reports)

#### Key fields available in Report: Events with invitees

| Field                                        | Description                               |
| -------------------------------------------- | ----------------------------------------- |
| `invitee_name`                               | Invitee's full name                       |
| `invitee_email`                              | Invitee's email address                   |
| `invitee_timezone`                           | Timezone selected at booking              |
| `invitee_created_at`                         | When the invitee booked                   |
| `utm_source` / `utm_medium` / `utm_campaign` | UTM tracking parameters passed at booking |
| `questions_and_answers`                      | Responses to custom booking form fields   |

## Availability and busy times

#### Key fields

| Field        | Description                             |
| ------------ | --------------------------------------- |
| `user`       | User the availability belongs to        |
| `start_time` | Start of available or busy window       |
| `end_time`   | End of available or busy window         |
| `type`       | Availability schedule name or busy type |

## Organization membership

#### Key fields

| Field          | Description            |
| -------------- | ---------------------- |
| `user_name`    | Member's display name  |
| `user_email`   | Member's email address |
| `role`         | Admin, owner, or user  |
| `organization` | Organization URI       |

## Common metric combinations

* **Bookings over time:** Use **Report: Events** filtered by date range, then group by `start_time` (day/week) in your destination
* **Cancellation rate:** Pull **Report: Events**, filter by `status = canceled`, and compare against total events
* **UTM-to-booking attribution:** Use **Report: Events with invitees** and match `utm_campaign` or `utm_source` to your ad data using a Join transformation
* **Team workload:** Use **Scheduled events for organization** combined with **List of users for organization** and Join on user URI to see bookings per team member

## Use cases by role

{% tabs %}
{% tab title="Sales teams" %}

* Export **Report: Events with invitees** to Google Sheets or BigQuery to track demo and discovery call volume by rep
* Match UTM parameters from Calendly bookings against ad campaign data to measure which channels drive qualified meetings
* Use the **Questions and answers report** to analyze pre-meeting form responses and qualify leads automatically
  {% endtab %}

{% tab title="Operations" %}

* Monitor team availability and busy times across users to spot scheduling conflicts or underutilization
* Pull **List of users for organization** to audit team membership and roles
* Append scheduled events from multiple team members into a single sheet for a unified scheduling dashboard
  {% endtab %}

{% tab title="Marketing" %}

* Track booking volume from campaigns using UTM parameters in **Report: Events with invitees**
* Feed Calendly booking data into ChatGPT or Gemini to generate summaries of which campaigns are driving the most meetings
* Join Calendly event data with CRM or ad data to close the loop between booking activity and pipeline
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* All timestamps are returned in **UTC**. If you're seeing unexpected times, convert to your local timezone in your destination tool.
* Organization-level entities (e.g., **Scheduled events for organization**, **Event types for organization**) require that your connected Calendly account belongs to a paid Calendly organization.
* UTM parameters are only captured if your Calendly booking links are embedded or shared with UTM parameters appended — they are not retroactively populated.
* The **Contacts** entity is not available through the Calendly API and cannot be exported via Coupler.io.
* User-level entities require selecting a specific user from your organization during data flow setup.

## Calendly common issues

### Connection issues

<details>

<summary>Coupler.io connected to the wrong Calendly account</summary>

This happens when your browser is already logged in to a personal Calendly account when you authorize. Coupler.io connects to whichever account is active in your browser session at the time of OAuth.

To fix this: log out of Calendly in your browser, then log back in to the correct account (e.g., your shared organization account). After that, create a new connection in Coupler.io and re-authorize.

</details>

<details>

<summary>OAuth authorization fails or loops back to the login page</summary>

Try clearing your browser cookies and cache, then retry the connection. If the issue persists, try using an incognito/private browser window to authorize.

</details>

### Missing data

<details>

<summary>Organization-level entities return no data or an error</summary>

Entities like **Scheduled events for organization** and **Event types for organization** require your connected Calendly account to be part of a paid Calendly organization (Teams plan or higher). If you're on a free plan, only user-level entities will return data.

</details>

<details>

<summary>Contacts data is not available</summary>

Calendly does not expose a Contacts endpoint in their API. Coupler.io cannot export contacts data from Calendly. To get invitee details, use **Report: Events with invitees** instead — it includes invitee names and emails for each booking.

</details>

<details>

<summary>UTM parameters are empty in the export</summary>

UTM data only appears if your booking links were shared with UTM parameters appended (e.g., `?utm_source=facebook`). If your links weren't tagged, those fields will be blank. UTM values are not retroactively added to past bookings.

</details>

<details>

<summary>Report entities return no rows for the selected date range</summary>

Double-check your start and end dates using the date picker. Reports like **Report: Events** require a valid date range — if the range is too narrow or set in the future, the result will be empty. Also confirm that events exist in Calendly for that period.

</details>

### Data discrepancies

<details>

<summary>Event times look wrong — off by several hours</summary>

All timestamps from Calendly are returned in **UTC**. If you're comparing them to times shown in the Calendly UI (which displays in your local timezone), there will be an offset. Convert the UTC timestamps to your local timezone in your destination tool (e.g., using a formula in Google Sheets or a timezone function in BigQuery).

</details>

<details>

<summary>Event count in Coupler.io doesn't match Calendly's dashboard</summary>

Calendly's dashboard may display events differently depending on filters applied (e.g., active only, excluding canceled). Make sure you're filtering your exported data by `status` to match what the Calendly UI shows. Canceled events are included in exports by default.

</details>

### Rate limits

<details>

<summary>Data flow fails with a rate limit or JSON error</summary>

Calendly's API has rate limits that can trigger errors if too much data is requested in a short window. If you see a "response is not valid JSON" error, this is often a symptom of a failed API response caused by rate limiting or a temporary Calendly API issue. Try running the data flow again after a few minutes. If the error persists, contact Coupler.io support.

</details>

## Calendly FAQ

<details>

<summary>Which Calendly plan do I need to use Coupler.io?</summary>

A free Calendly account gives you access to user-level entities (your own scheduled events, event types, and availability). To access organization-level entities — like Scheduled events for organization or List of users for organization — you need a Calendly Teams plan or higher.

</details>

<details>

<summary>Can I export Calendly contacts?</summary>

No — the Calendly API does not expose a Contacts endpoint, so Coupler.io cannot export contacts. If you need invitee details (names, emails, form responses), use **Report: Events with invitees** or **Report: Questions and answers** instead.

</details>

<details>

<summary>How do I get UTM tag data from Calendly bookings?</summary>

UTM parameters are included in **Report: Events with invitees** as fields like `utm_source`, `utm_medium`, and `utm_campaign`. These fields are only populated if your Calendly booking links were shared with UTM parameters appended. To match this data with ad performance, use the Join transformation in Coupler.io to combine the Calendly report with your Facebook Ads or Google Ads data on a shared campaign identifier.

</details>

<details>

<summary>Why are my event times showing the wrong hour?</summary>

Calendly returns all timestamps in UTC. The times are correct — they just need to be converted to your local timezone. Do this in your destination: use a timezone formula in Google Sheets, a `CONVERT_TIMEZONE` function in BigQuery, or a calculated field in Looker Studio.

</details>

<details>

<summary>How do I connect a shared or team Calendly account instead of my personal one?</summary>

Coupler.io connects to whichever Calendly account is active in your browser when you authorize. Before clicking Connect in Coupler.io, log out of your personal Calendly account and log in to the shared/organization account. Then create a new connection — Coupler.io will pick up the correct account.

</details>

<details>

<summary>Can I combine data from multiple Calendly users into one report?</summary>

Yes — there are two ways. If you have an org-level plan, use **Scheduled events for organization** to get all users' events in one pull. Alternatively, create multiple sources using user-level entities and use the **Append** transformation to stack them into a single dataset.

</details>

<details>

<summary>Can I send Calendly data to AI tools for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Calendly booking data directly to these tools to generate summaries, identify trends, or answer questions about your scheduling activity.

</details>

<details>

<summary>Why does my data flow show a "response is not valid JSON" error?</summary>

This usually means the Calendly API returned an unexpected response — often due to a temporary API issue or rate limiting. Wait a few minutes and try running the data flow again. If the error repeats consistently, reach out to Coupler.io support with the data flow name and error details.

</details>

{% hint style="info" %}
For details on what fields each entity returns, see the [Data Overview](#calendly-data-overview) article. For help with authorization and account switching, see [Common Issues](#calendly-common-issues). For tips on date ranges and combining entities, see [Best Practices](https://docs.coupler.io/sources/category/sales/calendly/best-practices.md).
{% endhint %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/sales/calendly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
