Linking Clockodo as a source
This source is currently in alpha. The interface and available tables may change.
The Clockodo connector syncs your Clockodo time-tracking data into PostHog, so you can analyze time and project data alongside your product data.
Prerequisites
You need a Clockodo account with access to your personal API key. Credentials are scoped to that co-worker's permissions, so connect a user that can see the data you want to sync.
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 Clockodo, you'll need:
- Email – the email address of the Clockodo user whose API key you're using.
- API key – find your personal API key under Personal data in your Clockodo account.
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.
Clockodo exposes no server-side modified-since filter, so this source is full refresh only.
Configuration
| Option | Type | Required |
|---|---|---|
Email | Yes | |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | Customers (companies/clients) that work is tracked against. | Full refresh | — | — |
projects | Projects belonging to customers; the unit time entries are booked to. | Full refresh | — | — |
services | Services (types of work) that can be booked on time entries. | Full refresh | — | — |
lumpsum_services | Lump-sum (flat-rate) services that can be booked as fixed-price entries. | Full refresh | — | — |
users | Co-workers (users) in the Clockodo account. | Full refresh | — | — |
teams | Teams that users are grouped into. | Full refresh | — | — |
surcharges | Surcharge rules (e.g. night/weekend premiums) configured in the account. | Full refresh | — | — |
entries | Time entries across the full account history. Full refresh only — the API has no server-side modified-since filter. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, check that your email and API key are correct. Find your API key under Personal data in Clockodo, then reconnect.
- If you see a permission error, Clockodo credentials are scoped per co-worker. Check the user's 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.