Two-way sync
Changes in Braze or Intercom instantly reflect in both systems. No stale data, no manual imports.
Keep Braze 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.
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 Braze 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 Canvases, Subscription Groups, Content Blocks, Users in Braze to Data Events, Custom Data Attributes, Tags, Segments in Intercom with bi-directional, real-time sync. Activity and record changes in Braze update the matching contact or account in Intercom, and CRM data flows the other way wherever Braze can store and use it.
Charges, refunds, and subscription changes appear on the account in Intercom, so revenue context lives with the relationship.
Owner, lifecycle stage, or account details from Intercom sync into Braze, so people working there have the context without switching tools.
Prospects, sends, and replies sync into Intercom, keeping lead status current without manual imports.
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.
| Braze objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Segments Audience definitions read for membership export and campaign targeting. | Segments Saved audience definitions are readable for targeting parity across tools. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Canvases Multi-step journeys; entry and performance data is read for lifecycle analysis. | Tickets Structured ticket records track issues alongside conversational threads. | Canvases is specific to Braze and Tickets to Intercom — each maps to any object or custom field on the other side. | |
| Subscription Groups Channel-level opt-in states synced with consent records in other systems. | Data Events Behavioral events pushed in from product databases trigger messages and flows. | Subscription Groups is specific to Braze and Data Events to Intercom — each maps to any object or custom field on the other side. | |
| Content Blocks Reusable message content referenced across campaigns. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Content Blocks is specific to Braze and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side. | |
| Users The central profile object, identified by external ID, Braze ID, or user aliases; the main sync target. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Users is specific to Braze and Tags to Intercom — each maps to any object or custom field on the other side. | |
| Custom Attributes Profile fields written from CRMs, warehouses, and product databases to drive personalization. | Admins & Teams Teammate records map conversation ownership to CRM users. | Custom Attributes is specific to Braze and Admins & Teams 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.
DetectionStacksync polls Braze for changes on an incremental schedule, reading only records changed since the previous pass. Braze Currents streams engagement events outward.
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 Braze through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Braze–Intercom connection.
Changes in Braze or Intercom instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Braze 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 Braze or Intercom record.
Track your Braze ⇄ Intercom sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Braze 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 Braze 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 Braze 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 Braze and Intercom: authenticate both systems, choose the objects to sync (such as Braze's Segments and Canvases), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Braze side: Canvases, Subscription Groups, Content Blocks, Users, plus custom fields where Braze exposes them. On the Intercom side: Data Events, Custom Data Attributes, Tags, Segments. 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 Braze and Intercom: Where Braze processes payments; Where Braze can store CRM context: fields kept current; Where Braze runs outreach. Charges, refunds, and subscription changes appear on the account in Intercom, so revenue context lives with the relationship.
Braze: REST API. Authentication: REST API keys scoped to specific endpoints, issued per workspace. 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.
Braze: The users/track endpoint accepts attributes, custom events, and purchases for many users in a single batched request, which is the standard write path for syncs. Intercom: API behavior is pinned per app using a version header, so integrations control when they adopt breaking changes. Stacksync's field mapping accounts for these differences between Braze 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 506 integrations available for Braze and Intercom.