Linking Tempo as a source
This source is currently in alpha. The interface and available tables may change.
The Tempo connector syncs your time-tracking and resource-planning data from Tempo for Jira Cloud into the PostHog Data warehouse – worklogs, accounts, customers, teams, plans, and work schemes – so you can analyze logged and planned time alongside your product data.
Prerequisites
You need a Tempo account on Jira Cloud with permission to create API tokens (Tempo administrators can grant this under Settings → Permissions in Tempo).
Create a token in Tempo under Settings → API Integration and click New Token. Tempo tokens are scoped, so grant view (read) access for the data you want to sync: worklogs, accounts, customers, teams, plans, and schemes. Tables the token can't read can simply be left deselected when configuring the source.
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 Tempo, you'll need:
- API token – the token you created under Settings → API Integration in Tempo.
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 worklogs table supports incremental sync on updatedAt, so each sync only fetches worklogs created or amended since the previous run. The other tables are small reference data and sync with full refresh.
Note that Tempo references Jira issues and users by numeric id and account id. To resolve them to human-readable names, also link your Jira data or use the Jira API.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
worklogs | Time logged against Jira issues: who worked, on what, when, and for how long. | Incremental, Full refresh | updatedAt | — |
accounts | Tempo accounts used to categorize logged time for billing and reporting. | Full refresh | — | — |
customers | Customers that Tempo accounts can be linked to. | Full refresh | — | — |
teams | Tempo teams that group Jira users for planning and reporting. | Full refresh | — | — |
plans | Resource allocations: planned time for a user or generic resource against an issue or project. | Full refresh | — | — |
workload_schemes | Workload schemes defining required working hours per weekday for members. | Full refresh | — | — |
holiday_schemes | Holiday schemes defining the holidays that apply to their members. | Full refresh | — | — |
Troubleshooting
- 401 Unauthorized – the API token is invalid or has been revoked. Generate a new token under Settings → API Integration in Tempo and update the source credentials.
- 403 Forbidden on a table – the token is missing the view scope for that table. Grant the scope on the token in Tempo, or deselect the table from the sync.
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.