Two-way sync
Changes in Citus or Smartsheet instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Smartsheet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Smartsheet through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Citus.
Stacksync mirrors Columns, Cells, Reports, Attachments from Smartsheet into Schemas, Views, Sequences, Distributed tables in Citus and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Smartsheet, so the tool and the database never disagree.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Smartsheet are ordinary rows in Citus; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in Citus and Stacksync propagates the change into Smartsheet, replacing custom integration code.
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 | Smartsheet objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Discussions and Comments Threaded comments on rows and sheets; read out to sync collaboration history or activity into another system. | Schemas is specific to Citus and Discussions and Comments to Smartsheet — 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 and Groups Account membership and sharing; synced to keep an HR or identity source aligned with sheet and workspace access. | Views is specific to Citus and Users and Groups to Smartsheet — 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. | Sheets The core container; each sheet has typed columns, rows, and a modifiedAt stamp. Stacksync treats a sheet as a table and syncs its rows two-way. | Sequences is specific to Citus and Sheets to Smartsheet — 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. | Rows Records inside a sheet, each with createdAt/modifiedAt and cells keyed by columnId; the primary unit synced to and from external tables. | Distributed tables is specific to Citus and Rows to Smartsheet — 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. | Columns Define sheet schema and cell type (TEXT_NUMBER, DATE, CONTACT_LIST, PICKLIST, CHECKBOX); read via the API so field mappings can be generated. | Reference tables is specific to Citus and Columns to Smartsheet — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Cells Row-by-column values; writes must match the column type and no single cell can exceed 4,000 characters. | Local tables is specific to Citus and Cells to Smartsheet — each maps to any object or custom field on the other side. |
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.
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 Smartsheet through its API, with automatic retries and rate-limit backoff.
DetectionSmartsheet notifies Stacksync of record changes through webhook events. Sheet-scoped webhooks subscribed to *.* events notify on row and cell changes.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Smartsheet connection.
Changes in Citus or Smartsheet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Smartsheet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Citus or Smartsheet record.
Track your Citus ⇄ Smartsheet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Smartsheet.
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.
Authenticate Citus and Smartsheet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Citus and Smartsheet 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Smartsheet: authenticate both systems, choose the objects to sync (such as Citus's Schemas and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Smartsheet: Sheet-scoped webhooks subscribed to *.* events notify on row and cell changes; otherwise polling on sheet and row modifiedAt timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Smartsheet side: Columns, Cells, Reports, Attachments, plus custom fields where Smartsheet exposes them. On the Citus side: Schemas, Views, Sequences, Distributed tables. Stacksync auto-detects both schemas and converts types between the two systems.
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 Smartsheet: One integration pattern for the whole stack; Read Smartsheet with a query; Automate Smartsheet from your codebase. Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
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). Smartsheet: REST API (v2.0). Authentication: OAuth 2.0 authorization-code flow, or a raw/personal API access token passed as a Bearer header. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 437 integrations available for Citus and Smartsheet.