Linking Cal.com as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Cal.com connector syncs bookings, event types, schedules, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Cal.com API key to pull your scheduling data.
You can create an API key under Settings → Security → API keys in Cal.com. The key grants read access to your bookings, attendees, event types, schedules, teams, and webhooks.
The organization tables (memberships, users, and routing forms) need a key from a Cal.com organization admin. If your account isn't in an organization, leave those tables unselected.
Pick the region your Cal.com account lives in. Choose EU if you sign in at cal.eu, since a key from one region is not valid in the other.
You'll be asked for:
- API key: for example
cal_live_.... - Region: choose between US (api.cal.com) and EU (api.cal.eu).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Cal.com tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
bookings | A scheduled meeting booked through Cal.com, including regular, recurring, and seated bookings. | Incremental, Full refresh | updatedAt, createdAt | — |
event_types | An event type — a bookable meeting template defining duration, availability, and booking rules. | Full refresh | — | — |
schedules | An availability schedule defining when its owner can be booked. | Full refresh | — | — |
teams | A team the authenticated user belongs to. | Full refresh | — | — |
webhooks | A webhook subscription configured for the authenticated user. | Full refresh | — | — |
me | The profile of the user the API key belongs to. | Full refresh | — | — |
organization_memberships | A membership joining a user to the Cal.com organization the API key's account belongs to. | Full refresh | — | — |
organization_users | A user in the Cal.com organization. Resolves the user and host IDs carried on bookings and event types. | Full refresh | — | — |
team_memberships | A membership joining a user to one of the teams in the teams table. | Full refresh | — | — |
routing_forms | A routing form in the organization, which qualifies a lead and sends them to the right event type. | Incremental, Full refresh | updatedAt, createdAt | — |
routing_form_responses | A submission of a routing form, including the answers given and the booking it routed to. | Incremental, Full refresh | createdAt | — |
booking_attendees | One row per attendee of a booking, the grain needed for no-show and guest analysis. The booking columns are copied from the parent booking. | Incremental, Full refresh | bookingUpdatedAt, bookingCreatedAt | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.