Linking Pabbly Subscription Billing as a source
This source is currently in alpha. The interface and available tables may change.
The Pabbly Subscription Billing connector syncs your customers, subscriptions, products, invoices, transactions, refunds, and related billing data into the PostHog Data Warehouse, so you can analyze your recurring revenue alongside your product data.
Prerequisites
You need a Pabbly Subscription Billing account with access to its API settings. The API key and secret key grant read access to every record in the account.
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.
When linking Pabbly Subscription Billing, you'll need:
- API key and Secret key – generate both under Settings → API Settings in your Pabbly Subscription Billing 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_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.
Pabbly Subscription Billing exposes no server-side change filter, so every table syncs via full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Secret key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | A customer in your Pabbly Subscription Billing account. | Full refresh | — | — |
subscriptions | A subscription of a customer to one of your plans. | Full refresh | — | — |
invoices | An invoice issued for a subscription. | Full refresh | — | — |
products | A product you sell; plans, addons, and coupons are grouped under a product. | Full refresh | — | — |
multiplans | A multiplan checkout page combining several plans of a product. | Full refresh | — | — |
payment_gateways | A payment gateway connected to your Pabbly Subscription Billing account. | Full refresh | — | — |
addons | An addon that can be attached to plans of a product. | Full refresh | — | — |
addon_list_category | An addon category of a product, used to group its addons. | Full refresh | — | — |
coupons | A discount coupon that can be applied to plans of a product. | Full refresh | — | — |
licenses | A license batch of a product, used to hand out license codes with subscriptions. | Full refresh | — | — |
payment_methods | A stored payment method of a customer. | Full refresh | — | — |
refunds | A refunded payment transaction of a customer. | Full refresh | — | — |
transactions | A payment transaction of a customer. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key or secret key is invalid or has been regenerated. Generate new keys under Settings → API Settings in Pabbly Subscription Billing, then reconnect.
- Pabbly Subscription Billing limits accounts to 10,000 API requests per day. Very large accounts syncing many tables on a frequent schedule can hit this quota; if syncs start failing late in the day, reduce the sync frequency or the number of synced tables.
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.