Two-way sync
Changes in BambooHR or BigQuery instantly reflect in both systems. No stale data, no manual imports.
Keep BambooHR and BigQuery in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 BambooHR 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 Employees, Job Information, Compensation, Time Off from BambooHR 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 BambooHR where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
A continuously synced copy in BigQuery gives you a durable, queryable record of how BambooHR's records change over time, for headcount planning and audit questions.
Segments, rollups, or risk flags computed in BigQuery sync back onto the matching records in BambooHR, where the HR team sees them in the system they already use.
People and organization records from BambooHR arrive in BigQuery as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
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.
| BambooHR objects | BigQuery objects | How this pairing syncs | |
|---|---|---|---|
| Compensation Effective-dated pay rate, schedule, and change reason; read into planning and payroll systems with access restricted to authorized fields. | Clustered tables Supported; clustering is transparent to the sync. | Compensation is specific to BambooHR and Clustered tables to BigQuery — each maps to any object or custom field on the other side. | |
| Time Off Requests, balances, and policies; read for absence calendars and capacity planning, with approved requests written from an external scheduling tool. | Datasets Organizational container — you pick which dataset’s tables to sync. | Time Off is specific to BambooHR and Datasets to BigQuery — each maps to any object or custom field on the other side. | |
| Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. | Projects Connection scope: the service account grants access per project. | Employment Status is specific to BambooHR and Projects to BigQuery — each maps to any object or custom field on the other side. | |
| Departments and Divisions Org-structure list values; synced to keep cost centers and team groupings consistent across ERP, identity, and analytics systems. | Tables The syncable unit: only tables can be synced per the Stacksync docs. | Departments and Divisions is specific to BambooHR and Tables to BigQuery — each maps to any object or custom field on the other side. | |
| Custom Tables Company-specific effective-dated tables (assets, training, certifications); rows read and written so custom HR data isn't trapped in the HRIS. | Partitioned tables Synced like regular tables; partition columns map to target fields. | Custom Tables is specific to BambooHR and Partitioned tables to BigQuery — each maps to any object or custom field on the other side. |
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.
DetectionBambooHR notifies Stacksync of record changes through webhook events. The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling.
DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.
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 BambooHR through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BambooHR–BigQuery connection.
Changes in BambooHR or BigQuery instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BambooHR or BigQuery data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BambooHR or BigQuery record.
Track your BambooHR ⇄ BigQuery sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BambooHR and BigQuery.
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.
Authenticate BambooHR and BigQuery with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the BambooHR and BigQuery 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BambooHR and BigQuery: authenticate both systems, choose the objects to sync (such as BambooHR's Compensation and Time Off), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 BambooHR and BigQuery: Queryable history for planning and audit; Write-back of computed values; HR data in the warehouse, minus the pipeline. A continuously synced copy in BigQuery gives you a durable, queryable record of how BambooHR's records change over time, for headcount planning and audit questions.
BambooHR: BambooHR API (REST, per-company subdomain). Authentication: API key per user over HTTP Basic auth (key as username), scoped to that user's permission level in BambooHR; OAuth/OpenID available for SSO-enabled apps. BigQuery: 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. Stacksync manages authentication, retries, and rate limits on both sides.
BigQuery: BigQuery is serverless: there are no clusters or warehouses to size, and storage and compute are billed separately. BambooHR: Job, compensation, and status data are effective-dated tables, not flat fields; reading current state means resolving the latest effective row. Stacksync's field mapping accounts for these differences between BambooHR and BigQuery 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 BambooHR and BigQuery records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 450 integrations available for BambooHR and BigQuery.