Skip to content
Human resources ⇄ Business productivity

Hibob to Lemlist integration — real-time, two-way sync

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

Keep the people, teams, and status that Lemlist and Hibob share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in Lemlist 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.

Stacksync syncs Activities, Unsubscribes, Webhooks, Team Members in Lemlist with Documents, Named lists, People (Employees), Employment in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Lemlist within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Lemlist captures details of its own, such as a corrected contact or a login identity, those can flow back to Hibob in whichever direction you configure.

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 Stop or pause sequences automatically when a reply converts to a deal in the CRM
  • 02 Mirror campaign performance data into BI tools for outbound reporting across senders
  • 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 Lemlist 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 Lemlist assigned to the right people.

What you can sync between Hibob and Lemlist

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 Lemlist objects How this pairing syncs
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Team Members Sender and seat records map outreach activity to reps in other systems. Named lists is specific to Hibob and Team Members to Lemlist — 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. Campaigns Outreach campaigns are the container leads are pushed into from CRMs and list-building workflows. People (Employees) is specific to Hibob and Campaigns to Lemlist — each maps to any object or custom field on the other side.
Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Leads Per-campaign prospect records sync in from enrichment sources and back out with status. Employment is specific to Hibob and Leads to Lemlist — each maps to any object or custom field on the other side.
Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Activities Engagement records such as opens, clicks, replies, and bounces sync to CRM timelines. Work is specific to Hibob and Activities to Lemlist — each maps to any object or custom field on the other side.
Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Unsubscribes Opt-out records propagate to other outreach tools and the CRM for compliance. Salaries is specific to Hibob and Unsubscribes to Lemlist — 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. Webhooks Hook subscriptions define which activity events are pushed to external endpoints. Time off is specific to Hibob and Webhooks to Lemlist — each maps to any object or custom field on the other side.

How changes propagate between Hibob and Lemlist

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

DeliveryEach detected change is written to Lemlist through its API, with automatic retries and rate-limit backoff.

Lemlist Hibob Sub-second propagation

DetectionLemlist notifies Stacksync of record changes through webhook events. Webhooks on outreach activity events, plus polling.

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.
  • Lemlist: Subject to the platform's API rate limits.
What ships with Hibob ⇄ Lemlist

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Hibob ⇄ Lemlist 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 Lemlist.

How the Hibob and Lemlist 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

Lemlist

Integration surface
REST API
Authentication
API key
Change detection
Webhooks on outreach activity events, plus polling
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits
How it works

How to connect Hibob to Lemlist — 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 Lemlist 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
    Lemlist connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and Lemlist 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 ⇄ Lemlist
    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 Lemlist
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and Lemlist 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 391 integrations available for Hibob and Lemlist.

Popular · 6 of 391
All Hibob integrations All Lemlist 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