Linking Aviator 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 Aviator connector syncs repositories, merge queue analytics, queued pull requests, 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 Aviator API token to pull your merge-queue data.
Create a user access token (it starts with av_uat_) from your Aviator account settings, then paste it below. The token inherits your account's repository access, so no extra scopes are required.
You'll be asked for:
- API token: for example
av_uat_....
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 Aviator tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
repositories | GitHub repositories connected to Aviator, with their merge-queue status. | Full refresh | — | — |
merge_queue_analytics | Daily merge-queue analytics per repository, merging Aviator's five daily aggregate series into one row per day. | Incremental, Full refresh | date | — |
queued_pull_requests | Pull requests currently in the queued state for each repository (a live snapshot). | Full refresh | — | — |
queue_stats | Live merge-queue depth per repository (a current-state snapshot). | Full refresh | — | — |
branches | Base branches configured on each repository's merge queue, as glob patterns with their pause state. | Full refresh | — | — |
bot_pull_requests | Batch (bot) pull requests Aviator creates in parallel mode, linking each batch to the queued pull requests it carries. | Full refresh | — | — |
user_actions | Audit log of actions taken by users in the Aviator account. Requires an Aviator Enterprise plan. | Full refresh | — | — |
config_history | History of merge-queue YAML config changes per repository, as diffs. | 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.