Linking Chargify 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 Chargify connector syncs customers, subscriptions, products, 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.
Enter your Chargify (Maxio Advanced Billing) API key and site subdomain to pull your billing data.
You can create an API key under Settings → Integrations → API Access in your Chargify site. Your subdomain is the first part of your site URL - for acme.chargify.com the subdomain is acme.
You'll be asked for:
- API key
- Site subdomain: for example
acme.
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 Chargify tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Site subdomain | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Customers | A customer of the site, who owns subscriptions and is billed for them. | Full refresh | — | — |
Subscriptions | A subscription binding a customer to a product, tracking its billing state and lifecycle. | Full refresh | — | — |
Products | A product defining the recurring price and terms a subscription can be created against. | Full refresh | — | — |
ProductFamilies | A grouping of related products, components, and coupons within the site. | Full refresh | — | — |
Components | An add-on billed alongside a subscription (metered, quantity, on/off, or prepaid). | Full refresh | — | — |
Transactions | A financial event on a subscription, such as a charge, payment, credit, or refund. | Full refresh | — | — |
Events | An append-only record of an event that occurred on a subscription or the site. | Full refresh | — | — |
Invoices | An invoice issued for a subscription, listing line items, taxes, and payments. | Full refresh | — | — |
CreditNotes | An inverse invoice that reduces what a customer owes, applied against one or more invoices. | Full refresh | — | — |
Coupons | A discount that can be applied to subscriptions, either site-wide or within a product family. | Full refresh | — | — |
ReasonCodes | A churn code a merchant can pick from when cancelling a subscription. | Full refresh | — | — |
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.