Linking My Hours as a source
This source is currently in alpha. The interface and available tables may change.
The My Hours connector syncs your time-tracking data into the PostHog data warehouse, so you can analyze clients, projects, tags, and team members alongside your product data.
Prerequisites
You need a My Hours account on a paid plan with permission to create an API key. The key is tied to the user who created it, so it stops working if that user is archived or removed.
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 My Hours, you'll need:
- API key – create one under Settings → Integrations → API keys in your My Hours account. The key grants read access to your clients, projects, tags, and users.
Sync modes
All My Hours tables use full refresh only. The My Hours API does not expose pagination or an updated-since cursor, so there is no incremental sync option.
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.
Sync limitations
- Time logs are not synced. The My Hours time-logs report requires mandatory date parameters and is excluded from this connector.
- Full refresh only. Every sync reloads all data because the API has no incremental cursor.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
clients | A client (customer) that projects and time logs can be billed against. | Full refresh | — | — |
projects | A project that time is tracked against, optionally linked to a client. | Full refresh | — | — |
tags | A label used to categorise time logs. | Full refresh | — | — |
users | A member of the My Hours account (team member) who logs time. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid or revoked. Create a new key under Settings → Integrations → API keys in your My Hours account, then reconnect.
- If you see a permissions error, the key does not have access to this data. Check the key's permissions, then reconnect.
- If the user who created the API key is archived or removed, the key stops working. Create a new key with an active user.
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.