Calendly
Sync data from Calendly API v2, including organization members, groups, teams, invitations, event types and hosts. You can also sync availability schedules, meeting locations, webhook subscriptions, scheduled events, event invitees, routing forms and submissions. Other supported data includes contacts, outgoing communications, activity logs and meeting recaps.
Prerequisites
- A Calendly account. API access is available on all Calendly plans, including Free. Routing forms and submissions need Teams. Outgoing communications and activity logs need Enterprise. Meeting recaps need a plan with Notetaker. Calendly can deny contacts with a paid-plan error. See Plan-gated streams.
- An organization owner or administrator account. This account must read organization-wide data, including scheduled events, webhook subscriptions, activity logs and outgoing communications. The connector reads the current organization from the authenticated user’s profile. You don’t need to enter an organization ID.
- One of these credentials:
- OAuth: In Airbyte Cloud, sign in to Calendly during setup. In Airbyte Open Source, OAuth needs your Calendly OAuth application’s client ID and client secret.
- A personal access token with the read scopes for every stream you sync, as listed in Token scopes.
- A start date in UTC. The connector reads scheduled events starting on or after this date. It reads outgoing communications, activity log entries and meeting recaps from this time onwards.
Set up Calendly
Use OAuth
- Create a Calendly source in Airbyte and select OAuth under Authentication.
- Select Authenticate your Calendly account and sign in to Calendly as an organization owner or administrator.
- Review and allow the requested access. Calendly grants the read scopes configured on Airbyte’s Calendly OAuth application. You don’t select the scopes yourself.
- Enter a Start date (UTC) and, optionally, a Lookback window (days) as described below.
Calendly rotates the OAuth refresh token whenever Airbyte requests a new access token. Airbyte stores the new token automatically. If Calendly rejects the refresh token, re-authenticate in the source settings. This can happen after you revoke Airbyte’s access in Calendly.
Each refresh spends the previous refresh token, so use one connection for each OAuth source. If two connections refresh the same source simultaneously, one will ask you to re-authenticate. Use a personal access token when several connections read the same Calendly account.
Use a personal access token
In Airbyte Open Source, use a personal access token unless you’ve registered your own Calendly OAuth application.
- In Calendly, open the Profile menu, select Developer, then select Personal access tokens. If Developer isn’t in your Profile menu, manage tokens from the Integrations page instead.
- Select Create personal access token, enter a token name, then select Next.
- Select the read scopes listed in Token scopes, then select Create.
- Enter the verification code Calendly emails you, then copy the token. Calendly displays the token only once.
- In Airbyte, create a Calendly source and select Personal access token under Authentication. Enter the token in Calendly personal access token. Enter a Start date (UTC) and, optionally, a Lookback window (days) as described below.
The connection check reads only the authenticated user’s profile (api_user). A successful check confirms users:read access, but not every stream’s required permissions. Missing stream-specific scopes or organization permissions can still cause a sync to fail.
Configuration
| Input | Type | Description | Default Value |
|---|---|---|---|
credentials.auth_type | string | Required. oauth2.0 for OAuth, or api_key for a personal access token. | |
credentials.client_id | string | Required for OAuth. Client ID of the Calendly OAuth application. Airbyte Cloud fills it in when you authenticate. | |
credentials.client_secret | string | Required for OAuth. Client secret of the Calendly OAuth application. Airbyte Cloud fills it in when you authenticate. | |
credentials.refresh_token | string | Required for OAuth. Refresh token returned by Calendly; the connector replaces it with the rotated token after every refresh. | |
credentials.api_key | string | Required for a personal access token. The personal access token created during setup. Configurations from versions before 1.1.0 that set a top-level api_key are moved here automatically. | |
start_date | string | Required. Read scheduled events starting on or after this time, and outgoing communications, activity log entries and meeting recaps from this time on. Use UTC in the format YYYY-MM-DDTHH:mm:ssZ, for example 2024-01-01T00:00:00Z. It applies to event start times, not to when invitees booked. | |
lookback_days | number | Optional. Incremental scheduled_events syncs re-emit events whose updated_at falls within this many days before the last synced update, plus a fixed five minutes. Every sync pages through all events from the start date, so 0 is right for most connections. | 0 |
When creating or updating the source through the Airbyte API or Terraform, put the personal access token inside credentials. For example, use {"auth_type": "api_key", "api_key": "<token>"}. The request no longer reads a top-level api_key. Sources saved before 1.1.0 move the token into credentials during their next check, schema refresh or sync. If you edit one in the Airbyte UI before then, enter the token again.
Token scopes
With OAuth, Calendly grants the scopes configured on Airbyte’s Calendly OAuth application. These scopes cover every stream below. The rest of this section applies to personal access tokens.
Since March 2026, new Calendly tokens have no API access until you select their scopes. Tokens created earlier keep their access. Select the scopes for every stream you sync. Every token also needs users:read for the connection check. If a scope is missing, the sync error identifies it. Version 0.3.0 added user_availability_schedules, locations and webhook_subscriptions. These streams need availability:read, locations:read and webhooks:read. Version 0.4.0 added routing_forms, routing_form_submissions, contacts, outgoing_communications, activity_log_entries and meeting_recaps. These streams need routing_forms:read, contacts:read, outgoing_communications:read, activity_log:read and meeting_recaps:read. Calendly sets a token’s scopes when you create it. Create a token with these scopes before syncing these streams, then update it in the source settings. Connections that propagate all field and stream changes add these streams automatically.
| Stream | Required scopes |
|---|---|
api_user | users:read |
event_types | users:read, event_types:read |
groups | users:read, groups:read |
organization_memberships | users:read, organizations:read |
scheduled_events | users:read, scheduled_events:read |
event_invitees | users:read, scheduled_events:read |
teams | users:read, organizations:read |
event_type_memberships | users:read, event_types:read |
group_relationships | users:read, groups:read |
user_availability_schedules | users:read, organizations:read, availability:read |
locations | users:read, organizations:read, locations:read |
organization_invitations | users:read, organizations:read |
webhook_subscriptions | users:read, webhooks:read |
routing_forms | users:read, routing_forms:read |
routing_form_submissions | users:read, routing_forms:read |
contacts | contacts:read |
outgoing_communications | users:read, outgoing_communications:read |
activity_log_entries | users:read, activity_log:read |
meeting_recaps | meeting_recaps:read |
Supported sync modes
You can use these sync modes with the Calendly source:
- Full refresh | Overwrite
- Full refresh | Append
- Incremental | Append
- Incremental | Append + Deduped
Incremental modes apply only to streams marked incremental in Supported streams. Other streams use Full refresh. locations and outgoing_communications have no primary key, so deduplicated modes don’t apply. See Incremental sync behavior for details about incremental syncs for scheduled_events and event_invitees, including how lookback_days applies.
Supported streams
| Stream | Data | Primary key | Full refresh | Incremental |
|---|---|---|---|---|
event_types | Event types in the organization, such as meeting names, durations, and scheduling URLs | uri | Yes | Yes, using updated_at |
api_user | The token owner’s profile and current organization | uri | Yes | No |
groups | Groups in the organization | uri | Yes | No |
organization_memberships | Organization members, their roles, and user profiles | uri | Yes | No |
scheduled_events | Scheduled meetings, including their times, status, and location | uri | Yes | Yes, using updated_at |
event_invitees | Invitees for each scheduled event, including answers, tracking data, and cancellation information | uri | Yes | Yes, dependent on scheduled_events |
teams | Teams in the organization | uri | Yes | No |
event_type_memberships | Hosts assigned to each event type | uri | Yes | No |
group_relationships | Member and admin relationships between groups and organization members or invitees | uri | Yes | No |
user_availability_schedules | Each organization member’s availability schedules, including time zones, weekly rules, and date-specific overrides | uri | Yes | No |
locations | Meeting location types available to each organization member | None | Yes | No |
organization_invitations | Invitations sent to join the organization | uri | Yes | No |
webhook_subscriptions | Configuration of organization-scoped webhook subscriptions, including callback URLs, subscribed event types, and state | uri | Yes | No |
routing_forms | Routing forms in the organization and their questions | uri | Yes | No |
routing_form_submissions | Submissions of each routing form, including answers, tracking data and the routing result | uri | Yes | No |
contacts | Contacts the token’s user can access | uri | Yes | No |
outgoing_communications | Email and SMS messages Calendly sent for the organization | None | Yes | Yes, using created_at |
activity_log_entries | Audit log of actions in the organization | uri | Yes | Yes, using occurred_at |
meeting_recaps | Notetaker recaps of meetings the token’s user can access | uri | Yes | Yes, using the meeting start_time |
The connector reads event_invitees for each new or changed event in scheduled_events. It reads every invitee for those events. Each invitee record includes scheduled_event_id, letting you join it to the id in scheduled_events. The invitee stream’s state follows scheduled_events. routing_form_submissions reads submissions from every routing form returned for the organization.
group_relationships reads the relationships for each group returned by groups. Organizations without groups sync this stream without records. The connector skips a group deleted during the sync. Permission errors still fail the sync.
Calendly’s OpenAPI specification marks calendar_event on scheduled_events as deprecated. The value can be null.
The incremental outgoing_communications, activity_log_entries and meeting_recaps streams request a window ending at the sync time. Their cursors never move beyond that time, and they don’t use lookback_days. Calendly returns a meeting recap only after processing finishes. Each sync rereads recaps for meetings starting up to three days before the saved cursor. Recaps that appear or change later need a Full refresh.
Calendly doesn’t return a unique identifier for outgoing communications. This stream therefore has no source-defined primary key, and no field combination is guaranteed unique. A primary key you select can merge distinct messages. Use Full refresh | Overwrite or Incremental | Append for this stream.
user_availability_schedules and locations send one request for each organization member. event_type_memberships sends one request for each event type. These streams aren’t suggested by default. locations has no primary key because Calendly doesn’t return a location identifier. Calendly can also list a location kind more than once. webhook_subscriptions lists only organization-scoped subscriptions. User-scoped and group-scoped subscriptions aren’t synced.
The scheduling-setup streams read configuration, not live availability or webhook deliveries:
user_availability_schedulesreturns availability rules, not bookable time slots or calendar busy times.locationslists the meeting location types configured for each member, not booked meeting locations. Readscheduled_eventsfor meeting-specific locations.webhook_subscriptionslists existing subscriptions. It doesn’t create subscriptions or receive webhook event payloads. Readscheduled_eventsandevent_inviteesfor bookings and cancellations.
Incremental syncs
Each incremental sync requests scheduled_events from the configured start date. It emits events whose updated_at changed since the previous sync, including upcoming events, cancellations and reschedules. Each sync therefore pages through every event from the start date. It makes as many scheduled_events requests as a Full refresh. On the Free plan, large histories need a later start date or less frequent syncs. lookback_days also re-emits events whose updated_at falls within that many days before the last synced update. It then reads their invitees again. Every sync already pages through all events from the start date, so 0 suits most connections. In every sync mode, events updated after a sync starts are excluded from that sync, along with their invitees. The next sync emits the event if it reads it before another change. With Full refresh | Overwrite, its rows remain missing from the destination until then.
event_invitees follows the scheduled_events state and rereads every invitee for each new or changed event. Calendly doesn’t document which invitee changes update the event’s updated_at. Examples include a no-show or one invitee leaving a group event. If the event remains unchanged, the invitee change reaches the destination after the event’s next change. A Full refresh of event_invitees also captures it.
Your first sync after upgrading to 1.0.0 ignores state saved by earlier versions. It rereads every event from your start date and all its invitees. In Incremental | Append mode, this adds another copy of each event and invitee. See the 1.0.0 migration guide.
Limits and troubleshooting
Plan-gated streams
Routing forms and submissions require Teams. Outgoing communications and activity logs require an Enterprise subscription. Meeting recaps require a paid plan with Notetaker enabled. Calendly also documents a paid-plan error for contacts. If Calendly reports an unavailable plan or feature, these streams finish without records. The connector logs a message explaining the requirement. Missing read scopes, owner or administrator permission errors, and other forbidden responses still fail the sync.
Calendly documents activity log entries and outgoing communications as Enterprise endpoints.
Rate limits
Calendly limits API requests to 500 requests per user each minute on paid plans and 50 on the Free plan. Other applications using the same Calendly user share this allowance.
The connector monitors X-RateLimit-Remaining and waits when the allowance runs out. If Calendly returns HTTP 429, the connector retries after the delay in X-RateLimit-Reset. Invitees and routing form submissions need requests for each scheduled event and form. Large histories can therefore take longer to sync.
Troubleshooting
| Symptom | Action |
|---|---|
| HTTP 401: invalid or revoked token | With OAuth, re-authenticate in the Airbyte source settings. With a personal access token, create a new token and update the Airbyte source settings. |
| Calendly rejected the OAuth refresh token | The refresh token expired, was revoked or was already used. Re-authenticate in the Airbyte source settings. |
| HTTP 403: insufficient scope or permission denied | Check the error for missing scopes. With a personal access token, create a token with the required read scopes. Authenticate with an organization owner or administrator account for organization-wide data such as scheduled events, webhook subscriptions, activity logs and outgoing communications. Update the credentials in Airbyte. |
| A plan-gated stream syncs no records | Calendly reported that the plan or feature is unavailable; the sync log names the requirement. Routing forms require Teams; without access to forms, routing form submissions also complete empty. |
| A scheduled event, event type, member, group or routing form disappears during a sync | The connector logs and skips that event’s invitees, that event type’s hosts, that member’s availability schedules and locations, that group’s relationships, or that form’s submissions, then continues. A 404 on other endpoints fails the sync. |
| New bookings or cancellations are missing | Upgrade to 1.0.0; its first sync reads every event from your start date again. See the 1.0.0 migration guide. Confirm that the connection’s start date covers the event. |
IP allow list
If you use Airbyte Cloud and your organization restricts access by IP address, add the Airbyte Cloud IP addresses to your allow list.
Changelog
Version 1.0.0 is a breaking change. Before you upgrade from 0.x, read the 1.0.0 migration guide.
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 1.1.0 | 2026-11-12 | 91296 | Add OAuth authentication as the default; personal access tokens remain available and existing configurations keep working |
| 1.0.0 | 2026-11-11 | 90864 | Fix incremental syncs missing new bookings and cancellations by using updated_at as the scheduled_events cursor, and declare date-time and integer types on existing fields |
| 0.4.2 | 2026-11-10 | 91376 | Update dependencies |
| 0.4.1 | 2026-11-09 | 91293 | Fix syncs that failed on routing_forms and routing_form_submissions below the Calendly Teams plan, and on group_relationships in organizations without groups |
| 0.4.0 | 2026-11-04 | 90848 | Add routing forms and submissions, contacts, outgoing communications, activity logs and meeting recaps streams; they need the new routing_forms:read, contacts:read, outgoing_communications:read, activity_log:read and meeting_recaps:read scopes |
| 0.3.0 | 2026-11-04 | 90847 | Add teams, event type memberships, group relationships, user availability schedules, locations, organization invitations and webhook subscriptions streams; user availability schedules, locations and webhook subscriptions need the new availability:read, locations:read and webhooks:read scopes |
| 0.2.0 | 2026-11-03 | 90829 | Handle rate limits and token errors, declare missing fields, fix the crash when lookback_days is unset, stop dropping event types updated before 2021 and invitees booked before the start date (refresh these streams to backfill) |
| 0.1.58 | 2026-11-03 | 90473 | Update dependencies |
| 0.1.57 | 2026-10-27 | 89813 | Update dependencies |
| 0.1.56 | 2026-10-20 | 89122 | Update dependencies |
| 0.1.55 | 2026-10-13 | 88545 | Update dependencies |
| 0.1.54 | 2026-10-06 | 87778 | Update dependencies |
| 0.1.53 | 2026-09-29 | 87092 | Update dependencies |
| 0.1.52 | 2026-09-22 | 86548 | Update dependencies |
| 0.1.51 | 2026-09-15 | 85958 | Update dependencies |
| 0.1.50 | 2026-09-08 | 85409 | Update dependencies |
| 0.1.49 | 2026-08-18 | 84504 | Update dependencies |
| 0.1.48 | 2026-08-11 | 83834 | Update dependencies |
| 0.1.47 | 2026-08-04 | 83371 | Update dependencies |
| 0.1.46 | 2026-07-28 | 82826 | Update dependencies |
| 0.1.45 | 2026-07-21 | 82322 | Update dependencies |
| 0.1.44 | 2026-07-14 | 81752 | Update dependencies |
| 0.1.43 | 2026-06-30 | 80989 | Update dependencies |
| 0.1.42 | 2026-06-23 | 80355 | Update dependencies |
| 0.1.41 | 2026-06-16 | 79778 | Update dependencies |
| 0.1.40 | 2026-06-09 | 79236 | Update dependencies |
| 0.1.39 | 2026-06-02 | 78555 | Update dependencies |
| 0.1.38 | 2026-04-28 | 77167 | Update dependencies |
| 0.1.37 | 2026-04-21 | 76522 | Update dependencies |
| 0.1.36 | 2026-03-31 | 75659 | Update dependencies |
| 0.1.35 | 2026-03-17 | 74912 | Update dependencies |
| 0.1.34 | 2026-03-10 | 74632 | Update dependencies |
| 0.1.33 | 2026-03-03 | 73791 | Update dependencies |
| 0.1.32 | 2026-02-03 | 72615 | Update dependencies |
| 0.1.31 | 2026-01-20 | 72052 | Update dependencies |
| 0.1.30 | 2026-01-14 | 71456 | Update dependencies |
| 0.1.29 | 2025-12-18 | 70622 | Update dependencies |
| 0.1.28 | 2025-11-25 | 69971 | Update dependencies |
| 0.1.27 | 2025-11-18 | 69431 | Update dependencies |
| 0.1.26 | 2025-10-29 | 68715 | Update dependencies |
| 0.1.25 | 2025-10-21 | 68240 | Update dependencies |
| 0.1.24 | 2025-10-14 | 67837 | Update dependencies |
| 0.1.23 | 2025-10-07 | 67205 | Update dependencies |
| 0.1.22 | 2025-09-30 | 66320 | Update dependencies |
| 0.1.21 | 2025-08-09 | 64664 | Update dependencies |
| 0.1.20 | 2025-08-02 | 64409 | Update dependencies |
| 0.1.19 | 2025-07-26 | 63801 | Update dependencies |
| 0.1.18 | 2025-07-19 | 63484 | Update dependencies |
| 0.1.17 | 2025-07-12 | 63040 | Update dependencies |
| 0.1.16 | 2025-06-28 | 62148 | Update dependencies |
| 0.1.15 | 2025-06-21 | 61888 | Update dependencies |
| 0.1.14 | 2025-05-28 | 60946 | update scheduled events to ingest future events |
| 0.1.13 | 2025-05-24 | 60689 | Update dependencies |
| 0.1.12 | 2025-05-10 | 59878 | Update dependencies |
| 0.1.11 | 2025-05-03 | 59314 | Update dependencies |
| 0.1.10 | 2025-04-26 | 58702 | Update dependencies |
| 0.1.9 | 2025-04-19 | 58247 | Update dependencies |
| 0.1.8 | 2025-04-12 | 57661 | Update dependencies |
| 0.1.7 | 2025-04-05 | 57123 | Update dependencies |
| 0.1.6 | 2025-03-29 | 56618 | Update dependencies |
| 0.1.5 | 2025-03-22 | 56087 | Update dependencies |
| 0.1.4 | 2025-03-08 | 55375 | Update dependencies |
| 0.1.3 | 2025-03-01 | 54839 | Update dependencies |
| 0.1.2 | 2025-02-22 | 54274 | Update dependencies |
| 0.1.1 | 2025-02-15 | 51240 | Update dependencies |
| 0.1.0 | 2025-02-12 | 52566 | Add stream organization members, groups, available event types, and scheduled events. |
| 0.0.8 | 2024-12-28 | 50462 | Update dependencies |
| 0.0.7 | 2024-12-21 | 50152 | Update dependencies |
| 0.0.6 | 2024-12-14 | 49551 | Update dependencies |
| 0.0.5 | 2024-12-12 | 49275 | Update dependencies |
| 0.0.4 | 2024-12-11 | 49022 | Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64 |
| 0.0.3 | 2024-11-04 | 48279 | Update dependencies |
| 0.0.2 | 2024-10-28 | 47568 | Update dependencies |
| 0.0.1 | 2024-09-01 | Initial release by @natikgadzhi via Connector Builder |