Two-way sync
Changes in Rillet or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Keep Rillet and Snowflake in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.
Stacksync syncs Bill, Journal Entry, Invoice Payment, Charge from Rillet into tables in Snowflake in real time, and the connection works in both directions: values computed in Snowflake can be written back to fields in Rillet where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.
Invoices, payments, and customer records from Rillet arrive in Snowflake as queryable tables, current within seconds instead of a day behind.
Analysts combine Rillet's financial records with product, marketing, or operational data already in Snowflake for reporting the finance system cannot do alone.
Scores or segments computed in Snowflake, like payment-risk flags or customer tiers, sync back onto records in Rillet where the finance team can act on them.
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.
| Rillet objects | Snowflake objects | How this pairing syncs | |
|---|---|---|---|
| Invoice Synced with incremental and full sync per the Stacksync docs. | Streams Row-level change records on a table, consumed to process deltas instead of full scans. | Invoice is specific to Rillet and Streams to Snowflake — each maps to any object or custom field on the other side. | |
| Credit Memo Synced with incremental and full sync per the Stacksync docs. | Stages File staging areas used for bulk loads into synced tables. | Credit Memo is specific to Rillet and Stages to Snowflake — each maps to any object or custom field on the other side. | |
| Bill Synced with incremental and full sync per the Stacksync docs. | Tasks Scheduled SQL used to transform synced data after it lands. | Bill is specific to Rillet and Tasks to Snowflake — each maps to any object or custom field on the other side. | |
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | VARIANT Columns Semi-structured JSON payloads stored alongside relational columns. | Journal Entry is specific to Rillet and VARIANT Columns to Snowflake — each maps to any object or custom field on the other side. | |
| Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Virtual Warehouses The compute a sync's queries run on, sized independently of storage. | Invoice Payment is specific to Rillet and Virtual Warehouses to Snowflake — each maps to any object or custom field on the other side. | |
| Charge Synced with incremental and full sync per the Stacksync docs. | Databases Top-level containers that scope which data a sync can touch. | Charge is specific to Rillet and Databases to Snowflake — 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.
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is applied to Snowflake as a row-level write, with types converted between the two schemas.
DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–Snowflake connection.
Changes in Rillet or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rillet or Snowflake data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Rillet or Snowflake record.
Track your Rillet ⇄ Snowflake sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rillet and Snowflake.
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 Rillet and Snowflake 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 Rillet and Snowflake 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 Rillet and Snowflake: authenticate both systems, choose the objects to sync (such as Rillet's Invoice and Credit Memo), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Rillet side: Bill, Journal Entry, Invoice Payment, Charge, plus custom fields where Rillet exposes them. On the Snowflake side: Schemas, Tables, Views, Materialized Views. 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 Rillet and Snowflake: Finance analytics without ETL; Revenue joined with everything else; Write-back of computed fields. Invoices, payments, and customer records from Rillet arrive in Snowflake as queryable tables, current within seconds instead of a day behind.
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. Snowflake: SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API. Authentication: Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Snowflake: External tables are not supported. Stacksync's field mapping accounts for these differences between Rillet and Snowflake 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 468 integrations available for Rillet and Snowflake.