Real-time
Two-way sync
Changes in Citus or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
Citus to Twenty CRM integration — real-time, two-way sync
Keep Citus and Twenty CRM 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 Twenty CRM
Treat Twenty CRM 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 Notes, Custom Objects, Attachments, Workspace Members from Twenty CRM into Views, Sequences, Distributed tables, Reference tables in Citus with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Twenty CRM 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 support tickets or tasks between Twenty and an operations tool.
- 02 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 03 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 04 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
Common sync patterns
Trigger workflows from CRM changes
Field and stage updates in Twenty CRM arrive as row changes in Citus, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Twenty CRM 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 Twenty CRM, giving go-to-market teams live product context.
What you can sync between Citus and Twenty CRM
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 | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| Sequences Key generators that matter when external writes must not collide with application inserts. | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | Sequences is specific to Citus and Notes to Twenty CRM — 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. | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | Distributed tables is specific to Citus and Custom Objects to Twenty CRM — 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. | Attachments Files linked to records. | Reference tables is specific to Citus and Attachments to Twenty CRM — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Workspace Members User accounts used for record ownership and assignment mapping. | Local tables is specific to Citus and Workspace Members to Twenty CRM — 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. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Schemas is specific to Citus and People to Twenty CRM — 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. | Companies Account-level records that group people and opportunities. | Views is specific to Citus and Companies to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Twenty CRM
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 Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Citus Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Citus ⇄ Twenty CRM
Connect Citus and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Citus ⇄ Twenty CRM 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 Twenty CRM.
How the Citus and Twenty CRM 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
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Citus to Twenty CRM — 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 Twenty CRM 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
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Twenty CRM 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 ⇄ Twenty CRMCustomers 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 Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Twenty CRM: 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.
-
Common patterns for Citus and Twenty CRM: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Twenty CRM 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). Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
-
Twenty CRM: Both GraphQL and REST APIs are generated from the workspace's object schema, so custom objects get the same API surface as standard ones. 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 Twenty CRM 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 Twenty CRM records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Twenty CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Twenty CRM integration in-house.
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 363 integrations available for Citus and Twenty CRM.
Popular · 4 of 363
No integrations match .
