Linking SavvyCal as a source
This source is currently in alpha. The interface and available tables may change.
The SavvyCal connector syncs your scheduling data — booked events, scheduling links, webhooks, and workflows — into the PostHog Data warehouse, so you can analyze meeting activity alongside your product data.
Prerequisites
You need a SavvyCal account with access to Developer Settings to create a personal access token. The token carries your account's full read access, so it can read every record you can see.
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.
When linking SavvyCal, you'll need:
- Personal access token – create one under Developer Settings in SavvyCal by clicking Create a token. Tokens start with
pt_secret_.
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.
The events table supports incremental sync using the event start time (start_at): each run fetches events starting on or after the last synced start date. Because SavvyCal filters on the start date rather than a last-modified timestamp, changes to events that started before the watermark — for example, a cancellation of a past event — are only picked up by a full refresh. Rescheduled events move to a new start time and are picked up naturally.
All other tables are synced with a full refresh, as the SavvyCal API doesn't provide a way to filter them by modification time.
Configuration
| Option | Type | Required |
|---|---|---|
Personal access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
events | A scheduled event/booking made through SavvyCal. | Incremental, Full refresh | start_at | — |
links | A scheduling link for booking appointments. | Full refresh | — | — |
webhooks | Webhook configuration for receiving event notifications. | Full refresh | — | — |
workflows | An automated workflow for event processing. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your personal access token is invalid or has been revoked. Create a new token under Developer Settings in SavvyCal, then reconnect.
- If you see a permissions error, the token is missing the access needed to sync this data. Check the token owner's account permissions, then reconnect.
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.