Two-way sync
Changes in Close or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Close 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. Close 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 Invoice, Credit Memo, Bill, Journal Entry in Rillet to Tasks, Custom Activities, Custom Fields, Users in Close 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 Close, so reps see overdue balances before they promise the next order.
When a contact or address is corrected in Close, Rillet gets the update before the next invoice goes out.
Finance sees the account owner and relationship history from Close 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.
| Close objects | Rillet objects | |
|---|---|---|
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Invoice Synced with incremental and full sync per the Stacksync docs. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Bill Synced with incremental and full sync per the Stacksync docs. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Charge Synced with incremental and full sync per the Stacksync docs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Rillet connection.
Changes in Close or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close 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 Close or Rillet record.
Track your Close ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close 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 Close 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 Close 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 Close and Rillet: authenticate both systems, choose the objects to sync (such as Close's Custom Activities and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. 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.
On the Rillet side: Invoice, Credit Memo, Bill, Journal Entry, plus custom fields where Rillet exposes them. On the Close side: Tasks, Custom Activities, Custom Fields, 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 Close and Rillet: Payment status on the account; Billing detail changes flow back; Collections with context. Invoice and payment status from Rillet appears on the account in Close, so reps see overdue balances before they promise the next order.
Close: REST API. Authentication: API key (sent via HTTP Basic auth). 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.
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 386 integrations available for Close and Rillet.