Intercom to Sage 100 integration — real-time, two-way sync

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

On the Intercom side: Companies, Conversations, Tickets, Data Events, plus custom fields where Intercom exposes them. On the Sage 100 side: Inventory Items, Sales Orders, AR Invoices, Purchase Orders. 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 Intercom and Sage 100: Where Sage 100 is the finance system of record: money status on the account; One customer master; Where Sage 100 manages people and org data: keep Intercom aligned. Invoice and payment state from Sage 100 shows on the account in Intercom, so reps see balances before promising the next order.

Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Sage 100: ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes. Authentication: Sage 100 company and user credentials; ODBC DSN credentials for direct reads. Stacksync manages authentication, retries, and rate limits on both sides.

Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. Sage 100: Writes should go through the Business Object Interface rather than direct file access, so module validation and GL postings are enforced. Stacksync's field mapping accounts for these differences between Intercom and Sage 100 without custom code.