Linking Omni Analytics 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
PostHog Wizard hedgehog

Alpha release

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

The Omni Analytics connector syncs your Omni workspace data into PostHog, so you can analyze your BI documents, folders, connections, schedules, users, and user groups alongside your product data.

Prerequisites

You need an Omni Analytics account with API access. You can use either an Organization API key or a Personal Access Token, but Organization API keys provide broader coverage:

  • Organization API key – access all tables, including Users and User groups (SCIM endpoints). Create one under Settings > API access in Omni.
  • Personal Access Token – access most tables, but can't read Users or User groups. Only sees content the token owner can access.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see Configuration below) and click Next.
  4. 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 Omni Analytics, you'll need:

  • Instance URL – your Omni instance URL, for example https://your-company.omniapp.co.
  • API key – an Organization API key or Personal Access Token from your Omni account.

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.

The Documents table supports incremental sync via the updatedAt field. All other tables are full refresh only, since the Omni API doesn't expose incremental sync filters for them.

Configuration

OptionTypeRequired
Instance URLtextYes
API keypasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
Documents

Dashboards and workbooks in your Omni instance, with their owner, folder, and access scope.

Incremental, Full refreshupdatedAt
Folders

Folders organizing documents in your Omni instance.

Full refresh
Connections

Database connections configured in your Omni instance.

Full refresh
Schedules

Scheduled deliveries and alerts configured for dashboards in your Omni instance.

Full refresh
Users

Users provisioned in your Omni organization (SCIM).

Full refresh
UserGroups

User groups provisioned in your Omni organization (SCIM).

Full refresh

Troubleshooting

  • If you get an authorization error, your API key is invalid or expired. Generate a new key in Omni under Settings > API access and reconnect.
  • If you get a permission error, your API key doesn't have access to the requested data. Check the key's permissions and try again.
  • If the Users or User groups tables fail, make sure you're using an Organization API key. Personal Access Tokens can't access SCIM user and group endpoints.
  • If PostHog can't reach your Omni instance, check that the Instance URL is correct and points to your Omni deployment.

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.

Community questions

Was this page useful?