Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
Business productivity · Two-way sync platform

Campfire connector for two-way sync.

Keep Campfire and your business systems aligned with Stacksync. Sync Invoice, Bill and Journal Entry within the connector’s object and field requirements, with two-way sync for eligible records.

Set this up from Claude or ChatGPT
  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Campfire

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Record types

Campfire objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Bill
Incremental: Yes; historical: Yes; delete detection: Yes, every 24h
Invoice
Incremental: Yes; historical: Yes; delete detection: Yes
Journal Entry
Incremental: Yes; historical: Yes; delete detection: Yes
Vendor
Incremental: Yes; historical: Yes; delete detection: Yes
View all 34 object types and restrictions
Debit Memo
Incremental: Yes; historical: Yes; delete detection: Yes
Credit Memo
Incremental: Yes; historical: Yes; delete detection: Yes
Bank Account
Incremental: Yes; historical: Yes; delete detection: Yes
Bank Transaction
Incremental: Yes; historical: Yes; delete detection: Yes
Intercompany Journal Entry
Incremental: Yes; historical: Yes; delete detection: Yes
Chart of Accounts
Incremental: Yes; historical: Yes; delete detection: Yes
Chart Transaction
Incremental: Yes; historical: Yes; delete detection: Yes
Fixed Asset
Incremental: Yes; historical: Yes; delete detection: Yes
Fixed Asset Class
Incremental: Yes; historical: Yes; delete detection: Yes
Fixed Asset Automation Rule
Incremental: Yes; historical: Yes; delete detection: Yes, every 24h
Fixed Asset Automation Match
Incremental: Yes; historical: Yes; delete detection: N/A (cannot be deleted)
Budget
Incremental: Yes; historical: Yes; delete detection: Yes
Transaction Match
Incremental: Yes; historical: Yes; delete detection: Yes
Vendor Summary
Incremental: Yes; historical: Yes; delete detection: N/A (cannot be deleted)
Vendor Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes, every 24h
Department
Incremental: Yes; historical: Yes; delete detection: Yes, every 24h
Entity
Incremental: Yes; historical: Yes; delete detection: Yes, every 24h
Tag
Incremental: Yes; historical: Yes; delete detection: Yes
Tag Group
Incremental: Yes; historical: Yes; delete detection: Yes, every 24h
Cost Allocation
Incremental: Yes; historical: Yes; delete detection: Yes
Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes
File
Incremental: Yes; historical: Yes; delete detection: Yes
Contract
Incremental: Yes; historical: Yes; delete detection: Yes
Contract Customer
Incremental: Yes; historical: Yes; delete detection: Yes
Product
Incremental: Yes; historical: Yes; delete detection: Yes
Product Bundle
Incremental: Yes; historical: Yes; delete detection: Yes
Revenue Transaction
Incremental: Yes; historical: Yes; delete detection: Yes
Customer Currency
Incremental: Yes; historical: Yes; delete detection: Yes
Reconciliation Report
Incremental: Yes; historical: Yes; delete detection: Yes
Webhook
Incremental: Yes; historical: Yes; delete detection: Yes

Read the Campfire object and setup guide

Connection setup

Campfire connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
HTTP endpoints for bot integrations on a self-hosted instance
Account access
API key — create an API user with a Super User Role in Campfire (Settings -> API Keys), generate an API Key secret, and provide it in the Stacksync connection setup
How changes are detected
Historical backfill and incremental change tracking are documented. Delete detection varies by object.

Sync directions

  • Read data Documented
  • Write data Documented
CampfireStacksync setup guide
Setup prerequisites for your administrator
  • Create an API user with a Super User role in Campfire Settings > API Keys and generate its secret.
  • Review the supported-object table for incremental sync and deletion behavior before selecting entities.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Campfire integration.

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
CampfireSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Keep financial record IDs and entity context separate from customer/vendor references. An invoice, payment, and journal entry are distinct business records even when they share an amount.
Load related records in the right order
Resolve Entity, Chart of Accounts, Vendor, and Contract Customer references before loading dependent financial records. Confirm the required object operations in the support table.

