Overview
The Confirm and Rippling integration provides an automated and reliable way for organizations to sync their HRIS data from Rippling directly into Confirm. This enables a seamless experience for managing performance reviews, leveling frameworks, and organizational network analysis (ONA) cycles, without the need for manual HRIS data uploads.
Quickstart: Let's Get Started!
As a system administrator of Confirm and as an admin in Rippling, navigate to Confirm's Integrations page (https://app.confirm.com/integrations/). From there, select Rippling as your Human Resource Information System. Follow the on-screen prompts to walk through the process!
When Should Customers Use vs. Not Use the Integration?
Use the Integration When:
They are already using Rippling as their HRIS.
They want real-time or scheduled updates to their employee data in Confirm.
They have multiple admins managing HRIS data and want an automated sync.
Do Not Use the Integration When:
They do not use Rippling as their HRIS.
They prefer to manually upload CSVs or manage HR data separately from Confirm.
Their HRIS data does not need frequent updates in Confirm.
What Items Need to Be in Place Prior to the Installation?
The customer must be on a Merge.dev Professional or Enterprise plan.
They must have administrative access to their Rippling account.
They must provide necessary approval for Merge.dev to submit the application to Rippling.
If their organization uses Single Sign-On (SSO), they must ensure SSO settings are properly configured.
Data Flows
What Are the Distinct Data Flows?
Employee Data Sync – Syncs employee details, including name, email, job title, department, and manager.
Organizational Structure Sync – Updates reporting relationships, teams, and department changes.
Employment Status Sync – Captures new hires, terminations, and role changes.
Group and Location Sync – Ensures accurate office locations and team structures.
When and How Do Each of the Data Flows Trigger?
By default, data flows trigger on a scheduled basis (daily).
Changes in Rippling (e.g., new hires, role updates) automatically trigger updates via Merge.dev's webhook system.
How Can Customers Manually Trigger Data Flows?
Customers can force a sync from the Confirm admin dashboard.
Confirm can also manually refresh Merge.dev’s connection to pull new data immediately on the client's behalf.
FAQs
What Gotchas or Good-to-Knows Are There?
SSO Requirement – Rippling enforces SSO for third-party integrations, so this must be configured properly. Note that this does not have to be through Rippling's SSO.
Data Latency – There may be slight delays between a change in Rippling and when it appears in Confirm, depending on sync frequency.
What Considerations Are There for Customers to Make Decisions On?
Data Filtering: Customers should define which data fields that they find key to send to Confirm. Confirm only require the bare minimum to process ONA, so it is important to filter ahead of time which fields are not required. Let your Confirm representative know of this during technical implementation.
Sync Frequency: Remember that updates are done on a daily basis.
Custom Fields: If customers have unique HR fields in Rippling, they should confirm these are mapped correctly.
What Are Common Edge Cases That Customers Should Be Aware Of?
Missing Manager Relationships – If an employee does not have a manager assigned in Rippling, they may appear as an orphaned record in Confirm.
Terminated Employees Syncing – Customers must ensure that terminated employees do not stay active in Confirm after offboarding.
Multiple HRIS Systems – If a customer uses both Rippling and another HR system, or they have previously used manual CSV uploads into Confirm, they need to decide which should be the primary data source and determine the right migration plan prior to onboarding to Rippling completely.