QuotaPath's integration with Campfire lets you bring your accounting data — invoices, payments, credit memos, and more — into QuotaPath to determine payout eligibility and, if needed, to create deals.
Like other accounting integrations (e.g. QuickBooks), Campfire is most commonly used in QuotaPath as a payouts eligibility source — for example, to release a commission once an invoice is paid — rather than as the source that creates deals, which usually originate in your CRM. That said, Campfire can create deals too, using objects like invoices, payments, or credit memos.
Integration Requirements
A Campfire account with API access. Campfire is cloud-based; QuotaPath connects to it over Campfire's API.
A Campfire API token, generated by a Campfire Admin. Campfire roles: Admin (full access; required to create the token), Clerk (read + draft writes), View only (read-only). QuotaPath only reads data (cannot write back to Campfire), so the token needs only read access — but creating it requires an Admin.
Important: Campfire shows API keys only once, at creation. Copy and store the token securely as soon as it's generated — you won't be able to view it again.
How to connect Campfire
In Campfire (as an Admin), generate an API token and copy it immediately. 🚧 (Confirm Campfire menu path.)
In QuotaPath, go to Settings > Integrations and find the Campfire card. Click Connect.
Paste your Campfire API token
Choose your sync schedule.
Select necessary objects for syncing and click Sync Now.
Once you've connected successfully and your first sync finishes, you'll see the Campfire connection card on the Integrations page, showing your last successful sync and sync status.
Supported objects
Invoices (most common)
Invoice Payments
Credit Memos
Bills
Bill Payments
Debit Memos
Vendors
Contracts
Customers
Products
Revenue Transactions
Journal Entries
Transactions
Bank Accounts
Chart of Accounts
Departments
Custom Fields
and more.
How to set up for Payouts Eligibility
This is the most common way to use Campfire: deals are created in your CRM, and Campfire data determines when a commission becomes payable. This means that two integrated sources will be used. You cannot use one Data Source for component mapping and another for Payout Terms (i.e. Payout eligibility).
To enable this multi-source eligibility setup, you must have a connecting ID (e.g. Deal ID) or field that exists in Campfire AND on your deal create data source records. QuotaPath will work with you to join your Campfire data needed to determine eligibility to the Deal Create source records, enabling you to use one source object for your mapping and eligibility, as is required. Work with your Customer Success Manager or Account Manager to build this data connection.
Important: You must have a connecting ID between your two data sources. This may involve adding and backfilling new fields in Campfire.
Once you have Campfire data joined to your deal create source data:
Map your component(s) to your Deal Create source first (e.g. Hubspot, Salesforce).
Click Setup Payout Terms on your component(s) and add a Payout Eligibility rule using one of the two options: By Invoice or By Date. Common fields used for each are:
Paid Amount to release the payout when (or in proportion to how much of) the invoice is paid.
Due Date, Paid Date or Transaction Date
For 1:many deals (one deal → several invoices/payments), typically Eligibility by Invoice: Paid Amount is used to aggregate all paid amounts as they come in. As the Paid Amount grows in proportion to the total Deal Amount, the Commission amount eligible to be paid out will grow in the same proportion. For example, if each invoice is 25% of the total deal amount, each paid invoice will make 25% of the earnings eligible for payout until 100% of the invoice is paid the entire payout is eligible.
For help, reach out to QuotaPath support, combining those records may need assistance.
How to set up for Deal Create only
Note: It is rare to use Campfire as the deal-create source — most teams create deals using their CRM. Use this only if Campfire records should generate deals directly.
The most common use cases for using Campfire as a Deal Create source is usage based plan components, or recurring book of business commissions.
To set up Campfire as your Deal Create source:
In your plan, click into your component and click Map Data Source. Select Campfire as your data source and select your object.
Map the required deal fields:
QuotaPath field | Campfire source (likely) | Notes |
Deal Name | invoice_number | Whatever value is most helpful to identify the Deal in QuotaPath. Could also join a field from another source to use. |
Deal Amount | total_amount | amount_paid / amount_due also available |
Deal Date | invoice_date | due_date / paid_date also available |
Deal Owner | custom field (rep email) | Rep email is necessary for Deal Create |
In the next mapping screen, define your deal stages (a "closed/won" equivalent is required; pipeline and closed-lost stages are optional). For invoices, this typically maps to status / payment_status. This criteria tells QuotaPath when to calculate earnings.
Pro tip: You can also use criteria like "Paid Date is not null" to trigger when a field is filled in.
Troubleshooting
Connection fails right after entering the token — confirm the token was copied in full, was created by an Admin, and hasn't been regenerated in Campfire (regenerating invalidates the old token).
A record isn't syncing — incremental syncs only pull records changed since the last run; check the record's last-modified date against your Start Date. If a record does have an old last-modified date, often you can make a small inconsequential change in Campfire on the record to update that date, then re-sync QuotaPath to pick up the updated record.
Records aren't attributed to a rep — confirm the Campfire custom field holds the rep's email and is mapped to Deal Owner.