Skip to content
Business productivity ⇄ CRM

Notion to Salesforce integration — real-time, two-way sync

Keep Notion and Salesforce 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 Notion and Salesforce

Sync what happens in Notion with the customer records in Salesforce, 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 Pages, Databases / Data sources, Properties, Blocks in Notion to Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Salesforce, and CRM data flows the other way wherever Notion can store and use it.

Common use cases

  • 01 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.
  • 02 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.
  • 03 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 04 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

Common sync patterns

Where Notion can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Salesforce 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 Salesforce, and refreshes keep them from going stale.

What you can sync between Notion and Salesforce

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 Salesforce objects How this pairing syncs
Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Formula and Rollup properties is specific to Notion and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Users is specific to Notion and Products and Price Books to Salesforce — 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. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Comments is specific to Notion and Custom Objects to Salesforce — 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. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Files and attachments is specific to Notion and Accounts to Salesforce — 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. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Pages is specific to Notion and Contacts to Salesforce — each maps to any object or custom field on the other side.
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 Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. Databases / Data sources is specific to Notion and Leads to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Notion and Salesforce

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.

Notion Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Notion Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • 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.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Notion ⇄ Salesforce

Connect Notion and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Notion–Salesforce connection.

Real-time

Two-way sync

Changes in Notion or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Notion or Salesforce 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 Notion or Salesforce record.

Observability

Monitoring

Track your Notion ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Notion and Salesforce.

How the Notion and Salesforce connectors work

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.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Notion to Salesforce — 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.

  1. 01

    Connect your apps

    Authenticate Notion and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Notion connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Notion and Salesforce 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Notion ⇄ Salesforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Notion Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Notion and Salesforce integration FAQ

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 542 integrations available for Notion and Salesforce.

Popular · 8 of 542
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.