Two-way sync
Changes in Google Cloud Platform or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Platform and Ukg Pro 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 Ukg Pro is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Google Cloud Platform next to everything else the company measures.
Stacksync syncs Employment Details, Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings) from Ukg Pro into tables in Google Cloud Platform continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Google Cloud Platform, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Ukg Pro where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Analysts combine Ukg Pro's workforce records with finance, product, or operational data already in Google Cloud Platform for reporting the HR system cannot produce on its own.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
A continuously synced copy in Google Cloud Platform gives you a durable, queryable record of how Ukg Pro's records change over time, for headcount planning and audit questions.
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 Platform objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Pub/Sub topics Event streams used to move change events between systems in near real time. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Pub/Sub topics is specific to Google Cloud Platform and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Firestore documents Document data read and written through the Firestore API for app-facing syncs. | Configuration Setup (Code Tables) Reference data such as jobs, locations, positions, earnings, and deduction codes; used to resolve and validate field values when mapping records during sync. | Firestore documents is specific to Google Cloud Platform and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Spanner tables is specific to Google Cloud Platform and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side. | |
| BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. | Employee (Person Details) Core worker record with demographics and identifiers; read by listing employee IDs then fetching each profile, and created on hire via the personnel/onboarding endpoints. | BigQuery datasets is specific to Google Cloud Platform and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | BigQuery tables is specific to Google Cloud Platform and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Cloud SQL databases Managed Postgres, MySQL, and SQL Server instances synced like ordinary relational databases. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Cloud SQL databases is specific to Google Cloud Platform and Job / Position History to Ukg Pro — 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.
DetectionGoogle Cloud Platform pushes changes as they happen — webhook events backed by change data capture. Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery.
DeliveryEach detected change is written to Ukg Pro through its API, with automatic retries and rate-limit backoff.
DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is applied to Google Cloud Platform 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 Platform–Ukg Pro connection.
Changes in Google Cloud Platform or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Platform or Ukg Pro 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 Platform or Ukg Pro record.
Track your Google Cloud Platform ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Platform and Ukg Pro.
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 Platform and Ukg Pro 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 Platform and Ukg Pro 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 Platform and Ukg Pro: authenticate both systems, choose the objects to sync (such as Google Cloud Platform's Pub/Sub topics and Firestore documents), 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 Google Cloud Platform and Ukg Pro: Headcount and cost joined with everything else; Fresh data instead of last night's load; Queryable history for planning and audit. Analysts combine Ukg Pro's workforce records with finance, product, or operational data already in Google Cloud Platform for reporting the HR system cannot produce on its own.
Google Cloud Platform: Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols. Authentication: IAM service accounts with OAuth 2.0 tokens. Ukg Pro: REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services. Authentication: Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint. Stacksync manages authentication, retries, and rate limits on both sides.
Google Cloud Platform: Authentication is uniform across services through IAM service accounts, so one credential model covers BigQuery, Cloud SQL, Cloud Storage, and Pub/Sub. Ukg Pro: Writes are modeled as HR events, not raw field edits: new hire (POST), termination (POST with a reason code that must match the tenant's configured reason table), and job or pay changes go through dedicated endpoints rather than a single PATCH. Stacksync's field mapping accounts for these differences between Google Cloud Platform and Ukg Pro 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 Google Cloud Platform and Ukg Pro 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 539 integrations available for Google Cloud Platform and Ukg Pro.