Skip to content
Database ⇄ Human resources

Neo4j to Ukg Pro integration — real-time, two-way sync

Keep Neo4j 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 Neo4j and Ukg Pro

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

Ukg Pro is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Neo4j is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details in Ukg Pro need to exist as queryable Users & Roles, Nodes, Relationships, Properties in Neo4j 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 Users & Roles, Nodes, Relationships, Properties in Neo4j with Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details in Ukg Pro field by field, in real time. You decide which system owns which fields — Ukg Pro 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 Write computed relationship scores (fraud, influence, similarity) back to operational systems.
  • 02 Keep a customer-360 graph continuously updated from ERP, CRM, and support sources.
  • 03 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.
  • 04 Replicate Compensation and pay-statement / earnings history into a warehouse for headcount, labor-cost, and payroll reporting without manual BI exports.

Common sync patterns

Mirror people records into the database

Records maintained in Ukg Pro land as queryable Users & Roles, Nodes, Relationships, Properties in Neo4j, 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

Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details replicate into Neo4j where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

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

Neo4j objects Ukg Pro objects How this pairing syncs
Relationships Typed, directed edges that carry the connections syncs exist to model. Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. Relationships is specific to Neo4j and Employment Details to Ukg Pro — each maps to any object or custom field on the other side.
Properties Key-value attributes on both nodes and relationships, mapped from source fields. Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. Properties is specific to Neo4j and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side.
Labels Node type markers used to map source tables or objects onto the graph. 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. Labels is specific to Neo4j and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side.
Indexes & Constraints Uniqueness constraints and indexes that make MERGE-based upserts reliable and fast. 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. Indexes & Constraints is specific to Neo4j and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side.
Databases Named databases in a single instance that scope multi-tenant or multi-domain syncs. Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. Databases is specific to Neo4j and Terminations to Ukg Pro — each maps to any object or custom field on the other side.
Users & Roles Security principals controlling what an integration credential can query or modify. 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. Users & Roles is specific to Neo4j and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side.

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

Neo4j Ukg Pro Sub-second propagation

DetectionChanges in Neo4j are captured at the source via change data capture — no polling loop against its API. Neo4j Change Data Capture on Enterprise and Aura streams graph changes.

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

Ukg Pro Neo4j Sub-second propagation

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

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

Rate-limit considerations

  • 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 Neo4j ⇄ Ukg Pro

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Neo4j ⇄ 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 Neo4j and Ukg Pro.

How the Neo4j and Ukg Pro connectors work

Neo4j

Integration surface
Bolt binary protocol with Cypher via official drivers, plus an HTTP query API
Authentication
Username/password (basic auth); enterprise deployments add SSO options
Change detection
Neo4j Change Data Capture on Enterprise and Aura streams graph changes; otherwise Cypher polling on timestamp properties
Capabilities
read · write · CDC

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

    Choose tables

    Pick the Neo4j 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 · Neo4j ⇄ 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
    Neo4j Ukg Pro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

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

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:

Related integrations

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

Popular · 8 of 517
Coworkers laughing in front of a laptop in a casual office setting

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