Skip to content
CRM ⇄ Accounting and finance

Kustomer to Rillet integration — real-time, two-way sync

Keep Kustomer 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Kustomer and Rillet

Sync customers, invoices, and payment status between Rillet and Kustomer in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Kustomer 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 Companies, Custom Objects (Klasses), Users, Teams in Kustomer 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.

Common use cases

  • 01 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
  • 02 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • 03 Keep customer attributes updated from billing systems so routing rules and SLAs reflect account value
  • 04 Escalate conversation-derived signals into the CRM as tasks or opportunities

Common sync patterns

Collections with context

Finance sees the account owner and relationship history from Kustomer when chasing a balance, and sales sees that the chase is happening.

Where Kustomer tracks deals: closed-won creates the finance record

A won opportunity creates or updates the customer in Rillet with the right billing details, so invoicing starts without re-keying.

Payment status on the account

Invoice and payment status from Rillet appears on the account in Kustomer, so reps see overdue balances before they promise the next order.

What you can sync between Kustomer and Rillet

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.

Kustomer objects Rillet objects How this pairing syncs
Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. Customer 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.
Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. Custom Field Synced with incremental and full sync per the Stacksync docs. Custom Objects (Klasses) is specific to Kustomer and Custom Field to Rillet — each maps to any object or custom field on the other side.
Users Agent records map conversation ownership to people in other systems. Account Synced with incremental and full sync per the Stacksync docs. Users is specific to Kustomer and Account to Rillet — each maps to any object or custom field on the other side.
Teams Team assignments support routing parity and reporting. Vendor Synced with incremental and full sync per the Stacksync docs. Teams is specific to Kustomer and Vendor to Rillet — each maps to any object or custom field on the other side.
Tags Labels on conversations and customers sync for categorization and analytics. Invoice Synced with incremental and full sync per the Stacksync docs. Tags is specific to Kustomer and Invoice to Rillet — each maps to any object or custom field on the other side.
Notes Internal annotations carry context alongside synced conversations. Credit Memo Synced with incremental and full sync per the Stacksync docs. Notes is specific to Kustomer and Credit Memo to Rillet — each maps to any object or custom field on the other side.

How changes propagate between Kustomer and Rillet

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.

Kustomer Rillet Sub-second propagation

DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.

DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.

Rillet Kustomer Sub-second propagation

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 Kustomer through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Kustomer: Subject to the platform's API rate limits.
  • Rillet: Subject to the platform's API rate limits.
What ships with Kustomer ⇄ Rillet

Connect Kustomer and Rillet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kustomer–Rillet connection.

Real-time

Two-way sync

Changes in Kustomer or Rillet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kustomer or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Kustomer or Rillet record.

Observability

Monitoring

Track your Kustomer ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Kustomer and Rillet.

How the Kustomer and Rillet connectors work

Kustomer

Integration surface
REST API
Authentication
API key used as a bearer token, scoped by role
Change detection
Outbound webhooks on record events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits

Rillet

Integration surface
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
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect Kustomer to Rillet — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Kustomer 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Kustomer connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kustomer 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Kustomer ⇄ Rillet
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Kustomer Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kustomer and Rillet integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 339 integrations available for Kustomer and Rillet.

Popular · 7 of 339
All Kustomer integrations All Rillet integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own