Two-way sync
Changes in Notion or Pigment instantly reflect in both systems. No stale data, no manual imports.
Keep Notion and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Pigment holds the financial truth: who the customers are, what they were billed, what they paid. Notion is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Metrics, Dimension lists, Tables, Scenarios in Pigment and Files and attachments, Pages, Databases / Data sources, Properties in Notion in sync, bi-directionally and in real time. Whatever records Notion keeps and whatever events it produces, the overlap with Pigment is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Front-line teams see invoice and payment status from Pigment next to the customer they are helping, without logging into the finance system.
Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.
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 | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Tables Row-based transactional data loaded into models from source systems | Files and attachments is specific to Notion and Tables to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Pages is specific to Notion and Scenarios to Pigment — 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. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Databases / Data sources is specific to Notion and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. | Users and permissions Access controls governing which model areas a sync can touch | Properties is specific to Notion and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. | Applications Planning models organized by domain such as finance, sales, or workforce | Blocks is specific to Notion and Applications to Pigment — 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. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Formula and Rollup properties is specific to Notion and Metrics to Pigment — 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 Pigment through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
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–Pigment connection.
Changes in Notion or Pigment instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Notion or Pigment 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 Pigment record.
Track your Notion ⇄ Pigment sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Notion and Pigment.
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 Pigment 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 Pigment 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 Pigment: authenticate both systems, choose the objects to sync (such as Notion's Files and attachments and Pages), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. Notion: Notion-hosted file URLs are temporary and expire after about an hour, so files must be re-fetched or copied during a sync. Stacksync's field mapping accounts for these differences between Notion and Pigment 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 Pigment records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Notion and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Notion–Pigment integration in-house.
Yes — Stacksync ships production-grade connectors for both Notion and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 416 integrations available for Notion and Pigment.