Linking Alguna as a source
This source is currently in alpha. The interface and available tables may change.
The Alguna connector syncs your billing and CPQ data – customers, invoices, subscriptions, payments, refunds, plans, products, and billable metrics – into PostHog, so you can join revenue data with product analytics.
Prerequisites
You need an Alguna account with access to API credentials. API keys are issued in the Alguna dashboard under Settings > Credentials.
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 Alguna, you'll need:
- API key – create one under Settings → Credentials in your Alguna dashboard. The key has read access to your workspace's billing data.
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 Alguna tables sync as full refresh. Billing entities are low volume, so a full reload on each sync stays cheap and always reflects deletions.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
billable_metrics | A billable metric defining how ingested usage events are aggregated into a billable value (e.g. count, sum of a field). | Full refresh | — | — |
customers | A customer account you bill in Alguna, including currency and tax configuration. | Full refresh | — | — |
invoices | An invoice issued to a customer for a billing period, with its status lifecycle and total. | Full refresh | — | — |
payments | A payment made against an invoice, with amounts received and refunded and payment-processor references. | Full refresh | — | — |
plans | A reusable pricing plan template that subscriptions can be created from. | Full refresh | — | — |
products | A product (fixed-price or usage-based) that can be priced on plans and subscriptions. | Full refresh | — | — |
refunds | A refund issued against a payment, with amount, status, and payment-processor references. | Full refresh | — | — |
subscriptions | A customer's subscription contract, including billing, renewal, and discount configuration. | Full refresh | — | — |
Troubleshooting
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.