> 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/time-tracking/cal-com/data-overview.md).

# Data Overview

Cal.com gives you access to six entities through Coupler.io, covering everything from your personal profile and availability setup to individual bookings and conferencing integrations.

## Available entities

| Entity        | What it contains                                                     |
| ------------- | -------------------------------------------------------------------- |
| Bookings      | Scheduled meetings with attendee info, timing, and booking responses |
| Event types   | Meeting templates — duration, slug, location type, and visibility    |
| Schedules     | Weekly availability windows and time slot configurations             |
| Calendars     | Connected calendar accounts and their integration status             |
| My profiles   | User profile: name, username, email, timezone, and avatar            |
| Conferencings | Conferencing tools linked to the account (Zoom, Meet, etc.)          |

## Bookings

#### Fields

| Field           | Description                                        |
| --------------- | -------------------------------------------------- |
| `id`            | Unique booking identifier                          |
| `uid`           | Public-facing unique ID for the booking            |
| `title`         | Meeting title                                      |
| `start_time`    | Scheduled start date and time                      |
| `end_time`      | Scheduled end date and time                        |
| `status`        | Booking status: `accepted`, `cancelled`, `pending` |
| `attendees`     | Names and emails of attendees                      |
| `event_type_id` | ID of the event type used for this booking         |
| `location`      | Meeting location or conferencing link              |
| `description`   | Notes or custom questions answered at booking      |
| `created_at`    | When the booking was created                       |

## Event types

#### Fields

| Field                  | Description                                                    |
| ---------------------- | -------------------------------------------------------------- |
| `id`                   | Unique event type identifier                                   |
| `title`                | Display name of the event type                                 |
| `slug`                 | URL-friendly identifier used in booking links                  |
| `length`               | Duration in minutes                                            |
| `hidden`               | Whether the event type is publicly visible                     |
| `locations`            | Allowed meeting locations (Zoom, Google Meet, in-person, etc.) |
| `description`          | Event type description shown to bookers                        |
| `require_confirmation` | Whether bookings require manual approval                       |

## Schedules

#### Fields

| Field          | Description                                 |
| -------------- | ------------------------------------------- |
| `id`           | Schedule identifier                         |
| `name`         | Schedule name                               |
| `timezone`     | Timezone the schedule is set in             |
| `availability` | Day-by-day time slot configuration          |
| `is_default`   | Whether this is the user's default schedule |

## Calendars

#### Fields

| Field         | Description                                             |
| ------------- | ------------------------------------------------------- |
| `integration` | Calendar type (e.g., `google_calendar`, `office365`)    |
| `name`        | Calendar display name                                   |
| `external_id` | External calendar account identifier                    |
| `is_selected` | Whether this calendar is used for availability checking |

## My profiles

#### Fields

| Field      | Description                |
| ---------- | -------------------------- |
| `id`       | User ID                    |
| `name`     | Full name                  |
| `username` | Cal.com username           |
| `email`    | Account email              |
| `timezone` | User's configured timezone |
| `avatar`   | Profile image URL          |

## Conferencings

#### Fields

| Field      | Description                                          |
| ---------- | ---------------------------------------------------- |
| `type`     | Integration type (e.g., `zoom_video`, `google_meet`) |
| `app_data` | App-specific connection details                      |

## Common field combinations

* **Booking volume analysis** — use `start_time`, `status`, and `event_type_id` to see how many bookings each event type generates over time
* **Cancellation tracking** — filter `status = cancelled` and group by `event_type_id` or date to identify drop-off patterns
* **Availability auditing** — combine Schedules and Calendars to verify that availability is set correctly across time zones and integrations
* **Attendee reporting** — flatten `attendees` from Bookings to build a contact list of everyone who has booked with you

## Use cases by role

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

* Pull Bookings data into Google Sheets or a CRM pipeline to track how many discovery calls are scheduled and completed each week
* Use the `status` field to monitor no-shows and follow up automatically
* Join Bookings with Event types to see which meeting format (demo, intro call, check-in) drives the most conversions
  {% endtab %}

{% tab title="Operations" %}

* Audit Schedules and Calendars to make sure team members have consistent availability windows and no misconfigured integrations
* Send data to BigQuery or Looker Studio for team-wide booking dashboards
* Use Append transformation to combine bookings from multiple Cal.com accounts into one unified report
  {% endtab %}

{% tab title="Consultants & freelancers" %}

* Track meeting volume and duration over time using Bookings + Event types in Google Sheets
* Export attendee data for invoicing or follow-up
* Send booking summaries to ChatGPT or Claude for AI-generated meeting prep notes or weekly recaps
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The Cal.com API returns attendees as a nested array — Coupler.io will flatten this into individual rows or columns depending on your destination
* `status` values in Bookings are: `accepted`, `cancelled`, `pending`, and `awaiting_host` — filter accordingly in your destination
* Conferencings data reflects linked integrations at the account level, not per-booking conferencing links (those appear in Bookings under `location`)
* If you use Cal.com Teams, the API key must belong to the team member whose data you want — there is no org-wide API key for pulling all team members' bookings at once


---

# 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/time-tracking/cal-com/data-overview.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.