Real-time
Two-way sync
Changes in Intercom or MongoDB instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Intercom to MongoDB integration — real-time, two-way sync
Keep Intercom and MongoDB 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 Intercom and MongoDB
Treat Intercom like part of your database: its records live in MongoDB as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in MongoDB, where it can be queried and joined like everything else.
Stacksync mirrors Companies, Conversations, Tickets, Data Events from Intercom into Embedded documents and arrays, Indexes, Views, Change streams in MongoDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Intercom with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Common use cases
- 01 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
- 02 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 03 Sync MongoDB collections with a CRM so customer documents written by the application appear as CRM records, and CRM edits flow back as document updates.
- 04 Replicate operational MongoDB data into a relational database, flattening nested documents into normalized tables for SQL reporting.
Common sync patterns
Product events onto CRM records
Signup, usage, or lifecycle changes written to MongoDB sync onto the matching records in Intercom, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Intercom API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Intercom arrive as row changes in MongoDB, ready to drive jobs and notifications.
What you can sync between Intercom and MongoDB
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.
| Intercom objects | MongoDB objects | How this pairing syncs | |
|---|---|---|---|
| Admins & Teams Teammate records map conversation ownership to CRM users. | Embedded documents and arrays Nested structures that syncs flatten or map to related records in relational targets. | Admins & Teams is specific to Intercom and Embedded documents and arrays to MongoDB — each maps to any object or custom field on the other side. | |
| Articles Help center content is accessible via API for knowledge sync and audits. | Indexes Keep lookups by sync key fast on large collections. | Articles is specific to Intercom and Indexes to MongoDB — each maps to any object or custom field on the other side. | |
| Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Views Read-only aggregation-defined sources for filtered sync datasets. | Contacts is specific to Intercom and Views to MongoDB — each maps to any object or custom field on the other side. | |
| Companies Company records group contacts and carry plan and account attributes used in segmentation. | Change streams The oplog-backed event feed that powers real-time change capture. | Companies is specific to Intercom and Change streams to MongoDB — each maps to any object or custom field on the other side. | |
| Conversations Support and sales threads sync outward for analytics and CRM context. | GridFS files Chunked file storage whose metadata can be referenced by synced documents. | Conversations is specific to Intercom and GridFS files to MongoDB — each maps to any object or custom field on the other side. | |
| Tickets Structured ticket records track issues alongside conversational threads. | Databases Logical groupings of collections that scope a sync connection. | Tickets is specific to Intercom and Databases to MongoDB — each maps to any object or custom field on the other side. |
How changes propagate between Intercom and MongoDB
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.
Intercom MongoDB Sub-second propagation
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 applied to MongoDB as a row-level write, with types converted between the two schemas.
MongoDB Intercom Sub-second propagation
DetectionChanges in MongoDB are captured at the source via change data capture — no polling loop against its API. MongoDB oplog and change streams (requires the database to run as a replica set — even single-node).
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Intercom ⇄ MongoDB
Connect Intercom and MongoDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–MongoDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom or MongoDB 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 Intercom or MongoDB record.
Observability
Monitoring
Track your Intercom ⇄ MongoDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Intercom and MongoDB.
How the Intercom and MongoDB connectors work
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
MongoDB
- Integration surface
- MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management
- Authentication
- Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required
- Change detection
- MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time
- Capabilities
- read · write · CDC
How it works
How to connect Intercom to MongoDB — 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 Intercom and MongoDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Intercom
connected
MongoDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom and MongoDB 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 · Intercom ⇄ MongoDBCustomers 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.
Intercom MongoDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and MongoDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and MongoDB: authenticate both systems, choose the objects to sync (such as Intercom's Admins & Teams and Articles), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and MongoDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–MongoDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Intercom and MongoDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. On MongoDB: MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Intercom side: Companies, Conversations, Tickets, Data Events, plus custom fields where Intercom exposes them. On the MongoDB side: Embedded documents and arrays, Indexes, Views, Change streams. 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.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 547 integrations available for Intercom and MongoDB.
Popular · 8 of 547
-
Intercom ⇄ Azure Cosmos DB -
Intercom ⇄ Azure SQL Database -
Intercom ⇄ Citus -
Intercom ⇄ Couchbase -
MongoDB ⇄ Zoho CRM -
MongoDB ⇄ Shopify -
MongoDB ⇄ Affinity -
MongoDB ⇄ 6sense
No integrations match .
