Skip to content
Database ⇄ Human resources

Reltio to Ukg Ready integration — real-time, two-way sync

Keep Reltio 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 Reltio and Ukg Ready

Put your workforce data where your apps can reach it: Reltio 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. Reltio is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Benefits, Cost Centers / Groups, Reports (Report-as-a-Service), Employees in Ukg Ready need to exist as queryable Crosswalks, Interactions, Matches (Potential Matches), Activity Log in Reltio 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 Crosswalks, Interactions, Matches (Potential Matches), Activity Log in Reltio with Benefits, Cost Centers / Groups, Reports (Report-as-a-Service), Employees 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 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 02 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
  • 03 Create new-hire Employee records in UKG Ready from an ATS or onboarding workflow, including position, cost center, and compensation fields.
  • 04 Feed Timesheet Entries and Accruals/Time Off into a data warehouse for labor-cost, overtime, and PTO-liability reporting.

Common sync patterns

Mirror people records into the database

Records maintained in Ukg Ready land as queryable Crosswalks, Interactions, Matches (Potential Matches), Activity Log in Reltio, so internal apps and dashboards read live data instead of a periodic export.

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

Benefits, Cost Centers / Groups, Reports (Report-as-a-Service), Employees replicate into Reltio where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

What you can sync between Reltio 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.

Reltio objects Ukg Ready objects How this pairing syncs
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Reports (Report-as-a-Service) Scheduled IBM Cognos extracts used for bulk historical pulls that the per-employee REST endpoints are not built for. Reference Data (RDM) is specific to Reltio and Reports (Report-as-a-Service) to Ukg Ready — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Employees Core person records (demographics, contact info, status, work location); synced two-way and mapped to HRIS or person tables in a database. Entities is specific to Reltio and Employees to Ukg Ready — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Employment / Positions Job title, department, employment type, hire and termination dates; read for org modeling and written when roles change. Relations is specific to Reltio and Employment / Positions to Ukg Ready — each maps to any object or custom field on the other side.
Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Compensation Salary or hourly rate, pay frequency, and FLSA status; often mastered elsewhere and written onto the employee record, or read into finance. Crosswalks is specific to Reltio and Compensation to Ukg Ready — each maps to any object or custom field on the other side.
Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Timesheet Entries Time-and-attendance punches, hours worked, and breaks; written from external time systems and read into warehouses for labor-cost reporting. Interactions is specific to Reltio and Timesheet Entries to Ukg Ready — each maps to any object or custom field on the other side.
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Accruals / Time Off PTO balances, requests, and approver status; read for liability reporting and requests can be created against employee records. Matches (Potential Matches) is specific to Reltio and Accruals / Time Off to Ukg Ready — each maps to any object or custom field on the other side.

How changes propagate between Reltio 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.

Reltio Ukg Ready Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

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

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • 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 Reltio ⇄ Ukg Ready

Connect Reltio and Ukg Ready for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Reltio ⇄ 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 Reltio and Ukg Ready.

How the Reltio and Ukg Ready connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

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 Reltio 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 Reltio 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
    Reltio connected
    Ukg Ready connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio 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 · Reltio ⇄ 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
    Reltio Ukg Ready
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Reltio 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.

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 431 integrations available for Reltio and Ukg Ready.

Popular · 7 of 431
All Reltio integrations All Ukg Ready 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