Skip to content
Data warehouse ⇄ Human resources

Apache Kylin to Ukg Pro integration — real-time data sync

Keep Apache Kylin 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.

  • 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 Apache Kylin and Ukg Pro

Land the people and organization records from Ukg Pro in Apache Kylin as live tables for workforce reporting, without extract jobs, and write computed results back where Ukg Pro can use them.

Apache Kylin is a read-only source: Stacksync reads its data in real time and delivers it into Ukg Pro, so Ukg Pro always reflects the current state of Apache Kylin — without exports, scripts, or schedulers.

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 Apache Kylin next to everything else the company measures.

Common use cases

  • 01 Sync Kylin aggregates into a cloud warehouse to combine them with data Kylin does not cover.
  • 02 Trigger downstream syncs after segment build jobs complete so consumers only read refreshed data.
  • 03 Two-way sync of Employee and Job Details (position, department, supervisor, location, cost center) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR edits in UKG Pro.
  • 04 Push new hires (Employee, Employment, Job) into an ERP, IdP, or app database when onboarding completes so account, cost-center, and payroll setup fire on hire instead of manual report exports.

Common sync patterns

Queryable history for planning and audit

A continuously synced copy in Apache Kylin gives you a durable, queryable record of how Ukg Pro's records change over time, for headcount planning and audit questions.

Write-back of computed values

Segments, rollups, or risk flags computed in Apache Kylin sync back onto the matching records in Ukg Pro, 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 Ukg Pro arrive in Apache Kylin as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

What you can sync between Apache Kylin and Ukg Pro

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.

Apache Kylin objects Ukg Pro objects How this pairing syncs
Models Star-schema definitions over source tables that determine what can be queried. Compensation Details Effective-dated pay rate and salary; usually read into a warehouse for comp reporting and writable as new dated changes through the compensation endpoints. Models is specific to Apache Kylin and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side.
Cubes / Indexes Pre-computed aggregate structures that answer queries at low latency. Payroll (Pay Statements, Direct Deposit, Earnings) Pay statements, direct-deposit accounts, and earnings history; read-only pay data replicated into finance and warehouse systems for labor-cost reporting. Cubes / Indexes is specific to Apache Kylin and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side.
Source Tables Hive or other upstream tables that builds read from. Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. Source Tables is specific to Apache Kylin and Terminations to Ukg Pro — each maps to any object or custom field on the other side.
Segments Time-ranged build units that partition pre-computed data. 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. Segments is specific to Apache Kylin and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side.
Build Jobs Batch jobs that compute or refresh segments, monitored via the REST API. Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. Build Jobs is specific to Apache Kylin and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side.
Projects Top-level workspaces that group models, tables, and jobs. 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. Projects is specific to Apache Kylin and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side.

How changes propagate between Apache Kylin and Ukg Pro

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.

Apache Kylin Ukg Pro Interval-based propagation

DetectionStacksync polls Apache Kylin for changes on an incremental schedule, reading only records changed since the previous pass. Data freshness follows segment build and refresh jobs, so integrations poll query results.

DeliveryEach detected change is written to Ukg Pro through its API, with automatic retries and rate-limit backoff.

Ukg Pro Apache Kylin Sub-second propagation

DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.

DeliveryApache Kylin does not accept inbound record writes, so this direction carries requests rather than records: Apache Kylin's output flows back as field updates on the originating Ukg Pro records.

Rate-limit considerations

  • Apache Kylin: No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage.
  • Ukg Pro: An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
What ships with Apache Kylin ⇄ Ukg Pro

Connect Apache Kylin and Ukg Pro for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Kylin–Ukg Pro connection.

Real-time

Real-time sync

Changes in Apache Kylin or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Kylin or Ukg Pro 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 Apache Kylin or Ukg Pro record.

Observability

Monitoring

Track your Apache Kylin ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Kylin and Ukg Pro.

How the Apache Kylin and Ukg Pro connectors work

Apache Kylin

Integration surface
SQL over JDBC/ODBC plus a REST API for queries and administration
Authentication
Username/password (HTTP basic authentication on the REST API)
Change detection
Not applicable for row-level capture; data freshness follows segment build and refresh jobs, so integrations poll query results
Capabilities
read
Rate limits
No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage

Ukg Pro

Integration surface
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.
Change detection
No CDC stream. UKG Pro publishes Pro HCM Webhook Events for changes such as new hire, employee and job detail changes, termination, and PTO, which Stacksync subscribes to for near-real-time triggers; bulk and historical loads use paged reads with each service's modified-since filters.
Capabilities
read · write · webhooks
Rate limits
An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
Ukg Pro setup guide
How it works

How to connect Apache Kylin to Ukg Pro — 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 Apache Kylin 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apache Kylin connected
    Ukg Pro connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Kylin 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apache Kylin ⇄ Ukg Pro
    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
    Apache Kylin Ukg Pro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Kylin and Ukg Pro 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 392 integrations available for Apache Kylin and Ukg Pro.

Popular · 7 of 392
All Apache Kylin integrations All Ukg Pro integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own