Real-time
Two-way sync
Changes in Close or Notion instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Close to Notion integration — real-time, two-way sync
Keep Close 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 Close and Notion
Sync what happens in Notion with the customer records in Close, 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 Files and attachments, Pages, Databases / Data sources, Properties in Notion to Users, Smart Views, Leads, Contacts in Close with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Close, and CRM data flows the other way wherever Notion can store and use it.
Common use cases
- 01 Read Notion wiki Pages and their Blocks into a database or search index for internal knowledge retrieval.
- 02 Two-way sync a Notion projects or tasks data source with a Postgres table so engineers work in SQL while the team edits Pages in Notion, mapping status, date, and assignee properties both ways.
- 03 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
- 04 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
Common sync patterns
Where Notion can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Close sync into Notion, so people working there have the context without switching tools.
Where Notion supplies contact or company data
Enriched fields land directly on records in Close, and refreshes keep them from going stale.
What you can sync between Close 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.
| Close objects | Notion objects | How this pairing syncs | |
|---|---|---|---|
| Users Sales reps referenced as owners on leads, opportunities, and activities. | 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. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. | Leads is specific to Close and Properties to Notion — each maps to any object or custom field on the other side. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Contacts is specific to Close and Blocks to Notion — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. | Opportunities is specific to Close and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. | Activities is specific to Close and Comments to Notion — each maps to any object or custom field on the other side. | |
| Tasks Follow-up items assigned to users; synced for workload and SLA reporting. | 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. | Tasks is specific to Close and Files and attachments to Notion — each maps to any object or custom field on the other side. |
How changes propagate between Close 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.
Close Notion Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.
Notion Close 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 Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- 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 Close ⇄ Notion
Connect Close and Notion for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Notion connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close 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 Close or Notion record.
Observability
Monitoring
Track your Close ⇄ Notion sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Notion.
How the Close and Notion connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
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 Close 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 Close 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.
Close
connected
Notion
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close 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 · Close ⇄ 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.
Close NotionCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Notion integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Notion: authenticate both systems, choose the objects to sync (such as Close's Users and Leads), 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 Close and Notion: Where Notion can store CRM context: fields kept current; Where Notion supplies contact or company data. Owner, lifecycle stage, or account details from Close sync into Notion, so people working there have the context without switching tools.
-
Close: REST API. Authentication: API key (sent via HTTP Basic auth). 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: Every page, block, database, and data source is keyed by a UUID; there is no per-record numeric ID. Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. Stacksync's field mapping accounts for these differences between Close 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 Close 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 534 integrations available for Close and Notion.
Popular · 7 of 534
-
Close ⇄ Adobe Sign -
Close ⇄ Asana -
Close ⇄ Docusign -
Close ⇄ Gatekeeper -
Notion ⇄ Outreach -
Notion ⇄ Salesloft -
Notion ⇄ SAP Sales Cloud
No integrations match .
