Disclaimer
The integration was either created by Saviynt or by Saviynt community users . The integration is available “as is” and falls under standard connectors support for REST, SOAP, JDBC, LDAP, PowerShell, Jar and Saviynt Connector Framework.
Note: Contributor - Manju Kumari
Preface
This guide describes the integration between Saviynt Enterprise Identity Cloud (EIC) and Rippling.
Audience
This guide is intended for administrators and target system integration teams responsible for integrating and importing users from Rippling.
Introduction
Rippling is a software platform that provides a comprehensive solution for managing HR, payroll, benefits, and other employee-related processes. Rippling is designed to streamline and automate various HR functions, making it easier for businesses to manage their workforce.
Key features and capabilities of Rippling's HR system typically include:
Onboarding: Rippling allows businesses to efficiently onboard new employees by automating the collection of personal and employment information, setting up accounts and access to necessary tools, and ensuring compliance with employment regulations.
Payroll: The system facilitates payroll processing, including tax calculations, direct deposit, and compliance with payroll tax laws. It can also integrate with accounting and finance software to streamline financial processes.
Benefits Administration: Rippling helps manage employee benefits, including health insurance, retirement plans, and other perks. Employees can make benefit selections and changes through the platform.
Time and Attendance Tracking: The system may include time-tracking features to monitor employee work hours, attendance, and time-off requests.
Employee Self-Service: Employees can access their own profiles, update personal information, view pay stubs, and make changes to their benefits, reducing administrative work for HR departments.
Compliance and Reporting: Rippling typically offers tools to help businesses remain compliant with labor laws and regulations, as well as generate reports and analytics related to their workforce.
Integration: Rippling often integrates with other business software and tools, such as accounting software, customer relationship management (CRM) systems, and other HR-related platforms.
Rippling is known for its user-friendly interface and the ability to provide a holistic view of HR and employee management in one system. It's designed to help businesses of various sizes and industries streamline their HR and administrative processes.
The REST connector enables you to create an integration with Rippling for importing users to Saviynt EIC as an HR Identity source. For more information about different connectors in EIC, see Saviynt Enterprise Identity Cloud Connectors.
Note: This guide provides information about using the Rippling (REST-based) connector for performing operations listed in the Supported Features.
Supported Features
The Rippling integration supports the following features:
Supported Software Versions
Software | Version |
EIC | Release v4.5 and later |
Understanding the Integration between EIC and Rippling
You must create an integration between EIC and the collaboration platform hosted by the target application to perform import tasks. The following components are involved in the integration:
Rippling is the target application that is integrated with the EIC through the REST connector to import the users.
The REST connector enables communication between EIC and the target application. It provides a simplified integration mechanism where in some instances you only need to create a connection with minimal connectivity information for your target application. The REST connector is used for importing users through the REST APIs. For more information about creating a connection, see Creating a Connection.
Job Scheduler is a software component that executes a job based on the configured schedule to perform import operations from EIC. For more information about the jobs used by the connector in the Rippling integration.
Integration Architecture
EIC uses a REST connection for integrating with Rippling for importing users. The REST connection uses the REST protocol to communicate with the REST interface of Rippling.
The following diagram illustrates the connector architecture and communication with the target application.
Figure: Rippling Integration Architecture
Configuring a Connection
Prerequisites
Rippling customers access the Rippling API to retrieve and update information on their organization's behalf to build integrations with internal systems and applications.
If you are a Rippling customer, you will need to create an Access Token with defined scopes in order to access the Rippling API. The Access Token will only be able to access data that you specifically enable it to during the Access Token creation process. You will need to explicitly grant the Access Token access to data fields on behalf of your organization.
Note, Access Tokens are to be used only for internal integrations and are not meant for sharing to 3rd-parties.
Lastly, customer Access Tokens currently require the Rippling Access Token package. If you'd like to learn more, please reach out to your Rippling Account Representative.
For more information check this link.
Creating a Connection
Connection refers to the configuration setup for connecting EIC to target applications. For more information about the procedure to create a connection, see Creating a Connection.
Understanding the Configuration Parameters
While creating a connection, you must specify connection parameters that the connector uses to connect with the target application, define the type of operations to perform, the target application objects against which those operations are performed, and the frequency of performing them. In addition, you can view and edit attribute mappings between EIC and the target application.
Configuration Parameters for User Import
The connector uses the following parameters for creating a connection and for importing users from the target application:
Connection Parameters
Parameter | Description | Example Configuration | Mandatory? |
Connection Name | Specify the name to identify the connection. | - | Yes |
Connection Description | Specify the description for the connection. | - | No |
Connection Type | Select the connection type as REST. | - | Yes |
Default SAV Role | Specify this parameter to assign the SAV role for the connection. The SAV role is a role in EIC that assigns specific access to users. This parameter is valid only for importing users. Sample value: User assigned with the ROLE_ADMIN role, has access to all the sections of EIC. | - | No |
Email Template | Specify this parameter to select an email template for sending notifications. Email templates provide immediate trigger of emails to a user based on actions performed. Email informs user about the action performed and if critical, needs immediate action from the user. | - | No |
ConnectionJSON | Specify this parameter to create a connection.
| Use the following format to connect to the Rippling application: Refer to the Connection Package | Yes |
Import Parameters
Parameter | Description
| Recommended Configuration | Mandatory? |
UserImport JSON | Specify this parameter to import the users. | Use the following format to import users using the Rippling application: Refer to the Connection Package |
Yes |
Using the Rippling Integration
You can use the Rippling integration for performing user import after configuring it to meet your requirements.
Guidelines for Using the Integration
To configure import, map all Rippling attributes to EIC user attributes using UserImport JSON.
Configuring Import Operations
Full User import: When configuring the connection for the first time, first perform the full import to import all existing Users from the target application to EIC. To perform full import, the invoke API gets response from the target application and maps the attributes in the target application with attributes in EIC.
The import jobs are automatically created in EIC after you create a connection for the Rippling integration.
To import users:
Specify the connection and import parameters.
Note: Ensure that the connection type is selected as REST.Configure the User Import via a Connection (UserImportJob) to import users. For more information about creating jobs, see Data Jobs.
Troubleshooting
To troubleshoot common problems with connectors, answer frequently asked questions, and provide solutions to a few common issues you might encounter while configuring or working with connectors, see Common Troubleshooting Guide for Connectors.
To troubleshoot common problems or obtain answers to frequently asked questions for REST connectors, see the REST Connector Guide.
