Real-time
Two-way sync
Changes in Kustomer or Notion instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Kustomer to Notion integration — real-time, two-way sync
Keep Kustomer 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.
- 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 Kustomer and Notion
Sync what happens in Notion with the customer records in Kustomer, 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 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 Blocks, Formula and Rollup properties, Users, Comments in Notion to Teams, Tags, Notes, Customers in Kustomer with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Kustomer, and CRM data flows the other way wherever Notion can store and use it.
Common use cases
- 01 Push rows from a warehouse or another database into a Notion data source as Pages so ops and leadership read live metrics in a familiar Notion view.
- 02 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
- 03 Escalate conversation-derived signals into the CRM as tasks or opportunities
- 04 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
Common sync patterns
Where Notion supplies contact or company data
Enriched fields land directly on records in Kustomer, and refreshes keep them from going stale.
Where Notion can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Kustomer sync into Notion, so people working there have the context without switching tools.
What you can sync between Kustomer and Notion
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.
| Kustomer objects | Notion objects | How this pairing syncs | |
|---|---|---|---|
| Users Agent records map conversation ownership to people in other systems. | Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. | Custom Objects (Klasses) is specific to Kustomer and Properties to Notion — each maps to any object or custom field on the other side. | |
| Teams Team assignments support routing parity and reporting. | Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Teams is specific to Kustomer and Blocks to Notion — each maps to any object or custom field on the other side. | |
| Tags Labels on conversations and customers sync for categorization and analytics. | 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 Kustomer and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side. | |
| Notes Internal annotations carry context alongside synced conversations. | Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. | Notes is specific to Kustomer and Comments to Notion — each maps to any object or custom field on the other side. | |
| Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | 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. | Customers is specific to Kustomer and Files and attachments to Notion — each maps to any object or custom field on the other side. |
How changes propagate between Kustomer and Notion
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.
Kustomer Notion Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.
Notion Kustomer Sub-second propagation
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 Kustomer through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kustomer: Subject to the platform's API rate limits.
- Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
What ships with Kustomer ⇄ Notion
Connect Kustomer and Notion for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kustomer–Notion connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kustomer or Notion 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 Kustomer or Notion record.
Observability
Monitoring
Track your Kustomer ⇄ Notion sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kustomer and Notion.
How the Kustomer and Notion connectors work
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
Notion
- Integration surface
- 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
- Change detection
- Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
- Capabilities
- read · write · webhooks
- Rate limits
- Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
How it works
How to connect Kustomer to Notion — 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 Kustomer 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.
Kustomer
connected
Notion
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kustomer 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.
objects · Kustomer ⇄ NotionCustomers 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.
Kustomer NotionCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kustomer and Notion integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kustomer and Notion: authenticate both systems, choose the objects to sync (such as Kustomer's Users and Custom Objects (Klasses)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Notion side: Blocks, Formula and Rollup properties, Users, Comments, plus custom fields where Notion exposes them. On the Kustomer side: Teams, Tags, Notes, Customers. 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 Kustomer 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 Kustomer, and refreshes keep them from going stale.
-
Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. 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: The 2025-09-03 API version splits databases (containers) from data sources (tables); queries and syncs target a data_source_id, and one database can hold multiple data sources. Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Stacksync's field mapping accounts for these differences between Kustomer and Notion without custom code.
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
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 423 integrations available for Kustomer and Notion.
Popular · 5 of 423
-
Kustomer ⇄ Microsoft Dynamics 365 -
Notion ⇄ Dun And Bradstreet -
Notion ⇄ Seismic -
Notion ⇄ Xactly -
Notion ⇄ Gong
No integrations match .
