Real-time
Two-way sync
Changes in Citus or Kommo instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
Citus to Kommo integration — real-time, two-way sync
Keep Citus and Kommo 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 Citus and Kommo
Treat Kommo like part of your database: its records live in Citus as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Citus, where it can be queried and joined like everything else.
Stacksync mirrors Leads, Contacts, Companies, Pipelines & Statuses from Kommo into Sequences, Distributed tables, Reference tables, Local tables in Citus with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kommo with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Common use cases
- 01 Mirror pipeline stage changes into BI tools for forecasting
- 02 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
- 03 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- 04 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
Common sync patterns
Trigger workflows from CRM changes
Field and stage updates in Kommo arrive as row changes in Citus, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Kommo become tables in Citus you can join with application data directly.
Product events onto CRM records
Signup, usage, or lifecycle changes written to Citus sync onto the matching records in Kommo, giving go-to-market teams live product context.
What you can sync between Citus and Kommo
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.
| Citus objects | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Sequences Key generators that matter when external writes must not collide with application inserts. | Companies Organization records map to accounts in ERPs and invoicing tools. | Sequences is specific to Citus and Companies to Kommo — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Distributed tables is specific to Citus and Pipelines & Statuses to Kommo — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Tasks Follow-up records keep rep activity consistent across systems. | Reference tables is specific to Citus and Tasks to Kommo — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Notes Free-text and system notes attach context to synced leads and contacts. | Local tables is specific to Citus and Notes to Kommo — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | Schemas is specific to Citus and Custom Fields to Kommo — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Users Account users map lead ownership to people in other systems. | Views is specific to Citus and Users to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Kommo
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.
Citus Kommo Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Citus 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 applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Kommo: Subject to per-account request rate limits.
What ships with Citus ⇄ Kommo
Connect Citus and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Kommo 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 Citus or Kommo record.
Observability
Monitoring
Track your Citus ⇄ Kommo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Kommo.
How the Citus and Kommo connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
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
How it works
How to connect Citus to Kommo — 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.
- 01
Connect your apps
Authenticate Citus and Kommo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Kommo 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.
objects · Citus ⇄ KommoCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Kommo: authenticate both systems, choose the objects to sync (such as Citus's Sequences and Distributed tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Citus and Kommo: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Kommo arrive as row changes in Citus, ready to drive jobs and notifications.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: The API uses OAuth 2.0 with short-lived access tokens refreshed via refresh tokens, and supports webhooks on record lifecycle events. Citus: Distributed tables are sharded by a declared distribution column, and reference tables are fully replicated to all nodes; the table type changes how writes and joins behave. Stacksync's field mapping accounts for these differences between Citus and Kommo 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 Citus and Kommo records are not retained after a sync operation.
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 444 integrations available for Citus and Kommo.
Popular · 5 of 444
No integrations match .
