Skip to content
Data warehouse ⇄ Human resources

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

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

Land the people and organization records from Hibob in Exasol as live tables for workforce reporting, without extract jobs, and write computed results back where Hibob can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Hibob is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Exasol next to everything else the company measures.

Stacksync syncs People (Employees), Employment, Work, Salaries from Hibob into tables in Exasol continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Exasol, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Hibob where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Sync computed metrics or customer segments from Exasol back into a CRM for sales and marketing use (reverse ETL).
  • 02 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
  • 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

Headcount and cost joined with everything else

Analysts combine Hibob's workforce records with finance, product, or operational data already in Exasol for reporting the HR system cannot produce on its own.

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

Queryable history for planning and audit

A continuously synced copy in Exasol gives you a durable, queryable record of how Hibob's records change over time, for headcount planning and audit questions.

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

Exasol objects Hibob objects How this pairing syncs
Schemas Namespaces that group the tables a sync reads from or writes into. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Schemas is specific to Exasol and Time off to Hibob — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Tables is specific to Exasol and Lifecycle to Hibob — each maps to any object or custom field on the other side.
Views Read-only query surfaces often used as curated sources for reverse ETL. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Views is specific to Exasol and Documents to Hibob — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Virtual schemas is specific to Exasol and Named lists to Hibob — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. 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. UDF scripts is specific to Exasol and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Users and roles is specific to Exasol and Employment to Hibob — each maps to any object or custom field on the other side.

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

Exasol Hibob Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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

Hibob Exasol 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 applied to Exasol as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • 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 Exasol ⇄ Hibob

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Exasol and Hibob connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

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 Exasol 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 Exasol 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
    Exasol connected
    Hibob connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Exasol 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 432 integrations available for Exasol and Hibob.

Popular · 7 of 432
All Exasol 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