Skip to content
Database ⇄ Human resources

Google Cloud SQL to Hibob integration — real-time, two-way sync

Keep Google Cloud SQL and Hibob 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 Google Cloud SQL and Hibob

Put your workforce data where your apps can reach it: Google Cloud SQL 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. Google Cloud SQL 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 Tables, Rows, Views, Transaction logs in Google Cloud SQL 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 Tables, Rows, Views, Transaction logs in Google Cloud SQL 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 Keep an internal admin application backed by Cloud SQL consistent with an ERP or billing system.
  • 02 Migrate from a self-managed database by syncing Cloud SQL and the legacy system during cutover.
  • 03 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
  • 04 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.

Common sync patterns

Mirror people records into the database

Records maintained in Hibob land as queryable Tables, Rows, Views, Transaction logs in Google Cloud SQL, 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.

Reporting and analytics on current data

Work, Salaries, Time off, Lifecycle replicate into Google Cloud SQL where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

What you can sync between Google Cloud SQL and Hibob

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.

Google Cloud SQL objects Hibob objects How this pairing syncs
Databases Scope the tables included in a sync configuration. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Databases is specific to Google Cloud SQL and Work to Hibob — each maps to any object or custom field on the other side.
Schemas Namespace tables in PostgreSQL and SQL Server instances. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Schemas is specific to Google Cloud SQL and Salaries to Hibob — each maps to any object or custom field on the other side.
Tables Mapped directly to sync targets; schema changes can be propagated. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Tables is specific to Google Cloud SQL and Time off to Hibob — each maps to any object or custom field on the other side.
Rows Read and written by primary key during each sync cycle. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Rows is specific to Google Cloud SQL and Lifecycle to Hibob — each maps to any object or custom field on the other side.
Views Read-only sources for shaping data before syncing it out. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Views is specific to Google Cloud SQL and Documents to Hibob — each maps to any object or custom field on the other side.
Transaction logs MySQL binlog or PostgreSQL WAL, the source for log-based change capture. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Transaction logs is specific to Google Cloud SQL and Named lists to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud SQL and Hibob

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.

Google Cloud SQL Hibob Sub-second propagation

DetectionChanges in Google Cloud SQL are captured at the source via change data capture — no polling loop against its API. Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking.

DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Google Cloud SQL: Constrained by instance size and connection limits rather than API quotas.
  • 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.
What ships with Google Cloud SQL ⇄ Hibob

Connect Google Cloud SQL and Hibob for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Google Cloud SQL ⇄ Hibob sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud SQL and Hibob.

How the Google Cloud SQL and Hibob connectors work

Google Cloud SQL

Integration surface
Native SQL wire protocols (MySQL, PostgreSQL, SQL Server) plus a REST admin API for instance management
Authentication
Database credentials; IAM database authentication is available for MySQL and PostgreSQL
Change detection
Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Constrained by instance size and connection limits rather than API quotas.

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
How it works

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

    Choose tables

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

Google Cloud SQL and Hibob 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 435 integrations available for Google Cloud SQL and Hibob.

Popular · 7 of 435
All Google Cloud SQL integrations All Hibob 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