Skip to content
Database ⇄ Human resources

Google Cloud Spanner to Ukg Ready integration — real-time, two-way sync

Keep Google Cloud Spanner and Ukg Ready 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 Google Cloud Spanner and Ukg Ready

Put your workforce data where your apps can reach it: Google Cloud Spanner and Ukg Ready share the same people, positions, and org structure in real time.

Ukg Ready 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: Reports (Report-as-a-Service), Employees, Employment / Positions, Compensation in Ukg Ready need to exist as queryable Rows, Interleaved tables, Secondary indexes, Change streams 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 Rows, Interleaved tables, Secondary indexes, Change streams in Google Cloud Spanner with Reports (Report-as-a-Service), Employees, Employment / Positions, Compensation in Ukg Ready field by field, in real time. You decide which system owns which fields — Ukg Ready 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.

Common use cases

  • 01 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • 02 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • 03 Mirror Cost Centers/Groups and Compensation into finance and planning systems for headcount and budget reconciliation.
  • 04 Two-way sync Employees and Employment/Position records with an operational Postgres database so internal apps and IT provisioning read job title, department, and status in SQL while HR edits in UKG Ready.

Common sync patterns

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Reports (Report-as-a-Service), Employees, Employment / Positions, Compensation replicate into Google Cloud Spanner where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Ukg Ready stay consistent in Google Cloud Spanner, so hierarchy-driven logic and permissions don't drift.

What you can sync between Google Cloud Spanner and Ukg Ready

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 Ukg Ready objects How this pairing syncs
Secondary indexes Used to make incremental read queries efficient on non-key columns. Payroll (Earnings / Deductions / Employee Payroll Runs) Earnings and deductions can be imported into pay runs; Employee Payroll Runs (gross, net, taxes) read back for GL posting and analytics. Secondary indexes is specific to Google Cloud Spanner and Payroll (Earnings / Deductions / Employee Payroll Runs) to Ukg Ready — 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. Benefits Plan enrollments, coverage tiers, contributions, and effective dates; typically read into benefits or finance systems. Change streams is specific to Google Cloud Spanner and Benefits to Ukg Ready — each maps to any object or custom field on the other side.
Views Read-only projections useful for shaping data before it leaves Spanner. Cost Centers / Groups Departments, locations, and hierarchy used as org structure; read to align headcount and budget models across systems. Views is specific to Google Cloud Spanner and Cost Centers / Groups to Ukg Ready — each maps to any object or custom field on the other side.
Databases Top-level containers that scope schema and sync configuration. Reports (Report-as-a-Service) Scheduled IBM Cognos extracts used for bulk historical pulls that the per-employee REST endpoints are not built for. Databases is specific to Google Cloud Spanner and Reports (Report-as-a-Service) to Ukg Ready — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. Employees Core person records (demographics, contact info, status, work location); synced two-way and mapped to HRIS or person tables in a database. Tables is specific to Google Cloud Spanner and Employees to Ukg Ready — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. Employment / Positions Job title, department, employment type, hire and termination dates; read for org modeling and written when roles change. Rows is specific to Google Cloud Spanner and Employment / Positions to Ukg Ready — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and Ukg Ready

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.

Google Cloud Spanner Ukg Ready Sub-second propagation

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

Ukg Ready Google Cloud Spanner Sub-second propagation

DetectionUkg Ready notifies Stacksync of record changes through webhook events. UKG Webhooks for select events (employee.created, employee.updated, account/org changes) with HMAC signing.

DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • Ukg Ready: Rate limits apply over roughly a 1-minute window and return HTTP 429 when exceeded (back off / exponential retry); UKG Webhooks run on a tiered quota with a free tier around 10,000 event notifications per month and 14-day event retention.
What ships with Google Cloud Spanner ⇄ Ukg Ready

Connect Google Cloud Spanner and Ukg Ready for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Ukg Ready connection.

Real-time

Two-way sync

Changes in Google Cloud Spanner or Ukg Ready instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Spanner or Ukg Ready 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 Google Cloud Spanner or Ukg Ready record.

Observability

Monitoring

Track your Google Cloud Spanner ⇄ Ukg Ready sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Ukg Ready.

How the Google Cloud Spanner and Ukg Ready connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

Ukg Ready

Integration surface
UKG Ready REST API (v1/v2) plus the Import Tool (XML transactions) and Report-as-a-Service (IBM Cognos); a legacy SOAP API also exists
Authentication
A 7-digit company short name, a Web API key (Company Setup > Login Config), and a dedicated API service-account user (username/password) are exchanged for a session Bearer token sent on every request; Onboarding/Recruiting endpoints use a separate authorization token
Change detection
UKG Webhooks for select events (employee.created, employee.updated, account/org changes) with HMAC signing; broad change capture via polling REST endpoints with date filters or scheduled Report-as-a-Service extracts
Capabilities
read · write · webhooks
Rate limits
Rate limits apply over roughly a 1-minute window and return HTTP 429 when exceeded (back off / exponential retry); UKG Webhooks run on a tiered quota with a free tier around 10,000 event notifications per month and 14-day event retention
How it works

How to connect Google Cloud Spanner to Ukg Ready — 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 Google Cloud Spanner and Ukg Ready 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
    Google Cloud Spanner connected
    Ukg Ready connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Spanner and Ukg Ready 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 · Google Cloud Spanner ⇄ Ukg Ready
    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
    Google Cloud Spanner Ukg Ready
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Google Cloud Spanner and Ukg Ready 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:

Coworkers laughing in front of a laptop in a casual office setting

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