Two-way sync
Changes in Citus or Google Sheets instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Google Sheets 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 Google Sheets 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 Spreadsheets, Sheets (tabs), Rows, Ranges from Google Sheets into Distributed tables, Reference tables, Local tables, Schemas 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 Google Sheets, 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 Google Sheets 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 Google Sheets, 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 | Google Sheets objects | |
|---|---|---|
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Spreadsheets The file-level container a sync connects to, identified by spreadsheet ID. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Sheets (tabs) Individual worksheets, typically mapped one-to-one to a synced table. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Rows Treated as records; a header row usually defines field names. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Ranges Addressed in A1 notation for batched reads and writes. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Named ranges Stable references that keep sync mappings valid when the grid moves. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Cell values Untyped by default, so syncs handle type coercion for dates and numbers. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Google Sheets connection.
Changes in Citus or Google Sheets instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Google Sheets 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 Google Sheets record.
Track your Citus ⇄ Google Sheets sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Google Sheets.
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 Google Sheets 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 Google Sheets 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 Google Sheets: 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.
On the Google Sheets side: Spreadsheets, Sheets (tabs), Rows, Ranges, plus custom fields where Google Sheets exposes them. On the Citus side: Distributed tables, Reference tables, Local tables, Schemas. 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 Google Sheets: One integration pattern for the whole stack; Read Google Sheets with a query; Automate Google Sheets 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). Google Sheets: REST API (Google Sheets API), with file-level change signals available through the Drive API. Authentication: OAuth 2.0 (user consent) or Google service accounts. Stacksync manages authentication, retries, and rate limits on both sides.
Google Sheets: Cells are untyped, so a reliable sync must normalize dates, numbers, and empty cells rather than trusting cell formatting. Citus: Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards. Stacksync's field mapping accounts for these differences between Citus and Google Sheets without custom code.
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 386 integrations available for Citus and Google Sheets.