Skip to content
Data warehouse ⇄ Human resources

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

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.

  • 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 Smartrecruiters

Land the people and organization records from Smartrecruiters in BigQuery as live tables for workforce reporting, without extract jobs, and write computed results back where Smartrecruiters 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 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.

Common use cases

  • 01 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 02 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools
  • 03 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.
  • 04 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.

Common sync patterns

Queryable history for planning and audit

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.

Write-back of computed values

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.

HR data in the warehouse, minus the pipeline

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.

What you can sync between BigQuery and Smartrecruiters

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.

How changes propagate between BigQuery and Smartrecruiters

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 Smartrecruiters 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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.

Smartrecruiters BigQuery Sub-second propagation

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.

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.
  • Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with BigQuery ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your BigQuery ⇄ Smartrecruiters 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 Smartrecruiters.

How the BigQuery and Smartrecruiters 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

Smartrecruiters

Integration surface
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
Change detection
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.
Capabilities
read · write · webhooks
Rate limits
Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
Smartrecruiters setup guide
How it works

How to connect BigQuery to Smartrecruiters — 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 Smartrecruiters 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
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · BigQuery ⇄ Smartrecruiters
    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 Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

BigQuery and Smartrecruiters 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 542 integrations available for BigQuery and Smartrecruiters.

Popular · 8 of 542
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.