Real-time
Real-time sync
Changes in Citus or Lusha instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Business productivity
Citus to Lusha integration — real-time data sync
Keep Citus and Lusha 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 Lusha
Mirror Lusha's data into Citus so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Lusha is a read-only source: Stacksync reads its data in real time and delivers it into Citus, so Citus always reflects the current state of Lusha — without exports, scripts, or schedulers.
Engineers integrate with tools like Lusha 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 Company Profiles, Email Addresses, Phone Numbers, Prospecting Results from Lusha 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 Lusha, so the tool and the database never disagree.
Common use cases
- 01 Append firmographic company data to account records before territory or scoring runs.
- 02 Build prospecting lists from Lusha search results and sync them into the CRM as leads.
- 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
Automate Lusha from your codebase
Write to the synced tables in Citus and Stacksync propagates the change into Lusha, replacing custom integration code.
React to changes as they happen
Updates in Lusha 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 Lusha
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 | Lusha objects | How this pairing syncs | |
|---|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. | Views is specific to Citus and Bulk Enrichment Requests to Lusha — 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. | Person Profiles Contact-level enrichment results (work emails, phone numbers, title, company) returned per lookup. | Sequences is specific to Citus and Person Profiles to Lusha — 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. | Company Profiles Firmographic records (industry, size, location) appended to account or company rows. | Distributed tables is specific to Citus and Company Profiles to Lusha — 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. | Email Addresses Work emails written into CRM contact fields during enrichment. | Reference tables is specific to Citus and Email Addresses to Lusha — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. | Local tables is specific to Citus and Phone Numbers to Lusha — 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. | Prospecting Results Search-based lists of people and companies matching filters, used to seed lead lists. | Schemas is specific to Citus and Prospecting Results to Lusha — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Lusha
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 Lusha 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.
DeliveryLusha does not accept inbound record writes, so this direction carries requests rather than records: Lusha's output flows back as field updates on the originating Citus records.
Lusha Citus Interval-based propagation
DetectionStacksync polls Lusha for changes on an incremental schedule, reading only records changed since the previous pass. Data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Lusha: Lookups consume credits and are subject to the platform's API rate limits.
What ships with Citus ⇄ Lusha
Connect Citus and Lusha for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Lusha connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Lusha 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 Lusha record.
Observability
Monitoring
Track your Citus ⇄ Lusha 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 Lusha.
How the Citus and Lusha 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
Lusha
- Integration surface
- REST API
- Authentication
- API key
- Change detection
- Not event-driven; data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change
- Capabilities
- read
- Rate limits
- Lookups consume credits and are subject to the platform's API rate limits.
How it works
How to connect Citus to Lusha — 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 Lusha 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
Lusha
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Lusha 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 ⇄ LushaCustomers 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 LushaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Lusha integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Citus and Lusha — Lusha is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Lusha connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Lusha integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Lusha. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 Lusha: Not event-driven; data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Lusha side: Company Profiles, Email Addresses, Phone Numbers, Prospecting Results, plus custom fields where Lusha 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.
-
Lusha is a read-only source, so this integration runs one-way: Stacksync reads from Lusha in real time and delivers into Citus. Field mapping and monitoring work the same as for two-way pairs.
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 303 integrations available for Citus and Lusha.
Popular · 4 of 303
No integrations match .
