Linking Axiom 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 Axiom connector syncs monitoring and configuration data – datasets, monitors, annotations, dashboards, and saved queries – into the PostHog data warehouse, so you can analyze your observability setup alongside product data.

Prerequisites

You need an Axiom account and an API token with the right permissions:

Create an advanced API token in Axiom Settings > API tokens.
Grant read access to the resources you want to sync (datasets, monitors, annotations, dashboards, saved queries).
Grant query access to the datasets used by your monitors.
If you're using a personal access token, you also need your organization ID (find it in Axiom Settings > General).

Note: API tokens can only read shared dashboards. Saved queries request who=all, subject to token permissions.

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 Axiom, you'll need:

API token – an advanced API token with read permissions for the resources you want to sync. Create one in Axiom Settings > API tokens. Tokens start with xaat-....
Organization ID (optional) – required only for personal access tokens. Find this in Axiom Settings > General.

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 Axiom tables (datasets, monitors, annotations, dashboards, saved_queries) use full refresh sync. The Axiom API doesn't expose incremental filtering for these endpoints.

Configuration

Option	Description
`API token` Type: password Required: True
`Organization ID` Type: text Required: False	Required for personal access tokens. Find this ID in Axiom Settings > General.

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`datasets`	Axiom datasets, including their retention settings and edge deployments.	Full refresh	—	—
`monitors`	Axiom monitor configurations visible to the token through its dataset permissions.	Full refresh	—	—
`annotations`	Events marked on Axiom charts, such as deployments.	Full refresh	—	—
`dashboards`	Axiom dashboards visible to the caller. API tokens return shared dashboards only.	Full refresh	—	—
`saved_queries`	Queries saved by users in the Axiom team, subject to the token permissions.	Full refresh	—	—

Troubleshooting

If you see a 401 authentication error, your API token is invalid or has expired. Create a new advanced API token in Axiom Settings > API tokens.
If you see a 403 access denied error, check that the token has read permissions for the resources you're syncing. For personal access tokens, verify the organization ID is correct.

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.