Skip to main content

Connect UKG Pro

Import your workers and their current job from UKG Pro, the HR platform. You connect Oho to UKG Pro once, and Oho creates your workers and keeps them in step with UKG Pro on the schedule you choose — so people don't have to be added in two places.

UKG Pro is in Beta

This connector is still being rolled out. It imports workers and their current job, along with worker status and organisation details such as work location — but not full job history yet. If you hit something unexpected, contact support@weareoho.com.

What you'll end up with

Your UKG Pro workers in Oho — each ready for credentials to be added and checked — kept in step with UKG Pro, without maintaining two lists.

Before you start​

You'll need:

  • Your people already recorded in UKG Pro, with the details you want in Oho — their names, contact details, and current job.
  • A UKG Pro administrator, or someone who has one, to create a service account in Step 1. This connector needs admin access, so loop them in early.
  • Your tenant's Service URL — for example https://service4.ultipro.com.

Step 1: Get your auth details​

What you'll need for this step

An admin login to UKG Pro. The service account and API key are set up inside UKG Pro, not in Oho.

UKG Pro uses a service account plus a Customer API Key. Oho needs four values, so gather them together.

  1. In UKG Pro, go to System Configuration → Security → Service Account Administration.
  2. Create a service account and note its Username and Password.
  3. On the Web Services page, copy your Customer API Key (a short code) and confirm your Service URL.
  4. Give the service account the View role for the Personnel Integration and Employee Person Details web services.
Technical detail: the four required values & regions
  • All four values — Username, Password, Customer API Key, and Service URL — are required together. A missing Customer API Key is the most common reason a connection is rejected with no clear error.
  • Canadian tenants use service.ultipro.ca, and some EU tenants have a separate subdomain — use the Service URL for your tenant.
  • See the shared Get your auth details.
Treat these credentials like a password

The service account and API key grant access to worker PII. Never post them in email, chat, or a ticket, and reset them if the connection is removed.

Expected outcome: you have your UKG Pro service account username and password, Customer API Key, and Service URL ready to enter into Oho.

Step 2: Connect it in Oho​

In the left menu under Admin, click Integrations, then start a new integration.

The Integrations page in Oho

Pick UKG Pro from the list of sources.

Choosing UKG Pro as the source

Enter the Username, Password, Customer API Key, and Service URL, then click Next.

Entering the UKG Pro connection details in Oho

Expected outcome: Oho confirms it can reach UKG Pro and moves you on to field mapping.

Step 3: Map your fields​

Oho creates one worker per UKG Pro employee. It recognises a returning worker by their UKG employee ID, carried on source.externalId — so a re-sync updates the existing worker in place rather than creating a duplicate. Workers employed across more than one company in your tenant bring in a job for each.

UKG Pro has its own names for things such as status and work location; the setup screen asks you to line each one up with its Oho value before your first sync. For what each field expects, which are required, and how re-syncs avoid duplicates, see the shared Map your fields reference, and the UKG Pro integration reference for what this connector imports at a glance.

Map every value, or those records won't land where you expect

A UKG Pro value you leave unmapped still imports, but Oho can't place it correctly until it's mapped. If a new value appears in UKG Pro later, Oho flags it so you can map it.

Expected outcome: every UKG Pro value the setup screen lists maps to its Oho equivalent, and each worker carries their UKG employee ID as the match key.

Step 4: Set the schedule​

Choose how often the sync runs, then name it and save.

  • Once — a one-off load to get started.
  • Recurring — Oho re-reads UKG Pro on a schedule, so new starters, role changes, and terminations flow through automatically. The service account and API key must stay valid for future runs.

Setting the sync schedule

Expected outcome: the connection is saved and scheduled, and appears in your Integrations list.

Step 5: Run & verify your first sync​

Run it now with Save & Run, or wait for the first scheduled run. Once it's run, confirm your people are in: they appear under All Workers, and each credential you later add is checked against its official source (see One-off verification).

The new UKG Pro connection in your Integrations list, run history green

If the run didn't bring everyone in, check the run history and the Common questions below.

Expected outcome: your people are in Oho under All Workers, ready for credentials to be added and checked.

What happens next​

  • Your people appear under All Workers, ready for checks.
  • To keep those checks current, add a verification source for the credential types you hold — synced credentials then verify at the register automatically.
  • If recurring, you don't re-import by hand — change it in UKG Pro and Oho picks it up on the next run.

Common questions​

The sync found nothing, or was rejected with no clear reason. Confirm all four values are entered — a missing Customer API Key is the usual cause. Check the Service URL matches your tenant's region.

Some workers didn't import. Check the match key and required fields from Step 3, and confirm the service account has the View role for the Personnel Integration and Employee Person Details web services.

I don't see Integrations. This is an admin area — if it's not in your menu, ask an admin in your organisation, or contact support@weareoho.com.