Real-time
Two-way sync
Changes in Hibob or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Database
Hibob to TimescaleDB integration — real-time, two-way sync
Keep Hibob and TimescaleDB 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 TimescaleDB
Put your workforce data where your apps can reach it: TimescaleDB 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. TimescaleDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Work, Salaries, Time off, Lifecycle in Hibob need to exist as queryable Regular PostgreSQL Tables, Views, Schemas, Hypertables in TimescaleDB 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 Regular PostgreSQL Tables, Views, Schemas, Hypertables in TimescaleDB with Work, Salaries, Time off, Lifecycle 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 Replicate subscription and billing events from operational Postgres tables into Timescale hypertables for time-series analysis.
- 02 Keep device or asset reference tables bi-directionally in sync between TimescaleDB and an ERP.
- 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
Reporting and analytics on current data
Work, Salaries, Time off, Lifecycle replicate into TimescaleDB 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 TimescaleDB, so hierarchy-driven logic and permissions don't drift.
Computed and operational fields flow back
Values assembled or corrected in TimescaleDB write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.
What you can sync between Hibob and TimescaleDB
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 | TimescaleDB 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. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | People (Employees) is specific to Hibob and Continuous Aggregates to TimescaleDB — 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. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | Employment is specific to Hibob and Regular PostgreSQL Tables to TimescaleDB — 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 Standard SQL views used to shape or filter data for consumers. | Work is specific to Hibob and Views to TimescaleDB — 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. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | Salaries is specific to Hibob and Schemas to TimescaleDB — 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. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | Time off is specific to Hibob and Hypertables to TimescaleDB — 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. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | Lifecycle is specific to Hibob and Chunks to TimescaleDB — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and TimescaleDB
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 TimescaleDB 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 TimescaleDB as a row-level write, with types converted between the two schemas.
TimescaleDB Hibob Sub-second propagation
DetectionChanges in TimescaleDB are captured at the source via change data capture — no polling loop against its API. Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must.
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.
- TimescaleDB: No API rate limits; throughput is bounded by database resources and connection limits.
What ships with Hibob ⇄ TimescaleDB
Connect Hibob and TimescaleDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–TimescaleDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or TimescaleDB 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 TimescaleDB record.
Observability
Monitoring
Track your Hibob ⇄ TimescaleDB 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 TimescaleDB.
How the Hibob and TimescaleDB 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.
TimescaleDB
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials
- Change detection
- Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by database resources and connection limits.
How it works
How to connect Hibob to TimescaleDB — 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 TimescaleDB 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
TimescaleDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and TimescaleDB 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 ⇄ TimescaleDBCustomers 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 TimescaleDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and TimescaleDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and TimescaleDB: authenticate both systems, choose the objects to sync (such as Hibob's People (Employees) and Employment), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 TimescaleDB: Reporting and analytics on current data; Org and structure stay aligned; Computed and operational fields flow back. Work, Salaries, Time off, Lifecycle replicate into TimescaleDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
-
Hibob: 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. TimescaleDB: SQL wire protocol (PostgreSQL). Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
-
TimescaleDB: TimescaleDB is packaged as a PostgreSQL extension, so standard Postgres drivers and SQL tooling work unchanged. Hibob: The employee.updated webhook flags which fields changed rather than sending the full record, so Bob recommends an API call for complete data; deleting a table entry triggers no webhook because Bob has no table-entry deletion event. Stacksync's field mapping accounts for these differences between Hibob and TimescaleDB without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Hibob and TimescaleDB 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.
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 429 integrations available for Hibob and TimescaleDB.
Popular · 7 of 429
-
Hibob ⇄ DuckDB -
Hibob ⇄ Elasticsearch -
Hibob ⇄ Google Cloud Spanner - Hibob ⇄ Google Cloud SQL
-
TimescaleDB ⇄ Greenhouse -
TimescaleDB ⇄ Jobvite -
TimescaleDB ⇄ Lever
No integrations match .
