Two-way sync
Changes in Gorgias or Intercom instantly reflect in both systems. No stale data, no manual imports.
Keep Gorgias and Intercom in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Custom fields, Tickets, Messages, Customers in Gorgias with Companies, Conversations, Tickets, Data Events in Intercom in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
Deal stage and value on shared accounts stay visible from either CRM.
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.
| Gorgias objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Tickets The central support object, aggregating a conversation across channels. | Tickets Structured ticket records track issues alongside conversational threads. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tags Categorize tickets for routing and downstream analytics. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Messages Individual inbound and outbound messages attached to a ticket. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Messages is specific to Gorgias and Contacts to Intercom — each maps to any object or custom field on the other side. | |
| Customers Unified shopper profiles that merge identities across connected stores. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Customers is specific to Gorgias and Companies to Intercom — each maps to any object or custom field on the other side. | |
| Users (agents) Support staff records used for assignment and workload reporting. | Conversations Support and sales threads sync outward for analytics and CRM context. | Users (agents) is specific to Gorgias and Conversations to Intercom — each maps to any object or custom field on the other side. | |
| Satisfaction surveys CSAT responses synced out for support quality reporting. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | Satisfaction surveys is specific to Gorgias and Data Events to Intercom — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionGorgias notifies Stacksync of record changes through webhook events. Webhooks for ticket and message events, supplemented by polling with updated-at cursors.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Gorgias through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gorgias–Intercom connection.
Changes in Gorgias or Intercom instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Gorgias or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Gorgias or Intercom record.
Track your Gorgias ⇄ Intercom sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Gorgias and Intercom.
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.
Authenticate Gorgias and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Gorgias and Intercom 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Gorgias and Intercom: authenticate both systems, choose the objects to sync (such as Gorgias's Tickets and Tags), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Gorgias side: Custom fields, Tickets, Messages, Customers, plus custom fields where Gorgias 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 Gorgias and Intercom: Migration with a parallel run; Divisional or regional split; Where both track pipeline: deal visibility across systems. When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Gorgias: REST API. Authentication: API key paired with the account email over HTTP Basic auth; OAuth 2.0 for public apps. 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.
Gorgias: Tickets aggregate messages from email, live chat, SMS, and social channels into a single object, so one synced record covers the full conversation. Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. Stacksync's field mapping accounts for these differences between Gorgias and Intercom without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 516 integrations available for Gorgias and Intercom.