Skip to content
Human resources

Connect Hibob to any app with two-way sync.

Two-way sync Hibob across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes
Setup guide: how Stacksync connects to Hibob

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
Object catalog

What Stacksync syncs in Hibob.

These objects sync between Hibob and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Hibob exposes them.

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.
Employment
Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate.
Work
Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories.
Salaries
Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user.
Time off
Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances.
Lifecycle
Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events.
Documents
Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user.
Named lists
Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync.
API surface

How Stacksync connects to Hibob.

The connector runs on Hibob's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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).
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
Hibob connector documentation
What ships with Hibob

Connect Hibob for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Hibob instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Hibob connector.

HiBob (Bob) is the HRIS system of record for mid-market and scaling companies, owned by People Operations and HRIS admins. Employee master data lives here: profiles, employment and work history, compensation, time off, and lifecycle status. IT, payroll, and finance all depend on it for provisioning, pay runs, and headcount reporting, so it is the source every downstream system needs to read from and, for corrections, write back to.

  • HRIS admins
  • People Operations
  • IT and IdP admins
  • Payroll teams
  • HR data and analytics

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

  2. Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.

  3. Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.

  4. Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.

  5. Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.

  6. Two-way sync of People profiles and Work records with an operational Postgres so internal apps and directories read employee data in SQL while HR corrections made anywhere flow back into Bob.

All Hibob integrations

Pick the system you need to keep in sync with Hibob. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 45

ERP · 38

Database · 50

Data warehouse · 29

Business productivity · 40

Accounting and finance · 17

How it works

Set up Hibob in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Hibob connector FAQ

What can I sync with the Hibob connector?

Hibob's core objects — People (Employees), Employment, Work, Salaries and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Hibob?

Via REST API (the Bob API), authenticated with Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin. Changes are detected as follows — 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).. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Hibob connector two-way?

Yes. Changes made in Hibob propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Hibob integration take to set up?

Most Hibob integrations go live in minutes: authenticate Hibob and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Hibob data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Hibob data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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