Linking Jellyfish as a source
This source is currently in alpha. The interface and available tables may change.
The Jellyfish connector syncs your engineering intelligence data into PostHog, so you can analyze R&D allocations, delivery deliverables, and engineering metrics alongside your product and financial data.
Prerequisites
You need a Jellyfish subscription with the API Export feature enabled, and an Admin user role in Jellyfish to generate an API token.
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 Jellyfish, you'll need:
- API token – generate one in Jellyfish under Settings → Data Connections → API Export. Tokens are created with an expiry, so reconnect with a fresh token when yours expires.
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.
Jellyfish tables sync as full refreshes: reference tables (engineers, teams, work categories) are small lists, and the analytics tables re-export a rolling two-year window of monthly data on each sync, so restated periods are always picked up.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
engineers | Active allocatable people tracked in Jellyfish, as returned by the people export. | Full refresh | — | — |
teams | The Jellyfish team hierarchy (top-level teams and their children). | Full refresh | — | — |
work_categories | Work categories configured in Jellyfish for grouping delivery work. | Full refresh | — | — |
allocations_by_person | R&D allocation (FTE effort) per person for each calendar-month window. | Full refresh | — | — |
allocations_by_team | R&D allocation (FTE effort) per top-level team for each calendar-month window. | Full refresh | — | — |
allocations_by_investment_category | R&D allocation (FTE effort) per investment category for each calendar-month window. | Full refresh | — | — |
company_metrics | Company-wide engineering metrics (delivery and DORA-style measures) for each calendar-month window. | Full refresh | — | — |
unlinked_pull_requests | Pull requests Jellyfish could not link to an issue, for each calendar-month window. | Full refresh | — | — |
deliverables | Deliverables (epics/projects) in each Jellyfish work category, with delivery status and effort. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API token may be invalid or expired. Generate a new token under Settings → Data Connections → API Export in Jellyfish, 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.