Two-way sync
Changes in BigQuery or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery and Smartrecruiters 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 Smartrecruiters 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 Applications, Jobs, Job Postings, Interviews from Smartrecruiters 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 Smartrecruiters 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 Smartrecruiters'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 Smartrecruiters, where the HR team sees them in the system they already use.
People and organization records from Smartrecruiters 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.
| BigQuery objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Projects Connection scope: the service account grants access per project. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Projects is specific to BigQuery and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Tables is specific to BigQuery and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Partitioned tables is specific to BigQuery and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Clustered tables Supported; clustering is transparent to the sync. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Clustered tables is specific to BigQuery and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Datasets is specific to BigQuery and Jobs to Smartrecruiters — 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.
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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Smartrecruiters connection.
Changes in BigQuery or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BigQuery or Smartrecruiters record.
Track your BigQuery ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and Smartrecruiters.
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 BigQuery and Smartrecruiters 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 BigQuery and Smartrecruiters 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 BigQuery and Smartrecruiters: authenticate both systems, choose the objects to sync (such as BigQuery's Projects and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on BigQuery: 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. On Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the BigQuery side: Clustered tables, Datasets, Projects, Tables, plus custom fields where BigQuery exposes them. On the Smartrecruiters side: Applications, Jobs, Job Postings, Interviews. Stacksync auto-detects both schemas and converts types between the two systems.
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 BigQuery and Smartrecruiters: 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 Smartrecruiters's records change over time, for headcount planning and audit questions.
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. Smartrecruiters: SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions. Authentication: X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions. Stacksync manages authentication, retries, and rate limits on both sides.
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 542 integrations available for BigQuery and Smartrecruiters.