Skip to main content

Connect Rippling

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

Rippling is in Beta

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

What you'll end up with

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

Before you start​

You'll need:

  • Your people already recorded in Rippling, with the details you want in Oho — their names, contact details, and current job.
  • A Rippling admin account, or someone who has one, to create an API token in Step 1.

Step 1: Get your auth details​

What you'll need for this step

An admin login to Rippling. The API token is created inside Rippling, not in Oho.

Rippling uses the API key pattern — you create a token in Rippling and paste it into Oho.

  1. In Rippling, open the API Tokens app (under the admin console).
  2. Create a token named Oho integration.
  3. Copy the token — it's shown once.
Technical detail: token, permissions & scopes
  • Oho authenticates with a Bearer token in the Authorization header.
  • The token inherits the permissions of the person who created it, so make sure it can read workers (and, optionally, users and departments for fuller detail).
  • See the shared Get your auth details → API key or token.
Treat the token like a password

The token grants ongoing access to worker PII for as long as it's valid. Never post it in email, chat, or a ticket, and rotate it periodically — and whenever someone with access to it leaves.

Expected outcome: you have your Rippling API token 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 Rippling from the list of sources.

Choosing Rippling as the source

Paste your API token, then click Next.

Entering the Rippling connection details in Oho

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

Step 3: Map your fields​

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

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

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

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

Expected outcome: every Rippling value the setup screen lists maps to its Oho equivalent, and each worker carries their Rippling 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 the token in Rippling afterwards if you don't intend to sync again.
  • Recurring — Oho re-reads Rippling on a schedule, so new starters, role changes, and terminations flow through automatically. The token 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 Rippling 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 Rippling and Oho picks it up on the next run.

Common questions​

The sync found nothing. The token may have been revoked or created without permission to read workers. Create a fresh token from an admin account with worker access.

Some workers didn't import. Check the match key and required fields from Step 3 — a worker missing a required value won't import until it's populated in Rippling. You can also limit the import to a particular status (for example, active only) in the integration's advanced settings.

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.