Real-time
Two-way sync
Changes in Airtable or Citus instantly reflect in both systems. No stale data, no manual imports.
Database
Airtable to Citus integration — real-time, two-way sync
Keep Airtable and Citus 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 Airtable and Citus
Keep Airtable and Citus synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Airtable and Citus continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- 01 Sync form-submitted records from Airtable into downstream systems like a helpdesk or marketing platform.
- 02 Push CRM accounts and deals into an Airtable base so operations teams can manage pipelines and enrichment without CRM licenses.
- 03 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- 04 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
Common sync patterns
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Cross-engine sync
Keep the same dataset live in both Airtable and Citus, so each workload runs on the engine that suits it.
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
What you can sync between Airtable and Citus
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.
| Airtable objects | Citus objects | How this pairing syncs | |
|---|---|---|---|
| Views Filtered subsets of a table that can scope which records a sync reads. | Views Curated projections over distributed data, often used as read-only sync sources. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables Map to sync tables; schema is readable through the base metadata endpoints. | Sequences Key generators that matter when external writes must not collide with application inserts. | Tables is specific to Airtable and Sequences to Citus — each maps to any object or custom field on the other side. | |
| Records The row-level unit created, updated, and deleted during syncs, identified by rec-prefixed IDs. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Records is specific to Airtable and Distributed tables to Citus — each maps to any object or custom field on the other side. | |
| Fields Typed columns including linked records, lookups, and rollups; computed fields are read-only in syncs. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Fields is specific to Airtable and Reference tables to Citus — each maps to any object or custom field on the other side. | |
| Linked records Cross-table references that carry relationships between synced tables. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Linked records is specific to Airtable and Local tables to Citus — each maps to any object or custom field on the other side. | |
| Attachments File fields exposed as expiring URLs that syncs can mirror to other systems. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Attachments is specific to Airtable and Schemas to Citus — each maps to any object or custom field on the other side. |
How changes propagate between Airtable and Citus
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.
Airtable Citus Sub-second propagation
DetectionAirtable pushes changes as they happen — webhook events backed by change data capture. Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks).
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Citus Airtable 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 Airtable through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Airtable: The Web API enforces a per-base limit of 5 requests per second.
What ships with Airtable ⇄ Citus
Connect Airtable and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Airtable–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Airtable or Citus 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 Airtable or Citus record.
Observability
Monitoring
Track your Airtable ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Airtable and Citus.
How the Airtable and Citus connectors work
Airtable
- Integration surface
- REST API (per-base Web API plus metadata and webhooks endpoints)
- Authentication
- OAuth (Airtable OAuth grant to specific bases or all resources); the authorizing user must have a `creator` role, since only creator roles can create webhooks
- Change detection
- Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks); formula fields don't emit change events and are re-synced every hour
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- The Web API enforces a per-base limit of 5 requests per second.
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
How it works
How to connect Airtable to Citus — 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 Airtable and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Airtable
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Airtable and Citus 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 · Airtable ⇄ CitusCustomers 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.
Airtable CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Airtable and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Airtable and Citus: authenticate both systems, choose the objects to sync (such as Airtable's Views and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Airtable and Citus connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Airtable–Citus integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Airtable and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Airtable: Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks); formula fields don't emit change events and are re-synced every hour. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Airtable side: Attachments, Collaborators, Bases, Tables, plus custom fields where Airtable exposes them. On the Citus side: Reference tables, Local tables, Schemas, Views. 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.
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 467 integrations available for Airtable and Citus.
Popular · 4 of 467
No integrations match .
