Real-time
Two-way sync
Changes in Citus or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
Citus to Kustomer integration — real-time, two-way sync
Keep Citus and Kustomer 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 Kustomer
Treat Kustomer 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 Conversations, Messages, Companies, Custom Objects (Klasses) from Kustomer into Distributed tables, Reference tables, Local tables, Schemas in Citus with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kustomer 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
- Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- Mirror conversations and satisfaction data into a warehouse for support analytics and agent performance reporting
- Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
Product events onto CRM records
Signup, usage, or lifecycle changes written to Citus sync onto the matching records in Kustomer, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Kustomer API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Kustomer arrive as row changes in Citus, ready to drive jobs and notifications.
What you can sync between Citus and Kustomer
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 | Kustomer objects | |
|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Notes Internal annotations carry context alongside synced conversations. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Conversations Support threads across channels sync outward for analytics and CRM context. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Messages Individual messages within conversations support full-thread replication. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Companies Organization records group customers and map to CRM accounts. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. |
What ships with Citus ⇄ Kustomer
Connect Citus and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Citus ⇄ Kustomer 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 Kustomer.
How the Citus and Kustomer 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
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
How it works
How to connect Citus to Kustomer — 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 Kustomer 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
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Kustomer 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 ⇄ KustomerCustomers 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 KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Kustomer: authenticate both systems, choose the objects to sync (such as Citus's Views and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. 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 Kustomer 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 Kustomer records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Kustomer integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Kustomer. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams love 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
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Citus and Kustomer.
Popular · 8 of 386
-
Citus ⇄ Freshsales -
Citus ⇄ Freshworks CRM -
Citus ⇄ Gladly -
Citus ⇄ Gorgias -
Kustomer ⇄ InfluxDB -
Kustomer ⇄ InterSystems IRIS -
Kustomer ⇄ MarkLogic -
Kustomer ⇄ Neo4j
No integrations match .
