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

# Linking Campfire as a source

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

> **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 Campfire connector syncs your accounting data from [Campfire](https://www.meetcampfire.com/) into PostHog: general ledger transactions, journal entries, invoices, bills, payments, bank activity, revenue recognition contracts, and company objects like vendors and the chart of accounts. This lets you analyze your financial data alongside your product data.

## Prerequisites

You need an active Campfire account with access to create API users and keys (Settings > API keys).

## 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 Campfire, you'll need an API key:

1.  In Campfire, go to the [API keys page](https://app.meetcampfire.com/v2/settings/api-keys) (**Settings > API keys**).
2.  Click **Create User** to create a dedicated API user. A `view only` role is enough, since PostHog only reads data.
3.  Click **Create API Key** on the new API user and copy the key. It's only shown once.

## 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.

Tables where Campfire supports server-side filtering by modification time (like GL transactions, bills, payments, vendors, and contracts) can sync incrementally on `last_modified_at`. The other tables sync with a full refresh.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `chart_transactions` | General-ledger transactions (ChartTransaction records) - Campfire's GL transaction log and the recommended endpoint for row-level GL data. Each transaction carries account, department, vendor, entity, and journal/date metadata. | Incremental, Full refresh | last\_modified\_at | — |
| `journal_entries` | Journal entries with their transactions, account information, vendor and department details, tag associations, attachments, and exchange rate data for multi-currency entries. | Full refresh | — | — |
| `invoices` | Accounts receivable invoices, including line items, payment status, client and entity relationships, and totals. | Full refresh | — | — |
| `invoice_payments` | Payments applied against accounts receivable invoices. Voided payments are included with voided\_date set, so payments reversed after a previous sync can be detected. | Incremental, Full refresh | last\_modified\_at | — |
| `credit_memos` | Accounts receivable credit memos, including line items, application status (open, partially used, used, voided), and client relationships. | Full refresh | — | — |
| `bills` | Accounts payable bills with vendor, entity, currency, aging, and payment status information, including calculated totals, amounts paid, and amounts due. | Incremental, Full refresh | last\_modified\_at | — |
| `bill_payments` | Payments applied against accounts payable bills. Voided payments are included with voided\_date set, so payments reversed after a previous sync can be detected. | Incremental, Full refresh | last\_modified\_at | — |
| `debit_memos` | Accounts payable debit memos, including line items, status, and vendor relationships. | Full refresh | — | — |
| `bank_accounts` | Bank accounts with balances, currency, institution details, and their mapping to chart of accounts types. | Incremental, Full refresh | last\_modified\_at | — |
| `bank_transactions` | Bank transactions from connected bank accounts. | Full refresh | — | — |
| `vendors` | Vendors and customers, including contact details, parent vendor metadata, and the full lineage of ancestor vendors so parent/child relationships can be reconstructed. | Incremental, Full refresh | last\_modified\_at | — |
| `departments` | Departments, including parent department metadata so parent/child relationships can be reconstructed. | Incremental, Full refresh | last\_modified\_at | — |
| `chart_of_accounts` | The chart of accounts (GL accounts). Each account includes metadata about its parent account and its full lineage, so parent/child account relationships can be reconstructed. | Full refresh | — | — |
| `chart_entities` | Legal entities (ChartEntity records) in the company structure. Every transaction, invoice and contract carries an entity ID, and each entity records its parent, its pre-computed lineage, its reporting currency and its fiscal year start, so multi-entity consolidation can be reconstructed. | Full refresh | — | — |
| `contracts` | Revenue recognition contracts. | Incremental, Full refresh | last\_modified\_at | — |
| `revenue_transactions` | Revenue transactions used for revenue recognition. | Incremental, Full refresh | last\_modified\_at | — |
| `contract_subscriptions` | Subscription schedules on revenue recognition contracts. Each subscription carries its product, rate, quantity, billing cadence and start and end dates, which is what ARR/MRR and revenue recognition waterfalls are built from. Collected by walking the contracts table, so every row names the contract it belongs to. | Incremental, Full refresh | last\_modified\_at | — |
| `products` | The product catalog behind contract line items, including pricing, usage tiers and the GL accounts each product posts revenue, AR and tax to. | Incremental, Full refresh | last\_modified\_at | — |
| `customers` | Customer records referenced by contracts, invoices and revenue transactions, with contact and billing details plus Campfire's rolled-up contract, revenue and receivable totals per customer. | Incremental, Full refresh | last\_modified\_at | — |
| `contract_milestones` | Milestones on revenue contracts. Each milestone recognizes a fixed amount on its milestone date and creates an associated revenue transaction. | Incremental, Full refresh | last\_modified\_at | — |
| `custom_dimensions` | Custom dimensions (transaction tags) used to break down transactions, journal entries and other records beyond account and department. | Incremental, Full refresh | last\_modified\_at | — |
| `custom_dimension_groups` | Groups that organize custom dimensions (transaction tags), such as a project or billable group. | Incremental, Full refresh | last\_modified\_at | — |
| `fixed_assets` | The fixed asset register, with each asset's accounts, depreciation schedule, disposals, transfers, impairments and net book value. | Incremental, Full refresh | last\_modified\_at | — |
| `budgets` | Budgets, each covering a date range for an entity or department at a set cadence. The amounts per account and period are in budget\_accounts. | Incremental, Full refresh | last\_modified\_at | — |
| `budget_accounts` | Budgeted amounts per GL account and period for each budget. | Incremental, Full refresh | last\_modified\_at | — |

## Troubleshooting

If a sync fails with an authentication error, the API key may have been revoked or the API user's role changed. Create a new API key in Campfire and update the source credentials in PostHog.

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.