Skip to content
Data warehouse ⇄ Human resources

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

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

Land the people and organization records from Hibob in Google Cloud Platform as live tables for workforce reporting, without extract jobs, and write computed results back where Hibob can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Hibob is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Google Cloud Platform next to everything else the company measures.

Stacksync syncs Employment, Work, Salaries, Time off from Hibob into tables in Google Cloud Platform continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Google Cloud Platform, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Hibob where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Publish change events to Pub/Sub so downstream services react to record updates as they happen.
  • 02 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
  • 03 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.

Common sync patterns

HR data in the warehouse, minus the pipeline

People and organization records from Hibob arrive in Google Cloud Platform as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

Headcount and cost joined with everything else

Analysts combine Hibob's workforce records with finance, product, or operational data already in Google Cloud Platform for reporting the HR system cannot produce on its own.

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

What you can sync between Google Cloud Platform 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 Platform objects Hibob objects How this pairing syncs
Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Cloud Storage objects is specific to Google Cloud Platform and Named lists to Hibob — each maps to any object or custom field on the other side.
Pub/Sub topics Event streams used to move change events between systems in near real time. 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. Pub/Sub topics is specific to Google Cloud Platform and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Firestore documents Document data read and written through the Firestore API for app-facing syncs. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Firestore documents is specific to Google Cloud Platform and Employment to Hibob — each maps to any object or custom field on the other side.
Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Spanner tables is specific to Google Cloud Platform and Work to Hibob — each maps to any object or custom field on the other side.
BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. BigQuery datasets is specific to Google Cloud Platform and Salaries to Hibob — each maps to any object or custom field on the other side.
BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. BigQuery tables is specific to Google Cloud Platform and Time off to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Platform 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 Platform Hibob Sub-second propagation

DetectionGoogle Cloud Platform pushes changes as they happen — webhook events backed by change data capture. Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery.

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

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

Rate-limit considerations

  • Google Cloud Platform: Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits.
  • 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 Platform ⇄ Hibob

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

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

Real-time

Two-way sync

Changes in Google Cloud Platform 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 Platform 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 Platform or Hibob record.

Observability

Monitoring

Track your Google Cloud Platform ⇄ 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 Platform and Hibob.

How the Google Cloud Platform and Hibob connectors work

Google Cloud Platform

Integration surface
Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols
Authentication
IAM service accounts with OAuth 2.0 tokens
Change detection
Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables
Capabilities
read · write · CDC · webhooks
Rate limits
Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits

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 Platform 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 Platform 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 Platform connected
    Hibob connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

Popular · 8 of 539
All Google Cloud Platform 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