Real-time
Two-way sync
Changes in Customer.io or Intercom instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Customer.io to Intercom integration — real-time, two-way sync
Keep Customer.io 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 Customer.io and Intercom
Sync what happens in Customer.io with the customer records in Intercom, in real time and in both directions.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Customer.io holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects Events, Segments, Campaigns, Broadcasts in Customer.io to Tickets, Data Events, Custom Data Attributes, Tags in Intercom with bi-directional, real-time sync. Activity and record changes in Customer.io update the matching contact or account in Intercom, and CRM data flows the other way wherever Customer.io can store and use it.
Common use cases
- Keep unsubscribe and subscription-preference state consistent between Customer.io and the CRM to avoid compliance gaps.
- Sync account-level objects and their person relationships for B2B messaging keyed to company attributes.
- Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
Where Customer.io runs outreach
Prospects, sends, and replies sync into Intercom, keeping lead status current without manual imports.
Where Customer.io supplies contact or company data
Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.
Where Customer.io processes payments
Charges, refunds, and subscription changes appear on the account in Intercom, so revenue context lives with the relationship.
What you can sync between Customer.io 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.
| Customer.io objects | Intercom objects | |
|---|---|---|
| Events Behavioral events sent via the Track API that trigger campaigns. | Articles Help center content is accessible via API for knowledge sync and audits. | |
| Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | |
| Campaigns Automated workflows whose membership and metrics can be read via the App API. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | |
| Broadcasts One-off sends to segments or audiences, triggerable via API. | Conversations Support and sales threads sync outward for analytics and CRM context. | |
| Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. | Tickets Structured ticket records track issues alongside conversational threads. | |
| Newsletters Recurring email sends with performance metrics available for reporting syncs. | Data Events Behavioral events pushed in from product databases trigger messages and flows. |
What ships with Customer.io ⇄ Intercom
Connect Customer.io and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Customer.io–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Customer.io 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 Customer.io or Intercom record.
Observability
Monitoring
Track your Customer.io ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Customer.io and Intercom.
How the Customer.io and Intercom connectors work
Customer.io
- Integration surface
- REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
- Authentication
- Basic auth with site ID and API key for the Track API; bearer token for the App API
- Change detection
- Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-API rate limits documented by Customer.io
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 Customer.io 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 Customer.io 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.
Customer.io
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Customer.io 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 · Customer.io ⇄ 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.
Customer.io IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Customer.io and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Customer.io and Intercom: authenticate both systems, choose the objects to sync (such as Customer.io's Events and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Customer.io: Beyond people, Customer.io supports non-person objects (for example accounts) with typed relationships to people, enabling account-based messaging logic. 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 Customer.io and Intercom without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Customer.io and Intercom records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Customer.io and Intercom connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Customer.io–Intercom integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Customer.io and Intercom. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Customer.io: Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection. 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.
SECURITY
Security teams love 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
CSA STAR
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 386 integrations available for Customer.io and Intercom.
Popular · 8 of 386
-
Customer.io ⇄ Pipedrive -
Customer.io ⇄ Zoho CRM -
Customer.io ⇄ Shopify -
Customer.io ⇄ Affinity -
Intercom ⇄ eClinicalWorks -
Intercom ⇄ Full Enrich -
Intercom ⇄ Google Sheets -
Intercom ⇄ Klaviyo
No integrations match .
