Linking Hub Planner as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Hub Planner connector syncs projects, resources, bookings, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Hub Planner API key to sync your resource-scheduling, project-planning and time-tracking data.
Generate a Read Only API key in Hub Planner under Settings → API (admin access required).
You'll be asked for:
- API key
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.
All Hub Planner tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | Projects scheduled in Hub Planner, including budget, status and assigned resources/managers. | Full refresh | — | — |
resources | Resources (people or assets) that can be scheduled, with role, status and contact details. | Full refresh | — | — |
bookings | Scheduled bookings allocating a resource to a project over a date range. | Incremental, Full refresh | updatedDate | — |
time_entries | Timesheet entries logging time a resource spent on a project. | Incremental, Full refresh | updatedDate | — |
events | Custom events in the scheduler (e.g. training, meetings) not tied to a project. | Full refresh | — | — |
clients | Clients that projects can be associated with. | Full refresh | — | — |
milestones | Project milestones with a target date. | Full refresh | — | — |
project_groups | Groups used to organise projects. | Full refresh | — | — |
resource_groups | Groups used to organise resources. | Full refresh | — | — |
billing_rates | Billing rates that can be applied to bookings and projects. | Full refresh | — | — |
holidays | Public holidays configured in Hub Planner. | Full refresh | — | — |
vacations | Vacation and time-off entries per resource. | Full refresh | — | — |
project_managers | Resources designated as project managers. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.