Linking SingleStore, Inc. 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 SingleStore, Inc. connector syncs organization, regions, workspace groups, 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.
See the SingleStore, Inc. API documentation for how to create the credentials this source needs.
You'll be asked for:
- API key: generate an organization API key from the SingleStore Cloud Portal (Org name -> API Keys).
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 SingleStore, Inc. tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | Generate an organization API key from the SingleStore Cloud Portal (Org name -> API Keys). |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
organization | The SingleStore Helios organization the API key belongs to. | Full refresh | — | — |
regions | A cloud region SingleStore Helios can deploy workspace groups into. | Full refresh | — | — |
workspace_groups | A SingleStore Helios workspace group — the deployment unit that holds one or more workspaces sharing storage, networking, and region. | Full refresh | — | — |
workspaces | A SingleStore Helios workspace — a compute cluster within a workspace group that runs queries against the group's shared storage. | Full refresh | — | — |
billing_usage | Compute credit and storage usage for the organization, broken down by resource and time window. | Incremental, Full refresh | startTime | — |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.