Two-way sync
Changes in Notion or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Keep Notion and Nutshell 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 Pages, Databases / Data sources, Properties, Blocks in Notion to Companies, Activities, Tasks, Notes in Nutshell with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Nutshell, and CRM data flows the other way wherever Notion can store and use it.
Owner, lifecycle stage, or account details from Nutshell sync into Notion, so people working there have the context without switching tools.
Enriched fields land directly on records in Nutshell, and refreshes keep them from going stale.
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.
| Notion objects | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. | Users Rep records used to resolve ownership when syncing assignments | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Blocks is specific to Notion and Notes to Nutshell — each maps to any object or custom field on the other side. | |
| 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 Line items attached to leads, used to sync sold products into billing | Formula and Rollup properties is specific to Notion and Products to Nutshell — each maps to any object or custom field on the other side. | |
| Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. | Tags Segmentation labels mapped to lists or filters in downstream tools | Comments is specific to Notion and Tags to Nutshell — each maps to any object or custom field on the other side. | |
| 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. | Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Files and attachments is specific to Notion and Leads to Nutshell — each maps to any object or custom field on the other side. | |
| Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. | People Individual contacts, kept consistent with marketing and outreach tools | Pages is specific to Notion and People to Nutshell — 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.
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 Nutshell through its API, with automatic retries and rate-limit backoff.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Notion–Nutshell connection.
Changes in Notion or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Notion or Nutshell data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Notion or Nutshell record.
Track your Notion ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Notion and Nutshell.
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 Notion and Nutshell 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 Notion and Nutshell 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 Notion and Nutshell: authenticate both systems, choose the objects to sync (such as Notion's Users and Blocks), 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 Notion and Nutshell: Where Notion can store CRM context: fields kept current; Where Notion supplies contact or company data. Owner, lifecycle stage, or account details from Nutshell sync into Notion, so people working there have the context without switching tools.
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. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. 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. Nutshell: Nutshell's most full-featured API is JSON-RPC: each call names a method such as findLeads or editLead instead of hitting resource URLs, though a newer REST API is also available. Stacksync's field mapping accounts for these differences between Notion and Nutshell 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 Notion and Nutshell 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 425 integrations available for Notion and Nutshell.