Linking Coolify 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.

Learn more

Alpha release

This source is currently in alpha. The interface and available tables may change.

The Coolify connector syncs applications, databases, deployments, 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 Coolify instance URL and an API token to pull your servers, projects, applications, databases, services, deployments, and teams.

Create a token under Keys & Tokens > API tokens in your Coolify dashboard. A read-only token is enough, because this source never writes or deploys.

The instance URL is where your Coolify dashboard runs, for example https://coolify.example.com (use https://app.coolify.io for Coolify Cloud).

You'll be asked for:

Instance URL: for example https://coolify.example.com.
API 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_at timestamp). 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 Coolify tables are full refresh. Each sync replaces the contents of the table.

Configuration

Option	Type	Required
`Instance URL`	text	Yes
`API token`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`applications`	An application deployed on a Coolify server: its git source, build configuration, domains, and health checks.	Full refresh	—	—
`databases`	A standalone database managed by Coolify (PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, or ClickHouse). Credential columns are removed before storage.	Full refresh	—	—
`deployments`	One row per application deployment, fetched per application. Deploy logs and configuration snapshots are removed before storage.	Full refresh	—	—
`projects`	A Coolify project: the top-level grouping that holds environments and their resources.	Full refresh	—	—
`servers`	A server connected to Coolify that resources deploy onto.	Full refresh	—	—
`services`	A one-click or compose-based service running on a Coolify server. Compose file contents are removed before storage.	Full refresh	—	—
`teams`	A Coolify team, with its members embedded. API tokens are scoped to one team, so this lists the teams that token can see.	Full refresh	—	—

Troubleshooting

If the connection fails with an authorization error, the API 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.