Two-way sync
Changes in Google Cloud Spanner or Jobvite instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and Jobvite in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Jobvite is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Google Cloud Spanner is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Requisition (Job), Application, Workflow Status, New Hire in Jobvite need to exist as queryable Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner with Requisition (Job), Application, Workflow Status, New Hire in Jobvite field by field, in real time. You decide which system owns which fields — Jobvite typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Records maintained in Jobvite land as queryable Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Requisition (Job), Application, Workflow Status, New Hire replicate into Google Cloud Spanner where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
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 Spanner objects | Jobvite objects | How this pairing syncs | |
|---|---|---|---|
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Attachment Resumes, cover letters, and files attached to a candidate; synced out to object storage or a document management system. | Interleaved tables is specific to Google Cloud Spanner and Attachment to Jobvite — each maps to any object or custom field on the other side. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | Offer Offer state tied to an application (extended, accepted, declined); read out for offer-acceptance reporting and written to downstream comp or HR systems. | Secondary indexes is specific to Google Cloud Spanner and Offer to Jobvite — each maps to any object or custom field on the other side. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Candidate Read from the candidate feed (GET /candidate) and written back via POST /candidate/updateCandidates to change status, notes, and disposition on each record. | Change streams is specific to Google Cloud Spanner and Candidate to Jobvite — each maps to any object or custom field on the other side. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Requisition (Job) Job openings created or updated through POST /job and read from GET /jobFeed; maps to opening tables in an ATS reporting warehouse. | Views is specific to Google Cloud Spanner and Requisition (Job) to Jobvite — each maps to any object or custom field on the other side. | |
| Databases Top-level containers that scope schema and sync configuration. | Application Links a candidate to one requisition with its workflow state; read for pipeline reporting and status written back through the candidate update call. | Databases is specific to Google Cloud Spanner and Application to Jobvite — each maps to any object or custom field on the other side. | |
| Tables Relational tables mapped one-to-one to sync targets. | Workflow Status The pipeline stage per application (Screen, Interview, Offer, Hired); updated through POST /candidate/updateCandidates to advance records. | Tables is specific to Google Cloud Spanner and Workflow Status to Jobvite — 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 Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.
DeliveryEach detected change is written to Jobvite through its API, with automatic retries and rate-limit backoff.
DetectionJobvite notifies Stacksync of record changes through webhook events. A candidate hired webhook, configured per customer by a Jobvite rep, POSTs to a custom URL on hire/offer-accepted events.
DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Jobvite connection.
Changes in Google Cloud Spanner or Jobvite instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or Jobvite data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or Jobvite record.
Track your Google Cloud Spanner ⇄ Jobvite sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Jobvite.
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 Google Cloud Spanner and Jobvite 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 Google Cloud Spanner and Jobvite 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 Google Cloud Spanner and Jobvite: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Interleaved tables and Secondary indexes), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Google Cloud Spanner side: Tables, Rows, Interleaved tables, Secondary indexes, plus custom fields where Google Cloud Spanner exposes them. On the Jobvite side: Requisition (Job), Application, Workflow Status, New Hire. 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 Google Cloud Spanner and Jobvite: Mirror people records into the database; One directory of record; Reporting and analytics on current data. Records maintained in Jobvite land as queryable Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner, so internal apps and dashboards read live data instead of a periodic export.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Jobvite: REST API (JSON) with candidate, requisition (job), and employee feed endpoints under https://api.jobvite.com/{version}. Authentication: API key (api) and secret (sc) plus company ID (companyId), sent in request headers since Jobvite's April 1, 2024 move from URL-query to header-based auth. Credentials are provisioned per customer by Jobvite Support. Stacksync manages authentication, retries, and rate limits on both sides.
Google Cloud Spanner: Interleaved tables physically store child rows with their parent rows, which affects how related records are read. Jobvite: The API is rate-limited to roughly 15 requests per minute and 850 per hour (reset at midnight Pacific), with per-endpoint daily caps, so high-volume backfills must be throttled and batched. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and Jobvite without custom code.
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 427 integrations available for Google Cloud Spanner and Jobvite.