Real-time
Two-way sync
Changes in Citus or Seismic instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
Citus to Seismic integration — real-time, two-way sync
Keep Citus and Seismic 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 Seismic
Treat Seismic 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 Reporting Activities, Library Content, Content Versions, Users from Seismic 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 Seismic 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 React to ContentManager and DSR webhook events to update a database when documents are published, versioned, or expired.
- 02 Provision and deactivate Seismic Users and User Groups from an HRIS or IdP so content access mirrors joiner, mover, and leaver changes.
- 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
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Seismic API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Seismic arrive as row changes in Citus, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Seismic become tables in Citus you can join with application data directly.
What you can sync between Citus and Seismic
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 | Seismic objects | How this pairing syncs | |
|---|---|---|---|
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Content Versions Version history for a library item; new versions upload via API and old ones expire, with events firing on ContentManager webhooks. | Reference tables is specific to Citus and Content Versions to Seismic — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Users User records managed through SCIM 2.0 and legacy user endpoints; created, updated, and deactivated for provisioning sync. | Local tables is specific to Citus and Users to Seismic — 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. | User Groups Group definitions and membership that govern content access; synced from an IdP or HRIS to keep permissions current. | Schemas is specific to Citus and User Groups to Seismic — 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. | Teamsites Tenant-scoped workspace partitions organizing Library content, permissions, and config; scoped by teamSiteId on most content calls. | Views is specific to Citus and Teamsites to Seismic — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | LiveSend Links Trackable content-share links created via the engagement API; their open and view engagement is read back through Reporting. | Sequences is specific to Citus and LiveSend Links to Seismic — 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. | Digital Sales Rooms Buyer-facing microsites (DSRs); lifecycle and content-change events surface via webhooks, currently marked Early Access. | Distributed tables is specific to Citus and Digital Sales Rooms to Seismic — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Seismic
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 Seismic 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 Seismic through its API, with automatic retries and rate-limit backoff.
Seismic Citus Sub-second propagation
DetectionSeismic notifies Stacksync of record changes through webhook events. Webhooks for content, version, user, group, workflow, DSR, and LiveSend events.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Seismic: Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers.
What ships with Citus ⇄ Seismic
Connect Citus and Seismic for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Seismic connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Seismic 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 Seismic record.
Observability
Monitoring
Track your Citus ⇄ Seismic 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 Seismic.
How the Citus and Seismic 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
Seismic
- Integration surface
- REST Integration APIs and Reporting API v2
- Authentication
- OAuth 2.0 / OpenID Connect; Bearer token in the Authorization header, via Authorization Code (user context) or client-credentials app-only flows
- Change detection
- Webhooks for content, version, user, group, workflow, DSR, and LiveSend events; the Reporting API v2 is polled for batch historical extracts (ETL-oriented, not high-frequency)
- Capabilities
- read · write · webhooks
- Rate limits
- Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers
How it works
How to connect Citus to Seismic — 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 Seismic 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
Seismic
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Seismic 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 ⇄ SeismicCustomers 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 SeismicCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Seismic integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Seismic: authenticate both systems, choose the objects to sync (such as Citus's Reference tables and Local 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 Seismic: Internal tools without API code; Trigger workflows from CRM changes; Query the CRM like a database. Back-office apps read and write the synced tables; Stacksync handles the Seismic API, limits, and retries.
-
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). Seismic: REST Integration APIs and Reporting API v2. Authentication: OAuth 2.0 / OpenID Connect; Bearer token in the Authorization header, via Authorization Code (user context) or client-credentials app-only flows. Stacksync manages authentication, retries, and rate limits on both sides.
-
Seismic: Webhook events are tenant-scoped and can be filtered by attributes like contentId, teamSiteId, tenantId, and format using JSONPath or regex expressions. Citus: Because shard data lives on worker nodes, log-based CDC is more involved than on single-node Postgres and depends on the Citus version and hosting (including the Azure managed service). Stacksync's field mapping accounts for these differences between Citus and Seismic 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 Seismic 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
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 455 integrations available for Citus and Seismic.
Popular · 5 of 455
No integrations match .
