Real-time
Two-way sync
Changes in Citus or Full Enrich instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Business productivity
Citus to Full Enrich integration — real-time, two-way sync
Keep Citus and Full Enrich 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 Full Enrich
Mirror Full Enrich's data into Citus so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Engineers integrate with tools like Full Enrich 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 Contacts, Enrichment results, Emails, Phone numbers from Full Enrich into Local tables, Schemas, Views, Sequences 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 Full Enrich, so the tool and the database never disagree.
Common use cases
- Run waterfall enrichment over warehouse lead lists before importing them into outbound sequencers.
- Backfill missing phone numbers on aging CRM records on a schedule.
- Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
Automate Full Enrich from your codebase
Write to the synced tables in Citus and Stacksync propagates the change into Full Enrich, replacing custom integration code.
React to changes as they happen
Updates in Full Enrich arrive as row changes in Citus, so triggers, jobs, and services can respond in near real time.
One integration pattern for the whole stack
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
What you can sync between Citus and Full Enrich
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 | Full Enrich objects | |
|---|---|---|
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Emails Returned addresses with verification status, written back to the CRM or database. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Credits Account balance consumed on successful finds; monitored to pace sync jobs. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Contacts The person inputs (name plus company or domain) sent for enrichment. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Enrichment results Completed records fetched by request ID or delivered via webhook. |
What ships with Citus ⇄ Full Enrich
Connect Citus and Full Enrich for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Full Enrich connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Full Enrich 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 Full Enrich record.
Observability
Monitoring
Track your Citus ⇄ Full Enrich 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 Full Enrich.
How the Citus and Full Enrich 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
Full Enrich
- Integration surface
- REST API with asynchronous bulk enrichment endpoints
- Authentication
- API key (Bearer token)
- Change detection
- Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits and per-batch size constraints
How it works
How to connect Citus to Full Enrich — 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 Full Enrich 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
Full Enrich
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Full Enrich 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 ⇄ Full EnrichCustomers 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 Full EnrichCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Full Enrich integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Full Enrich: authenticate both systems, choose the objects to sync (such as Citus's Distributed tables and Reference 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 Full Enrich: Automate Full Enrich from your codebase; React to changes as they happen; One integration pattern for the whole stack. Write to the synced tables in Citus and Stacksync propagates the change into Full Enrich, replacing custom integration code.
-
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). Full Enrich: REST API with asynchronous bulk enrichment endpoints. Authentication: API key (Bearer token). Stacksync manages authentication, retries, and rate limits on both sides.
-
Full Enrich: Enrichment is asynchronous: batches are submitted, run through a waterfall of upstream data providers, and results arrive by webhook or a later fetch, so syncs must handle pending states. 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 Full Enrich 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 Full Enrich records are not retained after a sync operation.
SECURITY
Security teams love 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 386 integrations available for Citus and Full Enrich.
Popular · 8 of 386
-
Citus ⇄ Braze -
Citus ⇄ ConnectWise -
Citus ⇄ Aviato -
Citus ⇄ Customer.io -
Full Enrich ⇄ PostgreSQL -
Full Enrich ⇄ Amazon RDS -
Full Enrich ⇄ Supabase -
Full Enrich ⇄ MySQL
No integrations match .
