Real-time
Real-time sync
Changes in DuckDB or Lusha instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Business productivity
DuckDB to Lusha integration — real-time data sync
Keep DuckDB 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 DuckDB and Lusha
Mirror Lusha's data into DuckDB 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 DuckDB, so DuckDB 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 DuckDB.
Stacksync mirrors Email Addresses, Phone Numbers, Prospecting Results, Bulk Enrichment Requests from Lusha into Attached databases, Database files, Schemas, Tables in DuckDB 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
- Re-verify stale contact data on a schedule and flag records that no longer resolve.
- Enrich new CRM leads with work emails and direct dials the moment they are created.
- Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
- Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
Automate Lusha from your codebase
Write to the synced tables in DuckDB 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 DuckDB, 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 DuckDB 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.
| DuckDB objects | Lusha objects | |
|---|---|---|
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Company Profiles Firmographic records (industry, size, location) appended to account or company rows. | |
| Views SQL views used to shape or filter data for downstream consumers. | Email Addresses Work emails written into CRM contact fields during enrichment. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Prospecting Results Search-based lists of people and companies matching filters, used to seed lead lists. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Person Profiles Contact-level enrichment results (work emails, phone numbers, title, company) returned per lookup. |
What ships with DuckDB ⇄ Lusha
Connect DuckDB and Lusha for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Lusha connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB 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 DuckDB or Lusha record.
Observability
Monitoring
Track your DuckDB ⇄ Lusha sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Lusha.
How the DuckDB and Lusha connectors work
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
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 DuckDB 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 DuckDB 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.
DuckDB
connected
Lusha
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB 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 · DuckDB ⇄ 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.
DuckDB LushaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Lusha integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between DuckDB 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.
-
Lusha: Lusha is a lookup-style enrichment API, not a system of record: integrations send an identifier (such as email, LinkedIn URL, or name plus company) and receive matched contact data back. DuckDB: It queries Parquet, CSV, and JSON files directly without importing them, which makes file-based exchange a natural sync pattern. Stacksync's field mapping accounts for these differences between DuckDB and Lusha 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 DuckDB and Lusha records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Lusha connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Lusha integration in-house.
-
Yes — Stacksync ships production-grade connectors for both DuckDB and Lusha. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. 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.
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 DuckDB and Lusha.
Popular · 8 of 386
- DuckDB ⇄ ServiceNow
-
DuckDB ⇄ Slack -
DuckDB ⇄ Zendesk -
DuckDB ⇄ Campfire -
Lusha ⇄ Apache Cassandra -
Lusha ⇄ Azure Cosmos DB -
Lusha ⇄ Azure SQL Database -
Lusha ⇄ Citus
No integrations match .
