Skip to main content

Connect Humanforce

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

What you'll end up with

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

Before you start​

You'll need:

  • Your people already recorded in Humanforce, with the details you want in Oho — their names, contact details, and job history.
  • A Humanforce admin account, or someone who has one, to generate an API key in Step 1.
  • Your Humanforce tenant — taken from your Humanforce URL (for example your-org.humanforce.com, where the tenant is your-org).

Step 1: Get your auth details​

What you'll need for this step

An admin login to Humanforce. The API key is generated inside Humanforce, not in Oho.

Humanforce uses the API key pattern: you generate a key and secret in Humanforce's API Key Management screen, and Oho uses them to read worker and job data over the REST API.

  1. In Humanforce, open the API Key Management screen and generate a new API key and secret.
  2. Make sure the key is granted access to the data you want to import — at minimum Employees (and Roles, for job history). If you're not sure, ask your Humanforce system administrator; data the key can't access is simply skipped.
  3. Copy your tenant from your Humanforce URL (for example your-org.humanforce.com → the tenant is your-org).
Technical detail: authentication & permissions

Hand these points to whoever administers Humanforce — a non-technical admin can skip them.

  • Auth mechanism. Oho authenticates to the Humanforce REST API with the API key and secret. [Eng to confirm the exact header/token scheme.]
  • Permissions. The key reads only what it's granted — grant at least Employees (and Roles for job history). Data the key can't access is skipped rather than erroring, so an incomplete import usually means an under-scoped key.
  • Where secrets live. Oho stores the API secret encrypted, referenced by a stored secret ref.
Treat the API secret like a password

The API secret grants ongoing access to worker PII for as long as it's valid. Never post it in email, chat, or a ticket, and regenerate it in Humanforce if the connection is removed or someone with access to it leaves.

Expected outcome: you have your Humanforce API key, API secret, and tenant copied, ready to paste 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 Humanforce from the list of sources.

Choosing a source in Oho

Paste your API key, API secret, and tenant, then click Next.

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

Step 3: Map your fields​

Oho creates one worker per Humanforce employee. It recognises a returning worker by their Humanforce employee ID, carried on source.externalId — so a re-sync updates the existing worker in place rather than creating a duplicate.

Humanforce has its own names for things such as status, location, and role; 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 Humanforce integration reference for what this connector imports at a glance.

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

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

Expected outcome: every Humanforce value the setup screen lists maps to its Oho equivalent, and each worker carries their Humanforce 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. You can remove the API key in Humanforce afterwards if you don't intend to sync again.
  • Recurring — Oho re-reads Humanforce on a schedule, so new starters, role changes, and terminations flow through automatically. The API key must stay active and keep its access 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 connection in your Integrations list

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 Humanforce and Oho picks it up on the next run.

Common questions​

The sync found nothing. The API key most likely lacks access to Employees — grant it, then run again. Also confirm the key, secret, and tenant were copied correctly.

Some workers or their job history didn't import. Data the key can't access is skipped — check the key is granted Employees and Roles. Oho matches returning workers on their Humanforce employee ID (source.externalId), so also confirm the match key and required fields from Step 3.

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.