Real-time
Two-way sync
Changes in Freshsales or Notion instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Freshsales to Notion integration — real-time, two-way sync
Keep Freshsales 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 Freshsales and Notion
Sync what happens in Notion with the customer records in Freshsales, 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 Databases / Data sources, Properties, Blocks, Formula and Rollup properties in Notion to Tasks, Appointments, Notes, Sales activities in Freshsales with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Freshsales, 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 deals into a data warehouse for pipeline reporting alongside product usage data.
- 04 Push product-qualified leads from the warehouse into Freshsales as contacts with lifecycle stages set.
Common sync patterns
Where Notion can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Freshsales 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 Freshsales, and refreshes keep them from going stale.
What you can sync between Freshsales 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.
| Freshsales objects | Notion objects | How this pairing syncs | |
|---|---|---|---|
| Sales activities Configurable activity types logged against records, useful for engagement scoring. | Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Sales activities is specific to Freshsales and Blocks to Notion — each maps to any object or custom field on the other side. | |
| Products Catalog items attached to deals for line-level revenue data. | 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 Freshsales and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side. | |
| Contacts Person records carrying lifecycle stages; the main entity for two-way CRM syncs. | Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. | Contacts is specific to Freshsales and Users to Notion — each maps to any object or custom field on the other side. | |
| Accounts Company records kept aligned with billing, ERP, and warehouse tables. | Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. | Accounts is specific to Freshsales and Comments to Notion — each maps to any object or custom field on the other side. | |
| Deals Pipeline records synced to a warehouse for revenue 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. | Deals is specific to Freshsales and Files and attachments to Notion — each maps to any object or custom field on the other side. | |
| Tasks Rep to-dos created from external triggers or synced for productivity reporting. | Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. | Tasks is specific to Freshsales and Pages to Notion — each maps to any object or custom field on the other side. |
How changes propagate between Freshsales 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.
Freshsales Notion Sub-second propagation
DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.
DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.
Notion Freshsales 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 Freshsales through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
- 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 Freshsales ⇄ Notion
Connect Freshsales and Notion for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Freshsales–Notion connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Freshsales 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 Freshsales or Notion record.
Observability
Monitoring
Track your Freshsales ⇄ Notion sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Freshsales and Notion.
How the Freshsales and Notion connectors work
Freshsales
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by Freshworks plan
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 Freshsales 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 Freshsales 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.
Freshsales
connected
Notion
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Freshsales 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 · Freshsales ⇄ 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.
Freshsales NotionCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Freshsales and Notion integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Freshsales and Notion: authenticate both systems, choose the objects to sync (such as Freshsales's Sales activities and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Freshsales and Notion. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Freshsales: Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations. On Notion: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Notion side: Databases / Data sources, Properties, Blocks, Formula and Rollup properties, plus custom fields where Notion exposes them. On the Freshsales side: Tasks, Appointments, Notes, Sales activities. Stacksync auto-detects both schemas and converts types between the two systems.
-
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 Freshsales 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 Freshsales sync into Notion, so people working there have the context without switching tools.
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 527 integrations available for Freshsales and Notion.
Popular · 7 of 527
-
Freshsales ⇄ Slack -
Freshsales ⇄ BetterContact -
Freshsales ⇄ Agiloft -
Freshsales ⇄ Gainsight -
Notion ⇄ Copper CRM -
Notion ⇄ Creatio CRM -
Notion ⇄ Folk CRM
No integrations match .
