Skip to content
Human resources ⇄ Business productivity

Hibob to Lusha integration — real-time data sync

Keep Hibob 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 Hibob and Lusha

Keep the people, teams, and status that Lusha and Hibob 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 Hibob, so Hibob 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. Hibob 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 Re-verify stale contact data on a schedule and flag records that no longer resolve.
  • 02 Enrich new CRM leads with work emails and direct dials the moment they are created.
  • 03 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.
  • 04 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.

Common sync patterns

Offboarding: no standing access after a departure

When someone is marked as leaving in Hibob, 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.

Org and team structure kept current

Department, team, and reporting-line changes from Hibob keep the groups, queues, or projects in Lusha assigned to the right people.

What you can sync between Hibob 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.

Hibob objects Lusha objects How this pairing syncs
Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. Salaries is specific to Hibob and Phone Numbers to Lusha — each maps to any object or custom field on the other side.
Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Prospecting Results Search-based lists of people and companies matching filters, used to seed lead lists. Time off is specific to Hibob and Prospecting Results to Lusha — each maps to any object or custom field on the other side.
Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. Lifecycle is specific to Hibob and Bulk Enrichment Requests to Lusha — each maps to any object or custom field on the other side.
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Person Profiles Contact-level enrichment results (work emails, phone numbers, title, company) returned per lookup. Documents is specific to Hibob and Person Profiles to Lusha — each maps to any object or custom field on the other side.
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Company Profiles Firmographic records (industry, size, location) appended to account or company rows. Named lists is specific to Hibob and Company Profiles to Lusha — each maps to any object or custom field on the other side.
People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. Email Addresses Work emails written into CRM contact fields during enrichment. People (Employees) is specific to Hibob and Email Addresses to Lusha — each maps to any object or custom field on the other side.

How changes propagate between Hibob 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.

Hibob Lusha Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

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 Hibob records.

Lusha Hibob 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 Hibob through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
  • Lusha: Lookups consume credits and are subject to the platform's API rate limits.
What ships with Hibob ⇄ Lusha

Connect Hibob and Lusha for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Lusha connection.

Real-time

Real-time sync

Changes in Hibob or Lusha instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Hibob 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 Hibob or Lusha record.

Observability

Monitoring

Track your Hibob ⇄ Lusha sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Hibob and Lusha.

How the Hibob and Lusha connectors work

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob setup guide

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 Hibob 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.

  1. 01

    Connect your apps

    Authenticate Hibob 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Hibob connected
    Lusha connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Hibob ⇄ Lusha
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Hibob Lusha
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and Lusha integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 375 integrations available for Hibob and Lusha.

Popular · 8 of 375
All Hibob integrations All Lusha integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own