> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Clockodo as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/clockodo > **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links). ## On this page - [Prerequisites](#prerequisites) - [Adding a data source](#adding-a-data-source) - [Sync modes](#sync-modes) - [Configuration](#configuration) - [Supported tables](#supported-tables) - [Troubleshooting](#troubleshooting) **Beta release** This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do. ![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70) ![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d) 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. `npx @posthog/wizard warehouse` ![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png) ![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you 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 1. In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section. 2. Click **\+ New source** and click **Link** next to this source. 3. Enter your credentials (see [Configuration](#configuration) below) and click **Next**. 4. 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#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` | 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 | — | — | | `absences` | Vacation, sick leave and other absences of each co-worker. | Full refresh | — | — | | `target_hours` | Target (planned) working hours per co-worker, and the periods they apply to. | Full refresh | — | — | | `user_reports` | Yearly co-worker report: target versus actual hours, overtime and holidays. One row per co-worker per year from 2011 on. | Full refresh | — | — | | `work_times` | Attendance per co-worker per day, with the clock-in/clock-out intervals of the day. Starts at 2023-08-21, the first day the API reports. Separate from the project time in `entries`. | 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.