Real-time
Two-way sync
Changes in Kommo or Notion instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Kommo to Notion integration — real-time, two-way sync
Keep Kommo 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 Kommo and Notion
Sync what happens in Notion with the customer records in Kommo, 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 Formula and Rollup properties, Users, Comments, Files and attachments in Notion to Pipelines & Statuses, Tasks, Notes, Custom Fields in Kommo with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Kommo, and CRM data flows the other way wherever Notion can store and use it.
Common use cases
- 01 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
- 02 Read Notion wiki Pages and their Blocks into a database or search index for internal knowledge retrieval.
- 03 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 04 Keep customer records consistent between Kommo and invoicing or ERP systems
Common sync patterns
Where Notion supplies contact or company data
Enriched fields land directly on records in Kommo, and refreshes keep them from going stale.
Where Notion can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Kommo sync into Notion, so people working there have the context without switching tools.
What you can sync between Kommo 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.
| Kommo objects | Notion objects | How this pairing syncs | |
|---|---|---|---|
| Users Account users map lead 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. | |
| Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. | Chats is specific to Kommo and Pages to Notion — each maps to any object or custom field on the other side. | |
| Leads The central pipeline record; external signups and form fills sync in as leads. | 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. | Leads is specific to Kommo and Databases / Data sources to Notion — each maps to any object or custom field on the other side. | |
| Contacts Person records sync with other CRMs and databases for a shared contact file. | Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. | Contacts is specific to Kommo and Properties to Notion — each maps to any object or custom field on the other side. | |
| Companies Organization records map to accounts in ERPs and invoicing tools. | Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Companies is specific to Kommo and Blocks to Notion — each maps to any object or custom field on the other side. | |
| Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. | Pipelines & Statuses is specific to Kommo and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side. |
How changes propagate between Kommo 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.
Kommo Notion Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.
DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.
Notion Kommo 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 Kommo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kommo: Subject to per-account request 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 Kommo ⇄ Notion
Connect Kommo and Notion for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Notion connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo 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 Kommo or Notion record.
Observability
Monitoring
Track your Kommo ⇄ Notion sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kommo and Notion.
How the Kommo and Notion connectors work
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request 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 Kommo 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 Kommo 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.
Kommo
connected
Notion
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo 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 · Kommo ⇄ 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.
Kommo NotionCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Notion integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Notion: authenticate both systems, choose the objects to sync (such as Kommo's Users and Chats), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Kommo 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 Kommo, and refreshes keep them from going stale.
-
Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. 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. Kommo: As a messenger-first CRM, chat threads from channels like WhatsApp and Instagram attach directly to leads, which is context most other CRMs lack when records are synced across. Stacksync's field mapping accounts for these differences between Kommo 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 Kommo and Notion records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Kommo and Notion connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Kommo–Notion integration in-house.
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 523 integrations available for Kommo and Notion.
Popular · 6 of 523
No integrations match .
