Two-way sync
Changes in Intercom or Notion instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom and Notion 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 Notion 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 Properties, Blocks, Formula and Rollup properties, Users in Notion to Custom Data Attributes, Tags, Segments, Admins & Teams in Intercom with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Intercom, and CRM data flows the other way wherever Notion can store and use it.
Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.
Owner, lifecycle stage, or account details from Intercom sync into Notion, so people working there have the context without switching tools.
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 | Notion objects | How this pairing syncs | |
|---|---|---|---|
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. | Tags is specific to Intercom and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. | Segments is specific to Intercom and Users to Notion — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. | Admins & Teams is specific to Intercom and Comments to Notion — 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. | Files and attachments File-property and file-block values. Notion-hosted URLs are temporary and expire, so files are re-fetched or copied at sync time. | Articles is specific to Intercom and Files and attachments to Notion — 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. | Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. | Contacts is specific to Intercom and Pages to Notion — 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. | Databases / Data sources Collections of pages with a typed property schema. Since the 2025-09-03 API a database is a container holding one or more data sources; syncs target a specific data_source_id. | Companies is specific to Intercom and Databases / Data sources to Notion — 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.
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 Notion through its API, with automatic retries and rate-limit backoff.
DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Notion connection.
Changes in Intercom or Notion instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Notion data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Notion record.
Track your Intercom ⇄ Notion sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Notion.
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 Intercom and Notion 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 Intercom and Notion 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 Intercom and Notion: authenticate both systems, choose the objects to sync (such as Intercom's Tags and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Intercom and Notion: Where Notion supplies contact or company data; Where Notion can store CRM context: fields kept current. Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Notion: REST API (api.notion.com/v1). Authentication: OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header. Stacksync manages authentication, retries, and rate limits on both sides.
Notion: Notion-hosted file URLs are temporary and expire after about an hour, so files must be re-fetched or copied during a sync. 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 Intercom and Notion 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 Intercom and Notion records are not retained after a sync operation.
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 518 integrations available for Intercom and Notion.