> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Alguna as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/alguna

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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](https://alguna.com) account with access to API credentials. API keys are issued in the Alguna dashboard under **Settings** > **Credentials**.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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](https://alguna.com) 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#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 | — | — |
| `credit_notes` | A credit note that reduces or offsets what a customer owes, optionally tied to an invoice. | 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 | — | — |
| `subscription_versions` | A version (phase) of a subscription's history — the state-transition record behind each change to its terms. | Full refresh | — | — |
| `wallets` | A prepaid wallet holding a customer's credit balance that can be drawn down against usage. | Full refresh | — | — |
| `wallet_grants` | A credit grant added to a wallet, with its amount, status, and expiry — the grant ledger behind wallet balances. | Full refresh | — | — |

## Troubleshooting

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.