Humanforce
Import your workers and their job history from Humanforce, the workforce management platform. Connecting Humanforce keeps your Oho worker list in step with your system of record, so people don't have to be added in two places.
What it imports
Workers and their job history from Humanforce, fetched over its REST API, along with worker status and the organisation details Humanforce holds. Where Humanforce records qualifications, they map to Oho credential types so they can be checked against the register — matched on the qualification name, and, where your tenant records the real type in a qualification's notes instead, on keywords found in those notes.
What you'll need
An API key generated in Humanforce's API Key Management screen, granted access to at least Employees (and Roles, for job history). Oho connects with:
- The API key and API secret.
- Your tenant — taken from your Humanforce URL (for example
your-org.humanforce.com→ the tenant isyour-org).
Data the key can't access is simply skipped, so if you're unsure of scope, ask your Humanforce system administrator. There's no file to manage — Oho connects directly to the Humanforce API. See Get your auth details.
How it runs
Oho syncs from Humanforce on the schedule you set, so new starters, role changes, and terminations in Humanforce flow through to Oho on their own. Each run pulls only the employees edited since the last run — including qualification edits, which update the employee in Humanforce — so repeat syncs stay fast. The very first run reaches back a short window (about one scheduled interval by default) rather than loading your whole workforce; to bring across every existing worker in one go, turn on Force Full Sync under Advanced, run once, then turn it off again. Because the catch-up is edit-based, it can't see workers deleted in Humanforce, so a periodic Force Full Sync reconciles those too.