Two-way sync
Changes in Outreach or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Outreach 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.
Outreach runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Ukg Pro. Ukg Pro is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Tasks, Opportunities, Users, Mailboxes in Outreach with Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations in Ukg Pro field by field, in real time, and in both directions. You decide which system owns which fields, so Ukg Pro stays authoritative on roles and org structure while Outreach keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
When Ukg Pro marks a worker as departed, the matching user in Outreach is flagged or deactivated, so former employees do not keep CRM access after their last day.
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
A person recorded in Ukg Pro, such as a candidate or applicant, can create or update the matching contact in Outreach, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
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.
| Outreach objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Mailings Sent emails with engagement data, pulled for activity analytics | 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. | Mailings is specific to Outreach and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Calls Logged call records synced into engagement reporting | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Calls is specific to Outreach and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Tasks Rep action items mirrored between Outreach and the CRM | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Tasks is specific to Outreach and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Opportunities Deal records used to tie engagement to pipeline outcomes | 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. | Opportunities is specific to Outreach and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Users Seat holders used to resolve ownership on synced records | 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. | Users is specific to Outreach and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Mailboxes Connected sending accounts referenced when attributing outbound activity | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Mailboxes is specific to Outreach and Terminations 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.
DetectionOutreach notifies Stacksync of record changes through webhook events. Webhook subscriptions on resource create, update, and destroy events, plus polling.
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 written to Outreach through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Outreach–Ukg Pro connection.
Changes in Outreach or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Outreach 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 Outreach or Ukg Pro record.
Track your Outreach ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Outreach 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 Outreach 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 Outreach 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 Outreach and Ukg Pro: authenticate both systems, choose the objects to sync (such as Outreach's Mailings and Calls), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Outreach: Webhook subscriptions on resource create, update, and destroy events, plus polling. On Ukg Pro: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Outreach side: Tasks, Opportunities, Users, Mailboxes, plus custom fields where Outreach exposes them. On the Ukg Pro side: Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations. Stacksync auto-detects both schemas and converts types between the two systems.
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 Outreach and Ukg Pro: Deactivate access when someone leaves; One directory of people; Where Ukg Pro tracks people the business also engages: contacts stay in sync. When Ukg Pro marks a worker as departed, the matching user in Outreach is flagged or deactivated, so former employees do not keep CRM access after their last day.
Outreach: REST API conforming to the JSON:API specification. Authentication: OAuth 2.0. 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.
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 499 integrations available for Outreach and Ukg Pro.