Two-way sync
Changes in Notion or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Notion and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Rillet 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 Invoice Payment, Charge, Reimbursement, Custom Field in Rillet and Properties, Blocks, Formula and Rollup properties, Users in Notion in sync, bi-directionally and in real time. Whatever records Notion keeps and whatever events it produces, the overlap with Rillet 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.
Payment and charge activity flows into Rillet 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.
Figures teams rely on, like customer status or outstanding balances, stay current wherever Notion surfaces them instead of going stale after a one-time paste.
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 | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Properties is specific to Notion and Invoice Payment to Rillet — 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. | Charge Synced with incremental and full sync per the Stacksync docs. | Blocks is specific to Notion and Charge to Rillet — 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. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Formula and Rollup properties is specific to Notion and Reimbursement to Rillet — 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. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Users is specific to Notion and Custom Field to Rillet — 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. | Account Synced with incremental and full sync per the Stacksync docs. | Comments is specific to Notion and Account to Rillet — 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. | Customer Synced with incremental and full sync per the Stacksync docs. | Files and attachments is specific to Notion and Customer to Rillet — 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 Rillet through its API, with automatic retries and rate-limit backoff.
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
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–Rillet connection.
Changes in Notion or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Notion or Rillet 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 Rillet record.
Track your Notion ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Notion and Rillet.
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 Rillet 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 Rillet 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 Rillet: authenticate both systems, choose the objects to sync (such as Notion's Properties and Blocks), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Rillet side: Invoice Payment, Charge, Reimbursement, Custom Field, plus custom fields where Rillet exposes them. On the Notion side: Properties, Blocks, Formula and Rollup properties, Users. 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 Notion and Rillet: Where Notion collects payments or triggers charges: events land in Rillet; Where Notion tracks people or companies: one identity; Where Notion is a docs or knowledge workspace: reference data kept fresh. Payment and charge activity flows into Rillet as it happens, so the books reflect reality without manual reconciliation.
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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: Only 17 documented objects are supported. 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. Stacksync's field mapping accounts for these differences between Notion and Rillet without custom code.
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 432 integrations available for Notion and Rillet.