Question 1

Which Campfire is this connector for?

Accepted Answer

Campfire the accounting and revenue platform, not Basecamp's Campfire chat product, which shares the name and causes regular confusion. This connects to Campfire's accounting API and reads your general ledger, financial statements, contracts, budgets, and cost allocations. If you are looking to sync team chat messages, this is not the connector you want.

Question 2

What Campfire data can Polytomic sync?

Accepted Answer

The ledger and the reporting layer both. On the transactional side: journal entries, invoices, bank accounts, contracts and contract customers, cost allocations, and departments. On the budgeting side: budgets and their accounts. And as prepared reports: daily and monthly income statements, monthly income statement by department, monthly balance sheet, and monthly cash flow. Having both means you can reconcile a model you build from journal entries against the statements Campfire produces, which is a useful check when the numbers need to be defensible.

Question 3

How does incremental syncing work?

Accepted Answer

Transactional objects filter on last modified time. Where the API supports sorting, such as bank accounts, invoices, budgets and departments, the checkpoint advances from the last record read. Where it does not, the checkpoint is taken at the sync's start time instead, which avoids missing records that change mid pagination. Report objects work differently: they read from a start date, with the income statement, balance sheet, and cash flow defaulting to a three year initial window and journal entries reaching considerably further back on the first ETL run.

Question 4

Are deleted records captured?

Accepted Answer

No. Campfire's API treats deleted records as a separate mode rather than including them alongside live ones, and enabling that flag returns only the deleted records rather than a combined view. Polytomic requests live records, so a deleted entry stops appearing and the previously synced row remains in your destination until you resync. For an accounting ledger this is rarely a practical issue since entries are normally reversed rather than deleted, but it is worth knowing if you rely on exact parity.

Question 5

Why move accounting data into a data warehouse?

Accepted Answer

Because the interesting financial questions need non financial data to answer. Gross margin by product line, cost to serve by customer segment, and whether a cohort's revenue justifies its support burden all require joining the ledger to product usage, CRM, and support data. A close tool reports the numbers; a data warehouse explains them. Running ETL from Campfire gives finance and analytics one shared source, and reverse ETL on the same platform can push a computed figure back into the tools other teams work in.

Campfire

Perfect pairings

Statements and ledger

Revenue recognition data

Incremental across objects

Example workflows

What you can sync

From Campfire

To your destinations

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Campfire in minutes

More integrations beyond Campfire