Skip to main content

Connect JobAdder

Import applicants and their job history from JobAdder, the recruitment platform. You authorise Oho to read from JobAdder once, and as candidates move through your hiring they flow into Oho as applicants — ready to be sent a Recruitment Check and, once hired, promoted to workers.

Because you authorise Oho from inside your own JobAdder account, there's no file to build and no key to copy or store — you click Authorise, and Oho keeps syncing on the schedule you choose.

What you'll end up with

Your JobAdder candidates in Oho as applicants — each ready for a Recruitment Check and, once hired, promotable to a worker with their credentials carried across — kept in step with JobAdder, without re-entering anyone.

Before you start​

You'll need:

  • Your candidates already recorded in JobAdder, with the details you want in Oho — their names, contact details, and job history.
  • A JobAdder admin account, or someone who has one, to approve the connection in Step 1. You approve it inside JobAdder's own sign-in page, not in Oho.
  • A Connect (or Authorise) button on the JobAdder integration in Oho. If it isn't there yet, the JobAdder app hasn't been registered for your account — contact support@weareoho.com and we'll set it up with you.

Step 1: Get your auth details​

What you'll need for this step

A JobAdder login you can sign in with when Oho sends you to JobAdder's sign-in page. There's nothing to copy or paste — but the person who approves the connection needs the JobAdder access to read the candidates you want in Oho.

JobAdder uses the Authorise with OAuth pattern: rather than generating a key, you grant Oho access from inside your own JobAdder account. You start this in Oho in Step 2 — there's nothing to prepare in JobAdder beforehand. When you click Connect, Oho sends you to JobAdder's sign-in page (at id.jobadder.com), you sign in and approve the access Oho asks for, and you're returned to Oho with the connection authorised.

Because you sign in on JobAdder's own page, Oho never sees your JobAdder password — it only receives permission to read the candidates you approved, and can keep syncing without asking you to sign in again each time.

For the shared version of this pattern, see Get your auth details → Authorise with OAuth.

Technical detail: the OAuth exchange and where the secret lives

Hand these points to whoever administers JobAdder or handles Oho's setup — a non-technical admin can skip them.

  • Consent flow. Oho uses the OAuth authorization_code grant. Clicking Connect redirects the admin's browser to JobAdder's consent screen; approving it returns an authorisation code to Oho.
  • Server-side token exchange. Oho exchanges that code for tokens server-to-server at https://id.jobadder.com/connect/token — the browser never handles the exchange. Oho then holds the resulting tokens and refreshes them automatically, so the admin never sees or manages an access token.
  • Where the secret lives. OAuth needs the JobAdder app registered first, which produces a Client ID (not sensitive) and a Client Secret. Oho stores the Client Secret encrypted and reads it only at the moment of the sign-in exchange, referenced by a stored secret ref — it's never sent by the browser.
  • App registration. If the integration doesn't offer a Connect button, this registration hasn't been done for your account. Contact support@weareoho.com.

Expected outcome: you're ready to authorise JobAdder from Oho, and you know which JobAdder login has the access to approve it.

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 JobAdder from the list of sources.

Choosing JobAdder as the source

Click Connect (or Authorise). Oho sends you to JobAdder's own sign-in page — sign in and approve the access Oho asks for. You're returned to Oho and the connection shows as authorised.

Authorising Oho to read from JobAdder

Expected outcome: the JobAdder connection shows as authorised in Oho, and it moves you on to field mapping — you didn't have to copy any credential.

Step 3: Map your fields​

JobAdder has its own names for things — its own statuses and, where you use them, its own organisation or company values — so the setup screen asks you to line each one up with its Oho value before your first sync. What it asks you to map depends on what your JobAdder account sends; map every value it lists.

How Oho recognises a returning applicant. For ATS integrations like JobAdder, Oho matches on your upstream record ID, carried on source.externalId (the JobAdder candidate ID) — not on email. On each sync a match updates the existing applicant in place; no match creates a new one. You don't set this by hand; Oho reads it from JobAdder.

For what each field expects, which are required, and how re-syncs avoid duplicates, see the shared Map your fields reference, and the JobAdder integration reference for what this connector imports at a glance.

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

A JobAdder value you leave unmapped still imports as a record, but Oho can't place it correctly until it's mapped. If a new value appears in JobAdder later, Oho flags it so you can map it rather than letting it slip through.

Expected outcome: every JobAdder value the setup screen lists maps to its Oho equivalent, and each applicant carries their JobAdder candidate 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. Oho has your applicants after it runs. If you don't need it again, you can revoke Oho's access in JobAdder afterwards.
  • Recurring — Oho re-reads JobAdder on a schedule, so new candidates and their job history flow through automatically with nothing to re-enter. 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 it 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 candidates are in: they appear as applicants in Oho, ready to be sent a Recruitment Check and, once hired, promoted to workers with their credentials carried across.

The new JobAdder 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 candidates are in Oho as applicants, ready for a Recruitment Check.

What happens next​

  • Your candidates appear as applicants, ready to be screened with a Recruitment Check before they start.
  • When you take one on, promote them to a worker — the credentials they submitted carry across, so nothing has to be re-collected (see Applicants).
  • To keep those checks current once people are workers, add a verification source for the credential types you hold — synced credentials then verify at the register automatically.
  • If you set a recurring schedule, you don't re-import by hand — new candidates in JobAdder flow through 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 JobAdder, or the account that approved it lost access to the candidates. Re-authorise from the integration's settings to fix it.

I'm asked to sign in to JobAdder again. Oho refreshes its own access, so it shouldn't ask routinely. If it does, the authorisation has expired or been revoked in JobAdder — click Connect on the integration and approve it again.

Some applicants didn't import. Oho matches returning applicants on their JobAdder candidate ID (source.externalId) and sorts them using the values you mapped in Step 3. Check those values are mapped and that the affected candidates are visible to the account that authorised the connection.

There's no Connect button on the JobAdder integration. The JobAdder app hasn't been registered for your account yet. Contact support@weareoho.com and we'll set it up with you.

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.