Real-time
Real-time sync
Changes in Lusha or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Lusha to Twenty CRM integration — real-time data sync
Keep Lusha and Twenty CRM 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 Lusha and Twenty CRM
Flow Lusha data into Twenty CRM in real time — no exports, no schedulers, no custom scripts.
Lusha is a read-only source: Stacksync reads its data in real time and delivers it into Twenty CRM, so Twenty CRM always reflects the current state of Lusha — without exports, scripts, or schedulers.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Lusha holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Common use cases
- 01 Build prospecting lists from Lusha search results and sync them into the CRM as leads.
- 02 Re-verify stale contact data on a schedule and flag records that no longer resolve.
- 03 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 04 Two-way sync of People and Companies between Twenty and a production Postgres database so engineers can query CRM data with SQL.
Common sync patterns
Where Lusha runs outreach
Prospects, sends, and replies sync into Twenty CRM, keeping lead status current without manual imports.
Where Lusha supplies contact or company data
Enriched fields land directly on records in Twenty CRM, and refreshes keep them from going stale.
Where Lusha can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Twenty CRM sync into Lusha, so people working there have the context without switching tools.
What you can sync between Lusha and Twenty CRM
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.
| Lusha objects | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. | Attachments Files linked to records. | Phone Numbers is specific to Lusha and Attachments to Twenty CRM — each maps to any object or custom field on the other side. | |
| Prospecting Results Search-based lists of people and companies matching filters, used to seed lead lists. | Workspace Members User accounts used for record ownership and assignment mapping. | Prospecting Results is specific to Lusha and Workspace Members to Twenty CRM — each maps to any object or custom field on the other side. | |
| Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Bulk Enrichment Requests is specific to Lusha and People to Twenty CRM — each maps to any object or custom field on the other side. | |
| Person Profiles Contact-level enrichment results (work emails, phone numbers, title, company) returned per lookup. | Companies Account-level records that group people and opportunities. | Person Profiles is specific to Lusha and Companies to Twenty CRM — each maps to any object or custom field on the other side. | |
| Company Profiles Firmographic records (industry, size, location) appended to account or company rows. | Opportunities Deal records tracked through pipeline stages, synced for forecasting. | Company Profiles is specific to Lusha and Opportunities to Twenty CRM — each maps to any object or custom field on the other side. | |
| Email Addresses Work emails written into CRM contact fields during enrichment. | Tasks To-dos linked to people, companies, or deals. | Email Addresses is specific to Lusha and Tasks to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Lusha and Twenty CRM
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.
Lusha Twenty CRM 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 written to Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Lusha Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
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 Twenty CRM records.
Rate-limit considerations
- Lusha: Lookups consume credits and are subject to the platform's API rate limits.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Lusha ⇄ Twenty CRM
Connect Lusha and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lusha–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Lusha or Twenty CRM 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 Lusha or Twenty CRM record.
Observability
Monitoring
Track your Lusha ⇄ Twenty CRM sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Lusha and Twenty CRM.
How the Lusha and Twenty CRM connectors work
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.
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Lusha to Twenty CRM — 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 Lusha and Twenty CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Lusha
connected
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Lusha and Twenty CRM 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 · Lusha ⇄ Twenty CRMCustomers 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.
Lusha Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Lusha and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Lusha and Twenty CRM — 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.
-
Change detection on Lusha: Not event-driven; data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change. On Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Lusha side: Phone Numbers, Prospecting Results, Bulk Enrichment Requests, Person Profiles, plus custom fields where Lusha exposes them. On the Twenty CRM side: Custom Objects, Attachments, Workspace Members, People. 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 Twenty CRM. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Lusha and Twenty CRM: Where Lusha runs outreach; Where Lusha supplies contact or company data; Where Lusha can store CRM context: fields kept current. Prospects, sends, and replies sync into Twenty CRM, keeping lead status current without manual imports.
-
Lusha: REST API. Authentication: API key. Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
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 304 integrations available for Lusha and Twenty CRM.
Popular · 7 of 304
-
Lusha ⇄ Freshworks CRM -
Lusha ⇄ Gladly -
Lusha ⇄ Infor CRM -
Twenty CRM ⇄ Monday -
Twenty CRM ⇄ Notion -
Twenty CRM ⇄ Quip -
Twenty CRM ⇄ Smartsheet
No integrations match .
