Real-time
Two-way sync
Changes in Hibob or PostgreSQL instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Database
Hibob to PostgreSQL integration — real-time, two-way sync
Keep Hibob and PostgreSQL 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 PostgreSQL
Put your workforce data where your apps can reach it: PostgreSQL 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. PostgreSQL is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Employment, Work, Salaries, Time off in Hibob need to exist as queryable JSONB Columns, Sequences, Custom Types and Enums, Tables in PostgreSQL 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 JSONB Columns, Sequences, Custom Types and Enums, Tables in PostgreSQL with Employment, Work, Salaries, Time off 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 Let an application write to its own database and have those rows appear as records in business systems in near real time
- 02 Consolidate data from several microservice databases into one operational Postgres store
- 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
Computed and operational fields flow back
Values assembled or corrected in PostgreSQL write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.
Mirror people records into the database
Records maintained in Hibob land as queryable JSONB Columns, Sequences, Custom Types and Enums, Tables in PostgreSQL, so internal apps and dashboards read live data instead of a periodic export.
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.
What you can sync between Hibob and PostgreSQL
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 | PostgreSQL objects | How this pairing syncs | |
|---|---|---|---|
| Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. | Time off is specific to Hibob and Primary and Unique Keys to PostgreSQL — 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. | JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. | Lifecycle is specific to Hibob and JSONB Columns to PostgreSQL — each maps to any object or custom field on the other side. | |
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Sequences Generate surrogate keys for rows created by inbound syncs. | Documents is specific to Hibob and Sequences to PostgreSQL — 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. | Custom Types and Enums Constrain synced values to a fixed set, mirroring picklist fields. | Named lists is specific to Hibob and Custom Types and Enums to PostgreSQL — 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 The primary sync target; rows map one-to-one to records in connected SaaS systems. | People (Employees) is specific to Hibob and Tables to PostgreSQL — 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. | Views Read-side projections used to expose joined or filtered data to a sync. | Employment is specific to Hibob and Views to PostgreSQL — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and PostgreSQL
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 PostgreSQL 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 PostgreSQL as a row-level write, with types converted between the two schemas.
PostgreSQL Hibob Sub-second propagation
DetectionChanges in PostgreSQL are captured at the source via change data capture — no polling loop against its API. Logical replication (wal_level = logical) for change data capture via the "Postgres" connector.
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.
- PostgreSQL: No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput.
What ships with Hibob ⇄ PostgreSQL
Connect Hibob and PostgreSQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–PostgreSQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or PostgreSQL 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 PostgreSQL record.
Observability
Monitoring
Track your Hibob ⇄ PostgreSQL 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 PostgreSQL.
How the Hibob and PostgreSQL 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.
PostgreSQL
- Integration surface
- SQL wire protocol (PostgreSQL frontend/backend protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
- Change detection
- Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput
How it works
How to connect Hibob to PostgreSQL — 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 PostgreSQL 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
PostgreSQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and PostgreSQL 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 ⇄ PostgreSQLCustomers 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 PostgreSQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and PostgreSQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and PostgreSQL: authenticate both systems, choose the objects to sync (such as Hibob's Time off and Lifecycle), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. PostgreSQL: SQL wire protocol (PostgreSQL frontend/backend protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user. Stacksync manages authentication, retries, and rate limits on both sides.
-
PostgreSQL: Renaming schemas, tables, or columns will break Stacksync configuration (requires manual sync configuration update). 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 PostgreSQL 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 PostgreSQL records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Hibob and PostgreSQL connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–PostgreSQL integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Hibob and PostgreSQL. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 545 integrations available for Hibob and PostgreSQL.
Popular · 8 of 545
-
Hibob ⇄ Amazon RDS -
Hibob ⇄ Supabase -
Hibob ⇄ MySQL -
Hibob ⇄ MariaDB -
PostgreSQL ⇄ Namely -
PostgreSQL ⇄ Paylocity -
PostgreSQL ⇄ Ukg Ready -
PostgreSQL ⇄ BambooHR
No integrations match .
