Real-time
Two-way sync
Changes in Cin7 or Notion instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Business productivity
Cin7 to Notion integration — real-time, two-way sync
Keep Cin7 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 Cin7 and Notion
Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Notion and Cin7.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Notion is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Properties, Blocks, Formula and Rollup properties, Users in Notion with Credit notes / returns, Products, Inventory levels, Sales orders in Cin7 bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
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 Sync sales orders from Cin7 into an accounting platform or warehouse for revenue and margin reporting.
- 04 Keep customer records aligned between Cin7 and the CRM to remove duplicate account entry.
Common sync patterns
Master data corrections travel
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Where Notion faces customers and Cin7 carries account records
Order, invoice, or account status from Cin7 appears alongside the customer in Notion, so front-line teams answer from live data.
Where Cin7 is the HR or people system of record
Worker and organization data from Cin7 stays current in Notion, so the tools people use daily reflect the org as it actually is.
What you can sync between Cin7 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.
| Cin7 objects | Notion objects | How this pairing syncs | |
|---|---|---|---|
| Credit notes / returns Return documents synced so finance and support see the same refund state. | Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Credit notes / returns is specific to Cin7 and Blocks to Notion — each maps to any object or custom field on the other side. | |
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. | Products is specific to Cin7 and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side. | |
| Inventory levels Stock on hand by branch or location, published outward for availability. | Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. | Inventory levels is specific to Cin7 and Users to Notion — each maps to any object or custom field on the other side. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. | Sales orders is specific to Cin7 and Comments to Notion — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | 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. | Purchase orders is specific to Cin7 and Files and attachments to Notion — each maps to any object or custom field on the other side. | |
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | 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 Cin7 and Pages to Notion — each maps to any object or custom field on the other side. |
How changes propagate between Cin7 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.
Cin7 Notion Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.
Notion Cin7 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 Cin7 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
- 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 Cin7 ⇄ Notion
Connect Cin7 and Notion for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Notion connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 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 Cin7 or Notion record.
Observability
Monitoring
Track your Cin7 ⇄ Notion sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Cin7 and Notion.
How the Cin7 and Notion connectors work
Cin7
- Integration surface
- REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
- Authentication
- API key credentials (paired with a username or account ID, depending on the product)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
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 Cin7 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 Cin7 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.
Cin7
connected
Notion
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 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 · Cin7 ⇄ 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.
Cin7 NotionCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Notion integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Notion: authenticate both systems, choose the objects to sync (such as Cin7's Credit notes / returns and Products), 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 Cin7 and Notion: Master data corrections travel; Where Notion faces customers and Cin7 carries account records; Where Cin7 is the HR or people system of record. A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
-
Cin7: REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs. Authentication: API key credentials (paired with a username or account ID, depending on the product). 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: Formula and rollup property values are computed by Notion and are read-only; they cannot be written back. Cin7: Order objects carry channel context (POS, B2B, e-commerce), which downstream reporting syncs typically preserve for channel-level margin analysis. Stacksync's field mapping accounts for these differences between Cin7 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 Cin7 and Notion records are not retained after a sync operation.
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 505 integrations available for Cin7 and Notion.
Popular · 4 of 505
No integrations match .
