Real-time
Two-way sync
Changes in Drift or Intercom instantly reflect in both systems. No stale data, no manual imports.
CRM
Drift to Intercom integration — real-time, two-way sync
Keep Drift 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.
- 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 Drift and Intercom
Run Drift and Intercom side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.
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 Playbooks, Meetings, Contacts, Conversations in Drift with Articles, Contacts, Companies, Conversations 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.
Common use cases
- 01 Sync meetings booked in Drift to CRM activities so pipeline attribution stays accurate.
- 02 Archive historical Drift conversation and contact data into a warehouse ahead of a platform migration.
- 03 Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
- 04 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
Common sync patterns
Post-acquisition consolidation
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
Migration with a parallel run
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Divisional or regional split
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
What you can sync between Drift and Intercom
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.
| Drift objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Visitor and lead records created or matched from chat identities; the main CRM-sync object. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Conversations Chat threads with status and participants; the center of Drift's data model. | Conversations Support and sales threads sync outward for analytics and CRM context. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Users Agents and sales reps who own conversations and meetings. | Tickets Structured ticket records track issues alongside conversational threads. | Users is specific to Drift and Tickets to Intercom — each maps to any object or custom field on the other side. | |
| Playbooks Bot flows that generate conversations and qualify visitors. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | Playbooks is specific to Drift and Data Events to Intercom — each maps to any object or custom field on the other side. | |
| Meetings Meetings booked through Drift, synced to CRM as sales activities. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Meetings is specific to Drift and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side. | |
| Messages Individual messages within a conversation, used for transcript and intent analysis. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Messages is specific to Drift and Tags to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Drift and Intercom
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.
Drift Intercom Sub-second propagation
DetectionDrift notifies Stacksync of record changes through webhook events. Webhook events for new conversations, messages, and contact changes.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Drift 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 written to Drift through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Drift: Subject to the platform's API rate limits.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Drift ⇄ Intercom
Connect Drift and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Drift–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Drift or Intercom 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 Drift or Intercom record.
Observability
Monitoring
Track your Drift ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Drift and Intercom.
How the Drift and Intercom connectors work
Drift
- Integration surface
- REST API
- Authentication
- OAuth 2.0 via apps registered on the Drift developer platform
- Change detection
- Webhook events for new conversations, messages, and contact changes; polling for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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
How it works
How to connect Drift to Intercom — 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 Drift 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.
Drift
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Drift 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.
objects · Drift ⇄ IntercomCustomers 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.
Drift IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Drift and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Drift and Intercom: authenticate both systems, choose the objects to sync (such as Drift's Contacts and Conversations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Drift and Intercom. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Drift: Webhook events for new conversations, messages, and contact changes; polling for backfills. On Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Drift side: Playbooks, Meetings, Contacts, Conversations, plus custom fields where Drift exposes them. On the Intercom side: Articles, Contacts, Companies, Conversations. 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 Drift and Intercom: Post-acquisition consolidation; Migration with a parallel run; Divisional or regional split. Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
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 288 integrations available for Drift and Intercom.
Popular · 3 of 288
No integrations match .
