Rippling HR Source
nexusID integrates with Rippling as an authoritative HR source for the joiner/mover/leaver (JML) lifecycle, pulling the worker directory over the Rippling API (Bearer auth).
Configure (admin console — recommended)
Add it as an HR_SOURCE integration (provider Rippling) in Admin → Integrations; see
HR Sources for the model. Config fields:
| Field | Notes |
|---|---|
accessToken | Rippling API key / OAuth Bearer token (encrypted at rest) |
baseUrl | default https://rest.ripplingapis.com |
workersPath | default /workers |
recordsPath | dot-path to the worker array; blank if the body is the array |
nexusID calls GET {workersPath} with Authorization: Bearer <token>, paginating with
limit/offset.
Field mapping (worker → identity)
| Canonical | Default Rippling field |
|---|---|
employeeId (required) | id |
email | workEmail |
firstName / lastName | firstName / lastName |
jobTitle | title |
department | department |
status | roleState (ACTIVE / TERMINATED / …) |
A leaver is detected when status resolves to TERMINATED / TERMED / INACTIVE.
Where it lives in code
- Provider:
modules/integration/hr-rippling/.../RipplingProvider.kt(+RipplingApiClient.kt) - DB sync:
HrSourceSyncService(no per-vendor connector needed)