Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: DuckDB 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. DuckDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Time off, Lifecycle, Documents, Named lists in Hibob need to exist as queryable Views, External files (Parquet/CSV/JSON), Attached databases, Database files in DuckDB 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 Views, External files (Parquet/CSV/JSON), Attached databases, Database files in DuckDB with Time off, Lifecycle, Documents, Named lists 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 SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • 02 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
  • 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

Time off, Lifecycle, Documents, Named lists replicate into DuckDB 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 DuckDB, so hierarchy-driven logic and permissions don't drift.

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

DuckDB objects Hibob objects How this pairing syncs
Views SQL views used to shape or filter data for downstream consumers. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Views is specific to DuckDB and Lifecycle to Hibob — each maps to any object or custom field on the other side.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. External files (Parquet/CSV/JSON) is specific to DuckDB and Documents to Hibob — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Attached databases is specific to DuckDB and Named lists to Hibob — each maps to any object or custom field on the other side.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. 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. Database files is specific to DuckDB and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Schemas is specific to DuckDB and Employment to Hibob — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Tables is specific to DuckDB and Work to Hibob — each maps to any object or custom field on the other side.

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

DuckDB Hibob Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

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

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

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • 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 DuckDB ⇄ Hibob

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the DuckDB and Hibob connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

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

    Choose tables

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

DuckDB 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 448 integrations available for DuckDB and Hibob.

Popular · 7 of 448
All DuckDB 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