Linking Float 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 Float connector syncs people, accounts, departments, 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 Float access token to automatically pull your Float resource-management data.
You can create an access token in Float under Team Settings → Integrations → API. The token has the same access as its account owner.
All streams sync via full refresh - Float's API exposes no server-side modified-since filter on its core resources.
You'll be asked for:
- Access token
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 Float tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
people | A person scheduled in Float — a team member or placeholder that work is allocated to. | Full refresh | — | people_id |
accounts | A Float login account with its access level and role in the workspace. | Full refresh | — | account_id |
departments | A department used to group people in Float. | Full refresh | — | department_id |
clients | A client that projects can be associated with. | Full refresh | — | client_id |
projects | A project that work (tasks, phases, milestones) is scheduled against. | Full refresh | — | project_id |
project_stages | A stage a project can sit in, pairing a workspace-defined label with the underlying project status. | Full refresh | — | id |
phases | A phase within a project, bounding a date range with its own budget and rate. | Full refresh | — | phase_id |
tasks | An allocation (scheduled task) assigning a person to work over a date range. | Full refresh | — | task_id |
project_tasks | A named task defined on a project (the reusable task names allocations can use). | Full refresh | — | task_meta_id |
project_expenses | A non-labor cost booked against a project, the other half of project margin alongside logged time. | Full refresh | — | id |
milestones | A milestone marking a key date on a project. | Full refresh | — | milestone_id |
timeoffs | A time off entry for one or more people over a date range. | Full refresh | — | timeoff_id |
timeoff_types | A category of time off (e.g. vacation, sick leave) configured in the workspace. | Full refresh | — | timeoff_type_id |
logged_time | An entry of actual hours logged against a project (and optionally a task) on a date. | Full refresh | — | logged_time_id |
status | A status entry marking a person as available/unavailable over a date range. | Full refresh | — | status_id |
roles | A role that can be assigned to people in the workspace. | Full refresh | — | id |
holidays | A company-wide (public) holiday that blocks scheduling for everyone. | Full refresh | — | holiday_id |
public_holidays | A public holiday for a region, distinct from the workspace's own team holidays. Holidays reduce a person's capacity. | Full refresh | — | id, region |
rate_cards | A rate card defining bill rates by role, applied to projects to turn scheduled hours into billable value. | Full refresh | — | rate_card_id |
currencies | A currency the workspace bills in, with its exchange rate against the company's base currency. | Full refresh | — | currency_id |
reports_people | Float's per-person utilization report, aggregated over one calendar month. One row per person per month. | Full refresh | — | people_id, start_date |
deleted_tasks | Tombstone log of deleted allocations (tasks), for reconciling deletions since a cursor. | Full refresh | — | task_id |
deleted_timeoffs | Tombstone log of deleted time off entries, for reconciling deletions since a cursor. | Full refresh | — | timeoff_id |
deleted_logged_time | Tombstone log of deleted logged-time entries, for reconciling deletions since a cursor. | Full refresh | — | logged_time_id |
Troubleshooting
- If the connection fails with an authorization error, the access token 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.