Real-time
Two-way sync
Changes in Hibob or MariaDB instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Database
Hibob to MariaDB integration — real-time, two-way sync
Keep Hibob and MariaDB 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 MariaDB
Put your workforce data where your apps can reach it: MariaDB 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. MariaDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: People (Employees), Employment, Work, Salaries in Hibob need to exist as queryable JSON Columns, Stored Procedures, Databases (Schemas), Tables in MariaDB 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 JSON Columns, Stored Procedures, Databases (Schemas), Tables in MariaDB with People (Employees), Employment, Work, Salaries 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 Keep several MariaDB instances aligned with one system of record across environments
- 02 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
- 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
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.
Reporting and analytics on current data
People (Employees), Employment, Work, Salaries replicate into MariaDB 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 MariaDB, so hierarchy-driven logic and permissions don't drift.
What you can sync between Hibob and MariaDB
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 | MariaDB 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. | JSON Columns Semi-structured payloads validated with JSON functions. | Time off is specific to Hibob and JSON Columns to MariaDB — 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. | Stored Procedures Server-side logic that can post-process synced rows. | Lifecycle is specific to Hibob and Stored Procedures to MariaDB — 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. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Documents is specific to Hibob and Databases (Schemas) to MariaDB — 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. | Tables The primary sync target; rows map to records in connected systems. | Named lists is specific to Hibob and Tables to MariaDB — 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. | Views Read-side projections used as outbound sync sources. | People (Employees) is specific to Hibob and Views to MariaDB — 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. | Columns Field-level mapping targets with engine-typed values. | Employment is specific to Hibob and Columns to MariaDB — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and MariaDB
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 MariaDB 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 MariaDB as a row-level write, with types converted between the two schemas.
MariaDB Hibob Sub-second propagation
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
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.
- MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Hibob ⇄ MariaDB
Connect Hibob and MariaDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–MariaDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or MariaDB 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 MariaDB record.
Observability
Monitoring
Track your Hibob ⇄ MariaDB 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 MariaDB.
How the Hibob and MariaDB 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.
MariaDB
- Integration surface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect Hibob to MariaDB — 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 MariaDB 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
MariaDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and MariaDB 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 ⇄ MariaDBCustomers 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 MariaDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and MariaDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and MariaDB: 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.
-
MariaDB: System-versioned (temporal) tables can retain full row history natively, which helps audit what a sync changed and when. Hibob: The GET Read-all-company-employees and Read-by-ID endpoints are legacy; Bob steers reads to POST /people/search, which the docs rate-limit at 50 requests per minute. Stacksync's field mapping accounts for these differences between Hibob and MariaDB 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 MariaDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Hibob and MariaDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–MariaDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Hibob and MariaDB. 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 MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 MariaDB.
Popular · 7 of 443
-
Hibob ⇄ Amazon DynamoDB -
Hibob ⇄ Reltio -
Hibob ⇄ SAP Hana -
Hibob ⇄ Jdbc -
MariaDB ⇄ Paylocity -
MariaDB ⇄ Ukg Ready -
MariaDB ⇄ BambooHR
No integrations match .
