Linking Platform.sh 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 Platform.sh connector syncs your Platform.sh (or Upsun) organizations, projects, environments, deploy activity, subscriptions, and organization members into PostHog, so you can analyze your deployments and infrastructure alongside your product data.
Prerequisites
You need a Platform.sh or Upsun account with access to the organizations you want to sync, and the ability to create an API token for your user.
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 Platform.sh, you'll need:
- API token – create one in the Console under My profile > API tokens. See the Platform.sh docs or Upsun docs for a walkthrough. The token has the same access as your user account, so no extra scopes are needed.
- API endpoint – pick the product you use: Platform.sh (
api.platform.sh) or Upsun (api.upsun.com). A Platform.sh token doesn't work against the Upsun API, and vice versa.
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 activities table syncs incrementally on created_at. Platform.sh prunes expired activities from its API, so incremental sync is also what preserves your full deploy history in PostHog beyond the API's retention window. The remaining tables are small lists and sync as full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
API endpoint | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
organizations | An organization groups projects, members, and billing under one account on Platform.sh or Upsun. | Full refresh | — | — |
projects | A project is a hosted application with its own Git repository, environments, and plan, belonging to an organization. | Full refresh | — | — |
environments | An environment is a running instance of a project tied to a Git branch, such as production or a preview branch. | Full refresh | — | — |
activities | An activity is an entry in a project's audit/deploy log: pushes, deploys, crons, backups, and other operations, with their state, result, and timings. The API prunes expired activities, so incremental sync is what preserves history. | Incremental, Full refresh | created_at | — |
subscriptions | A subscription is the billing record backing a project: its plan, allowances, and status within an organization. | Full refresh | — | — |
members | A member is a user's membership in an organization, with their permissions and owner flag. | Full refresh | — | — |
Activity rows exclude the raw log output, and environment rows exclude HTTP basic-auth credentials, so secrets from your Platform.sh account don't land in queryable tables.
Troubleshooting
- If you see an authentication error, check that the token is valid in the Console and that you picked the API endpoint matching where the token was created (Platform.sh vs. Upsun).
- If recent activity history looks shorter than expected, note that Platform.sh prunes expired activities from its API; PostHog keeps everything it has already synced.
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.