Real-time
Two-way sync
Changes in Campfire or Pigment instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Accounting and finance
Campfire to Pigment integration — real-time, two-way sync
Keep Campfire and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
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
Why teams connect Campfire and Pigment
Connect the financial records in Pigment with the work happening in Campfire, so both stay current without exports or copy-paste.
Pigment holds the financial truth: who the customers are, what they were billed, what they paid. Campfire is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Data imports, Users and permissions, Applications, Metrics in Pigment and Debit Memo, Invoice, Credit Memo, Bank Account in Campfire in sync, bi-directionally and in real time. Whatever records Campfire keeps and whatever events it produces, the overlap with Pigment is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Common use cases
- Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- Send scheduled digest messages built from synced database queries.
- Post alerts into a room when records change in a synced system such as a CRM or an operational database.
Where Campfire handles customer conversations: billing context in view
Front-line teams see invoice and payment status from Pigment next to the customer they are helping, without logging into the finance system.
Where Campfire collects payments or triggers charges: events land in Pigment
Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
Where Campfire tracks people or companies: one identity
A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.
What you can sync between Campfire and Pigment
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Campfire objects | Pigment objects | |
|---|---|---|
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | Users and permissions Access controls governing which model areas a sync can touch | |
| Intercompany Journal Entry Synced with incremental and full sync per the Stacksync docs. | Applications Planning models organized by domain such as finance, sales, or workforce | |
| Chart of Accounts Synced with incremental and full sync per the Stacksync docs. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | |
| Chart Transaction Synced with incremental and full sync per the Stacksync docs. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | |
| Fixed Asset Synced with incremental and full sync per the Stacksync docs. | Tables Row-based transactional data loaded into models from source systems | |
| Fixed Asset Class Synced with incremental and full sync per the Stacksync docs. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context |
What ships with Campfire ⇄ Pigment
Connect Campfire and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Campfire–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Campfire or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Campfire or Pigment record.
Observability
Monitoring
Track your Campfire ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Campfire and Pigment.
How the Campfire and Pigment connectors work
Campfire
- Integration surface
- HTTP endpoints for bot integrations on a self-hosted instance
- Authentication
- 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
- Change detection
- Near real-time updates via change tracking (incremental sync); delete detection per object (some objects detected every 24h)
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Limits depend on the self-hosted deployment; confirm against the instance's documentation.
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Campfire to Pigment — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Campfire and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Campfire
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Campfire and Pigment objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Campfire ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Campfire PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Campfire and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Campfire and Pigment: authenticate both systems, choose the objects to sync (such as Campfire's Journal Entry and Intercompany Journal Entry), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Campfire and Pigment: Where Campfire handles customer conversations: billing context in view; Where Campfire collects payments or triggers charges: events land in Pigment; Where Campfire tracks people or companies: one identity. Front-line teams see invoice and payment status from Pigment next to the customer they are helping, without logging into the finance system.
-
Campfire: HTTP endpoints for bot integrations on a self-hosted instance. Authentication: 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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. Campfire: Fixed Asset Automation Match and Vendor Summary have no delete detection (objects cannot be deleted). Stacksync's field mapping accounts for these differences between Campfire and Pigment without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Campfire and Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Campfire and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Campfire–Pigment integration in-house.
SECURITY
Security teams love 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.
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Campfire and Pigment.
Popular · 8 of 386
-
Campfire ⇄ QuickBooks -
Campfire ⇄ Stripe -
Campfire ⇄ Rillet -
Campfire ⇄ Workday -
Pigment ⇄ Orderful -
Pigment ⇄ Resend - Pigment ⇄ ServiceNow
-
Pigment ⇄ Slack
No integrations match .
