Linking Sigma Computing 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 Sigma Computing connector syncs workbooks, data models, connections, 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

  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.

Connect Sigma Computing to pull your workbook, data model, connection, and membership metadata.

Generate a client ID and secret from Administration > Developer Access in Sigma, then pick the deployment region shown on that same page (or under Account > General Settings).

You'll be asked for:

  • Deployment region: choose between GCP - United States (Iowa), GCP - Saudi Arabia (Dammam), AWS - United States West (Oregon), AWS - United States East (N. Virginia), AWS - Canada (Central), AWS - Europe (Frankfurt), AWS - Asia Pacific (Sydney), AWS - United Kingdom (London), Azure - United States (Virginia), Azure - Europe (Netherlands), Azure - Canada (Toronto), Azure - United Kingdom (London) and Azure - Australia (New South Wales).
  • Client ID
  • Client secret

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 Sigma Computing tables are full refresh. Each sync replaces the contents of the table.

Configuration

OptionTypeRequired
Deployment regionselectYes
Client IDtextYes
Client secretpasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
Workbooks

A Sigma workbook: a saved collection of pages, elements, and visualizations built on top of one or more data sources.

Full refresh——
DataModels

A Sigma data model: a governed, reusable dataset built from one or more connections, the successor to the deprecated Datasets feature.

Full refresh——
Connections

A Sigma connection: the credentials and configuration Sigma uses to query an external warehouse or database.

Full refresh——
Teams

A Sigma team: a named group of members used to manage sharing and permissions.

Full refresh——
Members

A Sigma member: a user account within the organization.

Full refresh——
Workspaces

A Sigma workspace: a shared folder area used to organize workbooks, data models, and connections.

Full refresh——
Reports

A Sigma report: a saved, formatted document built from workbook content for scheduled delivery or export.

Full refresh——
WorkbookElements

An element (chart, table, or control) placed on a page within a Sigma workbook.

Full refresh——
WorkbookPages

A page within a Sigma workbook, grouping the elements shown on one tab.

Full refresh——
WorkbookQueries

The generated SQL query behind one element of a Sigma workbook, used to audit what a workbook actually runs against its data source.

Full refresh——

Troubleshooting

  • If the connection fails with an authorization error, the client secret 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.

Still have questions?

Was this page useful?