Mapping checks by record type

Invoice

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Fields to consider
Source invoice ID · Customer or supplier reference · Line totals · Currency · Posting/payment status
Related records to resolve first
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test before going live
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Bill

Incremental: Yes; historical: Yes; delete detection: Yes, every 24h

Identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Fields to consider
Source bill ID · Supplier reference · Entity · Line amounts and currency · Approval/posting state
Related records to resolve first
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test before going live
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Journal Entry

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Retain journal ID and line IDs within the legal entity and accounting period.
Fields to consider
Source journal ID · Account references · Debit/credit amounts · Entity · Accounting period
Related records to resolve first
Resolve chart-of-account, currency, entity, and dimension references before lines.
Test before going live
Verify balanced debits and credits, dimension requirements, and rejection for a closed period.

Vendor

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Fields to consider
Source supplier ID · Legal name · Entity reference · Payment terms · Active status
Related records to resolve first
Resolve business-unit and payment-term references before purchasing transactions.
Test before going live
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.

Credit Memo

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Keep a distinct credit-document ID and its relationship to the original invoice or bill; it is not the original invoice itself.
Fields to consider
Source credit-document ID · Original document reference · Customer/supplier reference · Credit amount and currency · Posting state
Related records to resolve first
Resolve the original invoice/bill, customer or supplier, legal entity, and account references.
Test before going live
Test a partial credit, several credits against one invoice, and a credit without a valid original-document relationship.

Product

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Fields to consider
Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference
Related records to resolve first
Resolve units, variants, categories, and applicable price lists before order lines.
Test before going live
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Campfire integration in four steps.

Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

View the four setup tests and expected results

  1. Verify Campfire credentials and resource scope

    Use the documented setup with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object.

    Expected result: The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner.

  2. Exercise object-specific delete detection

    For a disposable test record in an eligible object, observe the documented delete check. Some objects are checked only every 24 hours.

    Expected result: The runbook records the actual behavior for that object and does not apply ordinary update timing to deletions.

  3. Test writes in the directions you need

    Select one eligible Campfire object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Campfire records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Campfire integration.

Diagnose record matching, delayed changes, and rejected operations
A removed record remains in a destination report
Check that object’s documented deletion support and interval. Reconcile the reporting period before retrying writes or removing destination rows.
The first load looks correct but later results differ
Historical backfill and incremental change tracking are documented. Delete detection varies by object. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Campfire object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Campfire workflow with an engineer

Campfire integration guides

FAQ

Campfire connector FAQ

How should I plan an integration with Campfire?

Financial document types have different incremental and deletion behavior; select them deliberately. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Campfire connector write changes back?

Stacksync supports reads and writes for eligible Campfire objects. Check the selected fields, account permissions, and the other system’s connector. For a disposable test record in an eligible object, observe the documented delete check. Some objects are checked only every 24 hours.

Which identifiers should I preserve for Campfire data?

Keep financial record IDs and entity context separate from customer/vendor references. An invoice, payment, and journal entry are distinct business records even when they share an amount.

Which related records should I load first for Campfire?

Resolve Entity, Chart of Accounts, Vendor, and Contract Customer references before loading dependent financial records. Confirm the required object operations in the support table.

What should I check if Campfire data is missing or delayed?

Check that object’s documented deletion support and interval. Reconcile the reporting period before retrying writes or removing destination rows.

What will we cover in a Campfire integration demo?

Start with one workflow and a sample record from Invoice, Bill and Journal Entry. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

AI assistant

Set up Campfire from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my Campfire and another app or database.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Campfire. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a Campfire record changes.”
  • “Create a Genie that answers questions about our Campfire data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

Explore Campfire connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

240 integration guides

CRM · 38

ERP · 38

Database · 50

Data warehouse · 29

Business productivity · 28

Accounting and finance · 17

AI · 5

Developer tools · 11

Human resources · 14

Security and identity · 6

Storage · 4

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started