Linking Creem 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.
Contents
The Creem connector syncs products, customers, subscriptions, transactions, discounts, licenses, affiliates, affiliate invites, splits, meters, usage events, and credit accounts into the PostHog data warehouse, so you can analyze your billing and payment data alongside your product data.
Prerequisites
An API key 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.
Connect your Creem account to sync your billing data. You can find your API key in the Creem dashboard under Developers > API Keys.
You'll be asked for:
API key – your Creem API key.
Environment – choose between Production (api.creem.io) and Test (test-api.creem.io). Make sure to use a key that matches your environment: live keys only work with Production, and test keys only work with Test.
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 Creem tables sync as full refresh. Each sync replaces the contents of the table. Creem's API doesn't expose an updated-since filter, so incremental sync isn't available.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Environment | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Products | A product sold in the Creem store, either a one-time purchase or a recurring subscription. | Full refresh | — | — |
Customers | A customer who bought from the Creem store. | Full refresh | — | — |
Subscriptions | A customer's recurring subscription to a product. | Full refresh | — | — |
Transactions | A payment for a one-time purchase or an invoice for a subscription period. | Full refresh | — | — |
Discounts | A discount code that customers can redeem at checkout. | Full refresh | — | — |
Licenses | A license key issued to a customer for a product, with its activated instances. | Full refresh | — | — |
Affiliates | An affiliate who joined the store's affiliate program. | Full refresh | — | — |
AffiliateInvites | An invitation to join the store's affiliate program. | Full refresh | — | — |
Splits | A revenue split that shares the payments of the store or of one product with other recipients. | Full refresh | — | — |
Meters | A meter that aggregates usage events into billable units for usage-based pricing. | Full refresh | — | — |
UsageEvents | A usage event sent to Creem for a customer. Meters aggregate these events for usage-based billing. | Full refresh | — | — |
CreditAccounts | A customer credits account that holds a balance of prepaid credits. | Full refresh | — | — |
The licenses table fans out over the customers table because Creem has no store-wide license listing. Each customer's licenses are fetched individually.
Troubleshooting
If the connection fails with an authorization error, check that you copied the whole key and that you chose the environment it belongs to. A test mode key works only with Test, and a live key only with Production.
If a table syncs no rows, the credential may not have access to that data. Check your API key permissions.
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.