Real-time
Real-time sync
Changes in Lusha or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Human resources
Lusha to Smartrecruiters integration — real-time data sync
Keep Lusha and Smartrecruiters 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 Smartrecruiters
Keep the people, teams, and status that Lusha and Smartrecruiters share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Lusha is a read-only source: Stacksync reads its data in real time and delivers it into Smartrecruiters, so Smartrecruiters always reflects the current state of Lusha — without exports, scripts, or schedulers.
Each tool in Lusha keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Smartrecruiters is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
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 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
- 04 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.
Common sync patterns
Onboarding: access ready on day one
A new hire recorded in Smartrecruiters creates the matching user in Lusha with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Smartrecruiters, the matching account in Lusha is deactivated or flagged, so departures do not leave open access behind.
One employee directory
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
What you can sync between Lusha and Smartrecruiters
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Bulk Enrichment Requests is specific to Lusha and Users to Smartrecruiters — 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. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Person Profiles is specific to Lusha and Approvals to Smartrecruiters — 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. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Company Profiles is specific to Lusha and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Email Addresses Work emails written into CRM contact fields during enrichment. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Email Addresses is specific to Lusha and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Phone Numbers is specific to Lusha and Jobs to Smartrecruiters — 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. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Prospecting Results is specific to Lusha and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Lusha and Smartrecruiters
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 Smartrecruiters 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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Lusha Sub-second propagation
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
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 Smartrecruiters records.
Rate-limit considerations
- Lusha: Lookups consume credits and are subject to the platform's API rate limits.
- Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with Lusha ⇄ Smartrecruiters
Connect Lusha and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lusha–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Lusha or Smartrecruiters 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 Smartrecruiters record.
Observability
Monitoring
Track your Lusha ⇄ Smartrecruiters 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 Smartrecruiters.
How the Lusha and Smartrecruiters 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.
Smartrecruiters
- Integration surface
- SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions
- Authentication
- X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions
- Change detection
- Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture.
- Capabilities
- read · write · webhooks
- Rate limits
- Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
How it works
How to connect Lusha to Smartrecruiters — 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 Smartrecruiters 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
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Lusha and Smartrecruiters 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 ⇄ SmartrecruitersCustomers 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 SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Lusha and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Lusha and Smartrecruiters — 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.
-
Yes — Stacksync ships production-grade connectors for both Lusha and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Lusha side: Prospecting Results, Bulk Enrichment Requests, Person Profiles, Company Profiles, plus custom fields where Lusha exposes them. On the Smartrecruiters side: Approvals, Candidates, Applications, Jobs. 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 Smartrecruiters. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Lusha and Smartrecruiters: Onboarding: access ready on day one; Offboarding: no standing access after a departure; One employee directory. A new hire recorded in Smartrecruiters creates the matching user in Lusha with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
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 375 integrations available for Lusha and Smartrecruiters.
Popular · 7 of 375
-
Lusha ⇄ Namely -
Lusha ⇄ Paylocity -
Lusha ⇄ Ukg Ready -
Smartrecruiters ⇄ ServiceNow -
Smartrecruiters ⇄ Slack -
Smartrecruiters ⇄ BetterContact -
Smartrecruiters ⇄ Agiloft
No integrations match .
