Two-way sync
Changes in Folk CRM or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Folk CRM 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.
Finance and sales describe the same customers in different systems. Folk CRM knows the relationship: who the contacts are and what is in motion with the account. Rillet knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Credit Memo, Bill, Journal Entry, Invoice Payment in Rillet to Custom fields, Notes, Reminders, People in Folk CRM with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Invoice and payment status from Rillet appears on the account in Folk CRM, so reps see overdue balances before they promise the next order.
When a contact or address is corrected in Folk CRM, Rillet gets the update before the next invoice goes out.
Finance sees the account owner and relationship history from Folk CRM when chasing a balance, and sales sees that the chase is happening.
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.
| Folk CRM objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Companies Organization records linked to people and kept aligned with billing or CS systems. | Charge Synced with incremental and full sync per the Stacksync docs. | Companies is specific to Folk CRM and Charge to Rillet — each maps to any object or custom field on the other side. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Groups is specific to Folk CRM and Reimbursement to Rillet — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | Account Synced with incremental and full sync per the Stacksync docs. | Notes is specific to Folk CRM and Account to Rillet — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | Customer Synced with incremental and full sync per the Stacksync docs. | Reminders is specific to Folk CRM and Customer to Rillet — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | Vendor Synced with incremental and full sync per the Stacksync docs. | People is specific to Folk CRM and Vendor 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.
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Rillet connection.
Changes in Folk CRM or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Rillet record.
Track your Folk CRM ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Folk CRM 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 Folk CRM 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 Folk CRM 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 Folk CRM and Rillet: authenticate both systems, choose the objects to sync (such as Folk CRM's Custom fields and Companies), map fields visually, and changes propagate both ways in milliseconds — no code required.
Rillet: Rillet is built for SaaS companies, with a general ledger organized around automated revenue recognition and month-end close. Folk CRM: Folk's model centers on people and companies organized into shared groups rather than pipeline-first objects, so group membership carries much of the workflow state. Stacksync's field mapping accounts for these differences between Folk CRM and Rillet 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 Folk CRM and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Folk CRM and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Folk CRM–Rillet integration in-house.
Yes — Stacksync ships production-grade connectors for both Folk CRM and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. On Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 339 integrations available for Folk CRM and Rillet.