Campfire to Intercom integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Campfire and Intercom: authenticate both systems, choose the objects to sync (such as Campfire's Bank Account and Bank Transaction), map fields visually, and changes propagate both ways in milliseconds — no code required.

On the Campfire side: Fixed Asset, Fixed Asset Class, Bill, Debit Memo, plus custom fields where Campfire exposes them. On the Intercom side: Companies, Conversations, Tickets, Data Events. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Campfire and Intercom: Where Campfire handles support or shared inboxes; Where Campfire supplies contact or company data; Where Campfire can store CRM context: fields kept current. Tickets and conversations attach to the right contact and account in Intercom, so sales sees open issues before the next call.

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. Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Stacksync manages authentication, retries, and rate limits on both sides.

Campfire: Fixed Asset Automation Match and Vendor Summary have no delete detection (objects cannot be deleted). Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. Stacksync's field mapping accounts for these differences between Campfire and Intercom without custom code.