# FAQ

<details>

<summary>Where do I find my Cal.com API key?</summary>

Log in to Cal.com and go to **Settings → Developer → API Keys**. Click **Add** to generate a new key. Copy it immediately — Cal.com won't show it again after you navigate away. Paste it into the API key field when setting up your Cal.com source in Coupler.io.

</details>

<details>

<summary>Can I pull booking data for my entire team, not just myself?</summary>

Not with a single API key — Cal.com's API is scoped to individual users. To get data across your whole team, each team member needs to generate their own API key. Create a separate data flow in Coupler.io for each person, then use the **Append** transformation to merge all their booking data into one unified table.

</details>

<details>

<summary>Can I filter bookings by date range or status?</summary>

Coupler.io pulls all available bookings from the Cal.com API. You can then filter the data in your destination (for example, using Google Sheets filters or Looker Studio date controls). The `status` field lets you filter by `accepted`, `cancelled`, `pending`, or `awaiting_host`, and `start_time` lets you apply date-based filtering.

</details>

<details>

<summary>How do I combine bookings with event type details in one table?</summary>

Add both the **Bookings** and **Event types** entities to your data flow, then use the **Join** transformation in Coupler.io. Join them on `event_type_id` (from Bookings) and `id` (from Event types) to get a flat table that includes meeting metadata — like duration and title — alongside each booking record.

</details>

<details>

<summary>Will Coupler.io capture recurring bookings?</summary>

Yes — Cal.com returns each instance of a recurring booking as a separate record. This means a weekly recurring meeting will appear as multiple rows in your Bookings data, one per occurrence. Use the `uid` field to identify and group recurring instances if needed.

</details>

<details>

<summary>Can I send Cal.com booking data to an AI tool?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Bookings data directly to any of these to generate summaries, identify patterns, or draft follow-ups based on attendee responses.

</details>

<details>

<summary>Why does the Conferencings entity return very little data?</summary>

The Conferencings entity reflects the conferencing integrations connected to your Cal.com account (like Zoom or Google Meet), not the individual meeting links for each booking. Actual meeting links per booking appear in the `location` field of the Bookings entity. If you haven't connected any conferencing integrations, this entity will be empty.

</details>

<details>

<summary>How often should I refresh my Cal.com data?</summary>

For most use cases, a daily refresh is sufficient. If you're tracking bookings in near real time (e.g., for a live dashboard), you can set a more frequent schedule — but be mindful of Cal.com's API rate limits, especially if you're running multiple data flows.

</details>

{% hint style="info" %}
For field-level details on each entity, see the [Data Overview](https://docs.coupler.io/sources/category/time-tracking/cal-com/data-overview) article. For help with connection errors or missing data, check [Common Issues](https://docs.coupler.io/sources/category/time-tracking/cal-com/common-issues).
{% endhint %}