Skip to main content

Connect Employment Hero

Import your workers and their job history from Employment Hero, the HR and payroll platform. You authorise Oho to read from Employment Hero once, and Oho creates your workers and keeps them in step with Employment Hero on the schedule you choose — so people don't have to be added in two places.

Employment Hero is in Beta

This connector is still being rolled out. It imports workers and their job history, along with worker status and organisation details. If you hit something unexpected, contact support@weareoho.com.

What you'll end up with

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

Before you start​

You'll need:

  • Your people already recorded in Employment Hero, with the details you want in Oho — their names, contact details, and job history.
  • An Employment Hero admin account, or someone who has one, to register an app and authorise the connection in Step 1. This is done inside Employment Hero, not in Oho.

Step 1: Get your auth details​

What you'll need for this step

An admin login to Employment Hero, and the callback URL Oho shows you on the connection screen. The app is registered inside Employment Hero, not in Oho — if you don't administer it yourself, loop in whoever does before you start.

Employment Hero uses the Authorise with OAuth pattern: rather than generating a single key, you register Oho as an application in Employment Hero and then grant it access. Before you authorise, Employment Hero needs to know where to send you back — so you register Oho's callback URL against the app first.

  1. In Employment Hero's developer/API area, create a new app.
  2. Register Oho's callback URL against the app — Oho shows you the exact URL to paste on the connection screen in Step 2.
  3. Copy the app's Client ID and Client Secret.
  4. Make sure the app is allowed to read employees and their job history.
Technical detail: the OAuth exchange, scopes & callback

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

  • Consent flow. Oho uses the OAuth authorization_code grant. Clicking Connect redirects the admin's browser to Employment Hero's consent screen; approving it returns an authorisation code to Oho, which Oho exchanges for an access token and a refresh token server-to-server. Oho refreshes its own access, so the admin never manages a token by hand.
  • Callback / redirect URI. The redirect URI registered on the app must exactly match the callback URL Oho presents on the connection screen, or the consent is rejected with a redirect-mismatch error.
  • Scopes. Grant the app read access to employees and job history. [Eng to confirm the exact Employment Hero OAuth scope names Oho requests.]
  • Where secrets live. Oho stores the Client Secret and refresh token encrypted, referenced by a stored secret ref; the browser never handles them.
Treat the Client Secret like a password

The Client Secret and the resulting tokens grant ongoing access to worker PII for as long as they're valid. Never post them in email, chat, or a ticket, and revoke the app in Employment Hero if the connection is removed or someone with access to the secret leaves.

Expected outcome: Oho's callback URL is registered on the Employment Hero app, and you have the Client ID and Client Secret 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 Employment Hero from the list of sources.

Choosing a source in Oho

Paste your Client ID and Client Secret, then click Connect. Oho sends you to Employment Hero's sign-in page — sign in and approve the access Oho asks for. You're returned to Oho and the connection shows as authorised.

Expected outcome: the Employment Hero connection shows as authorised in Oho, and it moves you on to field mapping.

Step 3: Map your fields​

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

Employment Hero has its own names for things such as status, team, 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 Employment Hero integration reference for what this connector imports at a glance.

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

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

Expected outcome: every Employment Hero value the setup screen lists maps to its Oho equivalent, and each worker carries their Employment Hero 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 revoke Oho's access in Employment Hero afterwards if you don't intend to sync again.
  • Recurring — Oho re-reads Employment Hero on a schedule, so new starters, role changes, and terminations flow through automatically. The authorisation from Step 1 must stay in place for future runs — leave it authorised and Oho refreshes its own access.

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

Common questions​

The sync found nothing. Check the connection still shows as authorised — the most common cause is that Oho's access was revoked in Employment Hero, or the app lost read access to employees. Re-authorise from the integration's settings to fix it.

Consent failed with a redirect error. The callback URL registered on the app must exactly match the one Oho shows on the connection screen. Re-copy it from Oho into the app and try again.

Some workers didn't import. Oho matches returning workers on their Employment Hero employee ID (source.externalId). Check the match key and the values you mapped in 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.