> 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/common-issues.md).

# 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>


---

# 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/common-issues.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.