Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: Elasticsearch and Hibob share the same people, positions, and org structure in real time.

Hibob is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Elasticsearch is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Documents, Named lists, People (Employees), Employment in Hibob need to exist as queryable Data streams, Ingest pipelines, Index templates, Indices in Elasticsearch before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Data streams, Ingest pipelines, Index templates, Indices in Elasticsearch with Documents, Named lists, People (Employees), Employment in Hibob field by field, in real time. You decide which system owns which fields — Hibob typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Sync CRM accounts and contacts into an Elasticsearch index to power internal search across customer records.
  • 02 Push product catalog data from an ERP or commerce database into Elasticsearch for storefront search.
  • 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

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Documents, Named lists, People (Employees), Employment replicate into Elasticsearch where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Hibob stay consistent in Elasticsearch, so hierarchy-driven logic and permissions don't drift.

What you can sync between Elasticsearch and Hibob

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.

Elasticsearch objects Hibob objects How this pairing syncs
Documents The unit of sync; JSON records created, updated, and deleted by _id. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Data streams Append-only targets for time-series or event data pushed from source systems. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Data streams is specific to Elasticsearch and Time off to Hibob — each maps to any object or custom field on the other side.
Ingest pipelines Server-side transforms applied to documents as a sync writes them. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Ingest pipelines is specific to Elasticsearch and Lifecycle to Hibob — each maps to any object or custom field on the other side.
Index templates Reusable settings and mappings applied automatically to new indices a sync creates. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Index templates is specific to Elasticsearch and Named lists to Hibob — each maps to any object or custom field on the other side.
Indices Target containers for synced records; each holds a table-like collection of JSON documents. 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. Indices is specific to Elasticsearch and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Index mappings Field type definitions that determine how synced fields are indexed and queried. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Index mappings is specific to Elasticsearch and Employment to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Elasticsearch and Hibob

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.

Elasticsearch Hibob Interval-based propagation

DetectionStacksync polls Elasticsearch for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or sequence fields.

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

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

Rate-limit considerations

  • Elasticsearch: No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity.
  • 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.
What ships with Elasticsearch ⇄ Hibob

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Elasticsearch and Hibob connectors work

Elasticsearch

Integration surface
REST API (JSON over HTTP)
Authentication
API keys or basic authentication; Elastic Cloud also issues service account tokens
Change detection
Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks
Capabilities
read · write
Rate limits
No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity

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
How it works

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

    Choose tables

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

Elasticsearch and Hibob 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 520 integrations available for Elasticsearch and Hibob.

Popular · 8 of 520
All Elasticsearch integrations All Hibob 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