Skip to content

Rippling

Rippling

Connect Rippling and your people are kept in step with it: an account from their start date, deactivated — every session signed out — at the end of their last day, and each department a group your administrators can map to roles.

In Rippling

In the portal, open Directory sync, choose Using an HR system?, and pick Rippling. Then, in Rippling:

  1. Sign in as an administrator whose permission profile covers the entire company — the token sees exactly what its creator sees. A dedicated service administrator is best: Rippling revokes a token when its creator leaves.
  2. Go to Tools → Developer → API Tokens and choose Create API token. Name it "Cbox ID".
  3. Grant the read scopes workers.read, users.read and departments.read, and nothing else.
  4. Copy the token and paste it here. Rippling also revokes a token that goes unused for 30 days, which a scheduled sync never lets happen.

What to paste into the portal

Field Where it comes from
API token (secret) Created under Tools → Developer → API Tokens. Shown once.

The portal checks these with Rippling before anything is stored, and never shows a secret again.

What happens next

  • The first sync starts straight away and runs in the background; the portal shows how it went.
  • After that, Rippling is asked for what changed, about every hour, with a full sync at least once a day.
  • A person whose termination date has passed loses access at the end of that day, even if their status has not been updated yet. People on leave keep their account.
  • People who left before the connection was made, and people who have not started yet, get no account.
  • A person with no work email, or whose email already belongs to an account that is not linked to this connection, is listed as not synced — by their Rippling employee ID — and nobody else is held up.
  • If a sync would suddenly deactivate more than half of your people, it deactivates nobody and says why: that is almost always permissions that changed in Rippling, not a mass layoff.

Rippling's own guide: https://developer.rippling.com/documentation/rest-api/essentials/api-tokens.