Skip to content
Human resources ⇄ Data warehouse

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

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

Land the people and organization records from Hibob in StarRocks 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 StarRocks next to everything else the company measures.

Stacksync syncs Work, Salaries, Time off, Lifecycle from Hibob into tables in StarRocks continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in StarRocks, 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 Continuously apply upserts from operational databases into Primary Key tables to keep analytics current
  • 02 Serve customer-facing analytics from SaaS data synced into one analytical store
  • 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

HR data in the warehouse, minus the pipeline

People and organization records from Hibob arrive in StarRocks 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 StarRocks 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.

What you can sync between Hibob and StarRocks

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 StarRocks objects How this pairing syncs
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Columns Columnar storage with types mapped from source systems during sync. Documents is specific to Hibob and Columns to StarRocks — each maps to any object or custom field on the other side.
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Databases Top-level namespaces addressed exactly as in MySQL clients. Named lists is specific to Hibob and Databases to StarRocks — each maps to any object or custom field on the other side.
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. Tables Defined with a table model (Primary Key, Unique Key, Aggregate, Duplicate Key) that determines update behavior. People (Employees) is specific to Hibob and Tables to StarRocks — 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. Materialized views Automatically maintained rollups used to accelerate queries on synced data. Employment is specific to Hibob and Materialized views to StarRocks — 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. Views Logical views for shaping analytical reads. Work is specific to Hibob and Views to StarRocks — 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. Partitions Time or range partitions that scope loads and retention. Salaries is specific to Hibob and Partitions to StarRocks — each maps to any object or custom field on the other side.

How changes propagate between Hibob and StarRocks

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

StarRocks Hibob Interval-based propagation

DetectionStacksync polls StarRocks for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling when reading.

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.
  • StarRocks: Ingestion throughput is bounded by cluster resources rather than API quotas.
What ships with Hibob ⇄ StarRocks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

StarRocks

Integration surface
MySQL wire protocol for SQL; HTTP-based Stream Load API for ingestion
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Query-based polling when reading; StarRocks is most often the destination side of a sync
Capabilities
read · write
Rate limits
Ingestion throughput is bounded by cluster resources rather than API quotas
How it works

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

    Choose tables

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

Hibob and StarRocks 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 434 integrations available for Hibob and StarRocks.

Popular · 8 of 434
All Hibob integrations All StarRocks 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