Skip to content
Human resources ⇄ Data warehouse

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

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

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

Stacksync syncs Salaries, Time off, Lifecycle, Documents from Hibob into tables in Tinybird continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Tinybird, 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 Stream CRM activity such as deals and tickets into Tinybird Data Sources to power customer-facing dashboards.
  • 02 Sync order events from an ERP into Tinybird to serve low-latency operational analytics endpoints.
  • 03 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.
  • 04 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.

Common sync patterns

Write-back of computed values

Segments, rollups, or risk flags computed in Tinybird 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 Tinybird 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 Tinybird for reporting the HR system cannot produce on its own.

What you can sync between Hibob and Tinybird

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 Tinybird 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. Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. People (Employees) is specific to Hibob and Workspaces to Tinybird — 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. Tokens Scoped credentials that control read and append rights per resource. Employment is specific to Hibob and Tokens to Tinybird — 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. Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. Work is specific to Hibob and Data Sources to Tinybird — 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. Pipes Chained SQL nodes that transform Data Sources into query-ready results. Salaries is specific to Hibob and Pipes to Tinybird — 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. API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. Time off is specific to Hibob and API Endpoints to Tinybird — 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. Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. Lifecycle is specific to Hibob and Materialized Views to Tinybird — each maps to any object or custom field on the other side.

How changes propagate between Hibob and Tinybird

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

Tinybird Hibob Interval-based propagation

DetectionStacksync polls Tinybird for changes on an incremental schedule, reading only records changed since the previous pass. Append-oriented ingestion.

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.
  • Tinybird: Subject to the platform's ingestion and query rate limits; batch appends where possible.
What ships with Hibob ⇄ Tinybird

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Tinybird

Integration surface
REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect
Authentication
Scoped auth tokens
Change detection
Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC
Capabilities
read · write
Rate limits
Subject to the platform's ingestion and query rate limits; batch appends where possible.
How it works

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

    Choose tables

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

Hibob and Tinybird 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 431 integrations available for Hibob and Tinybird.

Popular · 7 of 431
All Hibob integrations All Tinybird 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