Linking Windmill 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 Windmill connector syncs completed jobs, queued jobs, scripts, 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 Windmill instance URL, workspace ID, and API token to sync your Windmill data.
Create a personal API token in your Windmill account under User settings → Tokens. For cloud, your instance URL is https://app.windmill.dev; for self-hosted, use your own instance URL.
The audit logs table requires a workspace-admin token and is a Windmill Enterprise Edition feature.
You'll be asked for:
- Instance URL: for example
https://app.windmill.dev. - Workspace ID: for example
my-workspace. - 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_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 Windmill tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Instance URL | text | Yes |
Workspace ID | text | Yes |
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
completed_jobs | Execution history of finished jobs (scripts, flows, previews) with status, duration, and script path. Immutable, so supports incremental sync. | Incremental, Full refresh | created_at, started_at | — |
queued_jobs | Snapshot of jobs currently queued or running. Full refresh each sync since queued jobs are transient. | Full refresh | — | — |
scripts | Deployed scripts, one row per latest version per path. The list endpoint has no updated-since filter, so it is full-refresh only. | Full refresh | — | — |
flows | Deployed flows (multi-step workflows), one row per path. | Full refresh | — | — |
apps | Deployed apps (internal UIs built on Windmill), one row per path. | Full refresh | — | — |
schedules | Cron schedules that trigger scripts and flows. | Full refresh | — | — |
resources | Resource definitions (connection configs). The list endpoint returns metadata; secret values are not included. | Full refresh | — | — |
users | Workspace members. Returned in a single unpaginated response. | Full refresh | — | — |
audit_logs | Audit log entries. Windmill Enterprise Edition only and requires a workspace-admin token (empty on Community Edition). | 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.