OIIdentity and access management
Rippling to One Identity integration: employees and departments from Rippling in One Identity Manager
With an integration between Rippling and One Identity Manager, employees and contractors from Rippling are in fixed files every day with department path, entity, manager, entry date and exit date, which One Identity Manager's CSV connector reads. One Identity Manager uses them to create persons, calculate rights on department and entity, and process a departure on the end date from Rippling.
What the integration does
Organisations that use One Identity Manager and keep their HR in Rippling lack a connector for that source. Persons and departments are then loaded from a manual export, so a transfer or departure only reaches One Identity Manager with the next export.
- Rippling gets an API token on an admin account with read scopes only on workers, users, departments and entities.
- KoppelHet places a persons file and a departments file with fixed columns where the synchronisation server reads.
- The One Identity Manager administrator sets up the CSV connector with both files, the user ID as key and the department path as hierarchical sort order.
- After each change in Rippling KoppelHet updates that person's row; scheduled changes only on their effective date.
- A leaver stays in the file with the end date as exit date, until after the retention period.
What to watch for with Rippling and One Identity
- According to the release notes up to February 2026, One Identity's Starling Connect has HR connectors for Workday, SuccessFactors and Oracle Fusion, but not for Rippling. KoppelHet therefore delivers Rippling to One Identity Manager's CSV connector, in files that do not change shape when Rippling does.
- The CSV connector can use one column as hierarchical sort order, so parent departments are loaded first. Rippling gives the whole chain from top to bottom per department. KoppelHet builds the full path from it, so One Identity Manager does not load a new sub-department before its parent.
- Rippling creates a new worker under the same user on a rehire. The CSV connector has a setting for rows with the same key, from raising an error to taking the first or last. KoppelHet writes one row per user with the current worker, so that setting can stay on error and a duplicate row stands out instead of silently disappearing.
- With a file from another system, One Identity Manager cannot mark a person who disappears from the file as outstanding. KoppelHet therefore keeps a worker with status TERMINATED in the file, with the end date from Rippling in the exit date column.
- Rippling records for every change when it was entered and when it takes effect. KoppelHet only puts a transfer in the file on the effective date, so One Identity Manager does not grant the new department's rights weeks early.
- One Identity Manager reads dates according to the language set for the file. KoppelHet always writes entry and exit dates in the format that matches that setting, even if the entity in Rippling is in another country.
- Rippling states for an entity whether it runs through PEO, EOR or COR. KoppelHet fills the company column with the entity and puts the arrangement in a separate column, so company rules in One Identity Manager can treat people through an outside employer separately.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Why a second file for departments?
That way One Identity Manager first loads the departments in the right order, and then the persons attached to them.
Does pay data end up in the file?
No. The token has no scopes on compensation, and the file only contains the columns from the design.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Rippling through the REST API (rest.ripplingapis.com: /workers with expand user, manager, department and legal_entity; department_hierarchy, status, start_date, end_date, employment_type.type, legal_entity.management_type) and the Worker Changes API (applied_on and effective_on), plus webhooks. API token on an admin account with read scopes only.
- One Identity Manager reads two files in one system connection through the CSV connector (encoding, language for dates, header row, delimiter and text qualifier fixed), with PersonnelNumber as key column, Department.FullPath as hierarchical sort order and Uniqueness violation behavior set to Throw error. Synchronisation step with Data import, without MarkAsOutstanding; read-only access to the file.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in One Identity | Notes |
|---|---|---|
user_id | Sleutelkolom PersonnelNumber | |
Voornaam en achternaam | FirstName en LastName | |
work_email | Kolom werkadres | |
department_hierarchy | Department.FullPath | From top to bottom |
legal_entity_id | Kolom bedrijf | |
manager_id (via user) | Kolom leidinggevende | |
employment_type.type | Kolom soort medewerker | |
start_date | EntryDate | |
end_date bij TERMINATED | ExitDate |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension