Skip to content
Data warehouse ⇄ Human resources

BigQuery to Hibob integration — real-time, two-way sync

Keep BigQuery 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 BigQuery and Hibob

Land the people and organization records from Hibob in BigQuery 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 BigQuery next to everything else the company measures.

Stacksync syncs Named lists, People (Employees), Employment, Work from Hibob into tables in BigQuery continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in BigQuery, 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 Feed ML feature tables in BigQuery from operational systems on a continuous schedule
  • 02 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 03 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
  • 04 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.

Common sync patterns

Headcount and cost joined with everything else

Analysts combine Hibob's workforce records with finance, product, or operational data already in BigQuery 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.

Queryable history for planning and audit

A continuously synced copy in BigQuery gives you a durable, queryable record of how Hibob's records change over time, for headcount planning and audit questions.

What you can sync between BigQuery 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.

BigQuery objects Hibob objects How this pairing syncs
Tables The syncable unit: only tables can be synced per the Stacksync docs. Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Tables is specific to BigQuery and Work to Hibob — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Partitioned tables is specific to BigQuery and Salaries to Hibob — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Clustered tables is specific to BigQuery and Time off to Hibob — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Datasets is specific to BigQuery and Lifecycle to Hibob — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Projects is specific to BigQuery and Documents to Hibob — each maps to any object or custom field on the other side.

How changes propagate between BigQuery 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.

BigQuery Hibob Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

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

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

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • 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 BigQuery ⇄ Hibob

Connect BigQuery and Hibob for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and Hibob.

How the BigQuery and Hibob connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

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

    Choose tables

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

BigQuery 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 542 integrations available for BigQuery and Hibob.

Popular · 8 of 542
All BigQuery 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