Real-time
Two-way sync
Changes in Hibob or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Database
Hibob to Scaleway Postgres integration — real-time, two-way sync
Keep Hibob and Scaleway Postgres 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 Scaleway Postgres
Put your workforce data where your apps can reach it: Scaleway Postgres 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. Scaleway Postgres is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Documents, Named lists, People (Employees), Employment in Hibob need to exist as queryable Columns, Tables, Views, Materialized views in Scaleway Postgres 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 Columns, Tables, Views, Materialized views in Scaleway Postgres with Documents, Named lists, People (Employees), Employment 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 the application database into a warehouse for analytics without writing custom pipelines
- 02 Back internal tools with the same Postgres instance while Stacksync keeps it consistent with external systems
- 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
Documents, Named lists, People (Employees), Employment replicate into Scaleway Postgres 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 Scaleway Postgres, so hierarchy-driven logic and permissions don't drift.
Computed and operational fields flow back
Values assembled or corrected in Scaleway Postgres write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.
What you can sync between Hibob and Scaleway Postgres
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 | Scaleway Postgres objects | How this pairing syncs | |
|---|---|---|---|
| Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | Named lists is specific to Hibob and Columns to Scaleway Postgres — 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 Primary sync unit; each table maps to an object or table on the other side of the sync. | People (Employees) is specific to Hibob and Tables to Scaleway Postgres — 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-only sources for shaping data before it leaves the database. | Employment is specific to Hibob and Views to Scaleway Postgres — 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. | Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. | Work is specific to Hibob and Materialized views to Scaleway Postgres — 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 Namespace tables so multiple applications or environments can be synced selectively. | Salaries is specific to Hibob and Schemas to Scaleway Postgres — 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. | Sequences Generate primary keys; sync tooling must respect them when writing rows. | Time off is specific to Hibob and Sequences to Scaleway Postgres — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Scaleway Postgres
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 Scaleway Postgres 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 Scaleway Postgres as a row-level write, with types converted between the two schemas.
Scaleway Postgres Hibob Sub-second propagation
DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.
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.
- Scaleway Postgres: Throughput is bounded by instance size and connection limits rather than API quotas.
What ships with Hibob ⇄ Scaleway Postgres
Connect Hibob and Scaleway Postgres for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Scaleway Postgres connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Scaleway Postgres 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 Scaleway Postgres record.
Observability
Monitoring
Track your Hibob ⇄ Scaleway Postgres 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 Scaleway Postgres.
How the Hibob and Scaleway Postgres 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.
Scaleway Postgres
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials (username/password over TLS)
- Change detection
- Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling
- Capabilities
- read · write · CDC
- Rate limits
- Throughput is bounded by instance size and connection limits rather than API quotas
How it works
How to connect Hibob to Scaleway Postgres — 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 Scaleway Postgres 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
Scaleway Postgres
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Scaleway Postgres 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 ⇄ Scaleway PostgresCustomers 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 Scaleway PostgresCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Scaleway Postgres integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Scaleway Postgres: authenticate both systems, choose the objects to sync (such as Hibob's Named lists 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 Scaleway Postgres. 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 Scaleway Postgres: Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Scaleway Postgres side: Columns, Tables, Views, Materialized views, plus custom fields where Scaleway Postgres exposes them. On the Hibob side: Documents, Named lists, People (Employees), Employment. 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 Scaleway Postgres: Reporting and analytics on current data; Org and structure stay aligned; Computed and operational fields flow back. Documents, Named lists, People (Employees), Employment replicate into Scaleway Postgres where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
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 443 integrations available for Hibob and Scaleway Postgres.
Popular · 7 of 443
-
Hibob ⇄ IBM Db2 -
Hibob ⇄ Firebase -
Hibob ⇄ SingleStore -
Hibob ⇄ Amazon Aurora -
Scaleway Postgres ⇄ Paylocity -
Scaleway Postgres ⇄ Ukg Ready -
Scaleway Postgres ⇄ BambooHR
No integrations match .
