Linking Astronomer 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 Astronomer connector syncs platform inventory and deploy history from Astronomer (Astro) into the PostHog data warehouse: deployments, deploys, workspaces, and clusters. This lets you join your Airflow infrastructure data with the rest of your product analytics.
Prerequisites
You need an Astronomer organization and an API token with read permissions for the tables you want to sync.
To create an API token:
- Go to your Astronomer Cloud organization.
- Navigate to Organization Settings > Access Management > API Tokens.
- Create a token and grant the permissions for the tables you need:
| Table | Required permission |
|---|---|
deployments | organization.deployments.get |
deploys | deployment.deploys.get and organization.deployments.get |
workspaces | organization.workspaces.get |
clusters | organization.clusters.get |
The deploys table also requires permission to list deployments because deploy history is fetched per deployment.
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 Astronomer, you'll need:
- Organization ID: your Astronomer organization ID (not the full URL).
- API token: a bearer token with read permissions for the tables you want to sync.
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 Astronomer tables are full refresh. Each sync replaces the contents of the table. The Astronomer API list endpoints don't support filtering by update time, so incremental syncs aren't available.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Organization ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
deployments | Airflow environments in an Astro organization. | Full refresh | — | — |
deploys | Code and image deploys for each Astro deployment. | Full refresh | — | — |
workspaces | Groups of deployments in an Astro organization. | Full refresh | — | — |
clusters | Kubernetes clusters that host Astro deployments. | Full refresh | — | — |
| Table | Description | Sync method |
|---|---|---|
deployments | Airflow environments in your Astro organization | Full refresh |
deploys | Code and image deploys for each deployment | Full refresh |
workspaces | Groups of deployments in your organization | Full refresh |
clusters | Kubernetes clusters that host Astro deployments | Full refresh |
Troubleshooting
If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new token and reconnect the source.
If a table syncs with a permission error, the token is missing the required scope for that table. Check the permissions table above and update the token.
If you get a 404 error, verify that your organization ID is correct. Enter just the ID, not a full URL.
The
clusterstable returns only clusters available to your organization. If the table is empty, your organization may not have any dedicated clusters.
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.