Linking Baton 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 Baton connector syncs activity, companies, milestones, 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 Baton (Hellobaton) company instance and API key to pull your onboarding and implementation data.
Your company instance is the subdomain of your Baton URL - for yourcompany.hellobaton.com, enter yourcompany.
Generate an API key in Baton under the API section of your account settings. The key inherits your account permissions, so it can read every record you can see.
You'll be asked for:
- Company instance: for example
yourcompany. - 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 Baton tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Company instance | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
activity | Audit-log style activity events recording changes to Baton objects (who did what to which record). | Full refresh | — | — |
companies | Companies (customer accounts) tracked in Baton. | Full refresh | — | — |
custom_fields | Custom field definitions — the name, type and display settings of each custom field configured in Baton. | Full refresh | — | — |
custom_field_values | Custom field values set on projects. Join | Full refresh | — | — |
milestones | Milestones within a project — grouped deliverables with a target completion date. | Full refresh | — | — |
phases | Phases that projects move through during an implementation. | Full refresh | — | — |
projects | Onboarding/implementation projects — the central object in Baton. | Full refresh | — | — |
project_attachments | Files attached to projects. | Full refresh | — | — |
project_phases | Phase instances on a project, with the scheduled start and end of each phase. | Full refresh | — | — |
project_users | Project membership — which users are on which project, with their role and invitation status. | Full refresh | — | — |
tasks | Tasks — the unit of work within a project, grouped under milestones. | Full refresh | — | — |
task_attachments | Files attached to tasks, including deliverables that may require approval. | Full refresh | — | — |
templates | Project templates used to spin up new implementation projects. | Full refresh | — | — |
time_entries | Time logged by users against projects and tasks. | Full refresh | — | — |
users | Users in the Baton account — both internal team members and customer contacts. | 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.