Skip to content
CRM ⇄ Accounting and finance

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

Keep Kommo 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 Kommo and Rillet

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

Finance and sales describe the same customers in different systems. Kommo 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 Leads, Contacts, Companies, Pipelines & Statuses in Kommo 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 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • 04 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards

Common sync patterns

Billing detail changes flow back

When a contact or address is corrected in Kommo, Rillet gets the update before the next invoice goes out.

Collections with context

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

Where Kommo 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.

What you can sync between Kommo 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.

Kommo objects Rillet objects How this pairing syncs
Custom Fields Per-entity custom fields hold data written from external databases and enrichment. 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. Custom fields on either side are included in the mapping.
Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Customer Synced with incremental and full sync per the Stacksync docs. Chats is specific to Kommo and Customer to Rillet — each maps to any object or custom field on the other side.
Leads The central pipeline record; external signups and form fills sync in as leads. Vendor Synced with incremental and full sync per the Stacksync docs. Leads is specific to Kommo and Vendor to Rillet — each maps to any object or custom field on the other side.
Contacts Person records sync with other CRMs and databases for a shared contact file. Invoice Synced with incremental and full sync per the Stacksync docs. Contacts is specific to Kommo and Invoice to Rillet — each maps to any object or custom field on the other side.
Companies Organization records map to accounts in ERPs and invoicing tools. Credit Memo Synced with incremental and full sync per the Stacksync docs. Companies is specific to Kommo and Credit Memo to Rillet — each maps to any object or custom field on the other side.
Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. Bill Synced with incremental and full sync per the Stacksync docs. Pipelines & Statuses is specific to Kommo and Bill to Rillet — each maps to any object or custom field on the other side.

How changes propagate between Kommo 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.

Kommo Rillet Sub-second propagation

DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.

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

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

Rate-limit considerations

  • Kommo: Subject to per-account request rate limits.
  • Rillet: Subject to the platform's API rate limits.
What ships with Kommo ⇄ Rillet

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kommo 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 Kommo or Rillet record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Kommo and Rillet connectors work

Kommo

Integration surface
REST API
Authentication
OAuth 2.0 with refresh tokens
Change detection
Webhooks on record add and update events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-account request 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 Kommo 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 Kommo 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
    Kommo connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kommo 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 · Kommo ⇄ 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
    Kommo Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kommo 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 439 integrations available for Kommo and Rillet.

Popular · 7 of 439
All Kommo 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