Real-time
Two-way sync
Changes in Hibob or Rockset instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Data warehouse
Hibob to Rockset integration — real-time, two-way sync
Keep Hibob and Rockset 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 Rockset
Land the people and organization records from Hibob in Rockset 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 Rockset next to everything else the company measures.
Stacksync syncs Work, Salaries, Time off, Lifecycle from Hibob into tables in Rockset continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Rockset, 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 Serve real-time dashboards over CRM and ERP records synced from operational databases.
- 02 Sync Postgres or DynamoDB tables into collections for low-latency aggregations without loading a batch warehouse.
- 03 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
- 04 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
Common sync patterns
Write-back of computed values
Segments, rollups, or risk flags computed in Rockset sync back onto the matching records in Hibob, where the HR team sees them in the system they already use.
HR data in the warehouse, minus the pipeline
People and organization records from Hibob arrive in Rockset as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Headcount and cost joined with everything else
Analysts combine Hibob's workforce records with finance, product, or operational data already in Rockset for reporting the HR system cannot produce on its own.
What you can sync between Hibob and Rockset
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 | Rockset objects | How this pairing syncs | |
|---|---|---|---|
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Documents JSON records addressable by _id, written via the Write API in sync pipelines. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. | People (Employees) is specific to Hibob and Query Lambdas to Rockset — 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. | Aliases Stable names that point at collections, used to swap datasets without changing queries. | Employment is specific to Hibob and Aliases to Rockset — 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. | Integrations Managed source connections (databases, streams, object storage) feeding collections. | Work is specific to Hibob and Integrations to Rockset — 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. | Virtual Instances Isolated compute units that separate ingest from query workloads. | Salaries is specific to Hibob and Virtual Instances to Rockset — 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. | Collections Schemaless document containers that ingested and synced records land in. | Time off is specific to Hibob and Collections to Rockset — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Rockset
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 Rockset 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 Rockset as a row-level write, with types converted between the two schemas.
Rockset Hibob Interval-based propagation
DetectionStacksync polls Rockset for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL queries on timestamp fields.
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.
What ships with Hibob ⇄ Rockset
Connect Hibob and Rockset for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Rockset connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Rockset 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 Rockset record.
Observability
Monitoring
Track your Hibob ⇄ Rockset 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 Rockset.
How the Hibob and Rockset 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.
Rockset
- Integration surface
- REST API (SQL over HTTP, plus a document Write API)
- Authentication
- API key
- Change detection
- Polling via SQL queries on timestamp fields; ingestion-side change capture is handled by Rockset's managed source connectors
- Capabilities
- read · write
How it works
How to connect Hibob to Rockset — 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.
- 01
Connect your apps
Authenticate Hibob and Rockset with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Hibob
connected
Rockset
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Rockset 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.
objects · Hibob ⇄ RocksetCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Hibob RocksetCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Rockset integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Rockset: authenticate both systems, choose the objects to sync (such as Hibob's Documents and People (Employees)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Hibob and Rockset. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Hibob: 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). On Rockset: Polling via SQL queries on timestamp fields; ingestion-side change capture is handled by Rockset's managed source connectors. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Rockset side: Query Lambdas, Aliases, Integrations, Virtual Instances, plus custom fields where Rockset exposes them. On the Hibob side: Work, Salaries, Time off, Lifecycle. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Hibob and Rockset: Write-back of computed values; HR data in the warehouse, minus the pipeline; Headcount and cost joined with everything else. Segments, rollups, or risk flags computed in Rockset sync back onto the matching records in Hibob, where the HR team sees them in the system they already use.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 502 integrations available for Hibob and Rockset.
Popular · 6 of 502
-
Hibob ⇄ Amazon Redshift -
Hibob ⇄ Apache Doris -
Hibob ⇄ Apache Druid -
Rockset ⇄ Paylocity -
Rockset ⇄ Ukg Ready -
Rockset ⇄ BambooHR
No integrations match .
