Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: SingleStore 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. SingleStore is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: People (Employees), Employment, Work, Salaries in Hibob need to exist as queryable Views, Reference Tables, Pipelines, Stored Procedures in SingleStore 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, Reference Tables, Pipelines, Stored Procedures in SingleStore with People (Employees), Employment, Work, Salaries 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 Mirror CRM and SaaS objects into SingleStore tables to serve low-latency operational dashboards.
  • 02 Sync results of real-time analytical queries back into business tools where teams act on them.
  • 03 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.
  • 04 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.

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

People (Employees), Employment, Work, Salaries replicate into SingleStore 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 SingleStore, so hierarchy-driven logic and permissions don't drift.

What you can sync between Hibob and SingleStore

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 SingleStore objects How this pairing syncs
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. Pipelines Native ingestion jobs from Kafka or object storage that coexist with external syncs. People (Employees) is specific to Hibob and Pipelines to SingleStore — 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. Stored Procedures Existing logic sometimes invoked on write paths. Employment is specific to Hibob and Stored Procedures to SingleStore — 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. Indexes and Shard Keys Determine data distribution and lookup speed for sync match keys. Work is specific to Hibob and Indexes and Shard Keys to SingleStore — 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. Databases The connection target containing the tables a sync addresses. Salaries is specific to Hibob and Databases to SingleStore — 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. Tables (rowstore and columnstore) Primary read/write target; storage type affects whether a table suits point lookups or scans. Time off is specific to Hibob and Tables (rowstore and columnstore) to SingleStore — each maps to any object or custom field on the other side.
Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Views Read-only projections used as curated sync sources. Lifecycle is specific to Hibob and Views to SingleStore — each maps to any object or custom field on the other side.

How changes propagate between Hibob and SingleStore

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

SingleStore Hibob Interval-based propagation

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

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.
  • SingleStore: No API rate limits; throughput is bounded by workspace or cluster size.
What ships with Hibob ⇄ SingleStore

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

SingleStore

Integration surface
SQL over the MySQL wire protocol; an HTTP Data API is also available for SQL over REST
Authentication
Database credentials
Change detection
Polling on timestamp or watermark columns; the platform also provides change-observation features in recent versions
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by workspace or cluster size
How it works

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

    Choose tables

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

Hibob and SingleStore 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 449 integrations available for Hibob and SingleStore.

Popular · 7 of 449
All Hibob integrations All SingleStore 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