Setting up your integration with Rippling
Please Note: If your organization uses Lattice's elevated design, you can find the updated navigation steps here.
Integrating Rippling with Lattice makes user management easier:
- We automatically sync the employees you select from Rippling to Lattice in almost real time.
- We mirror your reporting structure from Rippling.
- When users are added or removed from Rippling, we'll create them and deactivate them in Lattice with the click of a button.
To sync your Lattice account with Rippling, you must be an admin in both Lattice and Rippling.
What employee information will come over to Lattice from Rippling? If synced, Lattice will pull the following information from Rippling:
- Job Title
- Start Date
- Telephone Number
- Preferred Name
First, go to the Admin Settings page, then click on the Integrations sidebar tab. From the Integrations page, click on "Rippling" to open the configuration window.
From here, click "Go to Rippling" in order to establish the connection with an existing Rippling account.
After you click "Go to Rippling," enter your Lattice subdomain, as shown below:
What is my Lattice subdomain? You can find this in your URL when logged into Lattice (shown below). Your subdomain is the word before ".lattice.hq.com" (oftentimes your company name). In the case below, the subdomain is "lattice".
In order to install Lattice, you will have to grant Rippling access to the following information that will be pulled over:
Once you have authorized and established this connection, you will be able to choose which employees you would like to sync over to Lattice.
You will also be able to choose when employees get access to Lattice.
Lastly, you will be redirected to Lattice in order to finalize this installation.
As a reminder, once you have chosen who you would like to sync over, if you would like to make any changes to a users' employee information, you will want to make these changes in Rippling first, which will then sync these changes over to Lattice.
If you would like the information ported over from Rippling you have two options. The first is to use the "Sync" button to push information over manually at a time of your choosing. The second would be to toggle on the "Nightly Sync" option which would conduct a sync once a day every night.
Removing this Integration
If you would like to remove this integration, you will want to go to the Rippling App Directory, search for "Lattice", and disconnect Lattice from the Rippling side. You will then want to remove this integration by signing into Lattice, and then removing the integration from Lattice.
The Rippling Import Log
If you want to confirm that your Rippling integration has synced successfully, you can check in the integration log. Here's how you access your integration log:
Step 1: Navigate to your "Admin" panel.
Step 2: Under "People" on the left-hand side, click on "Import Log."
From here, you can view what synced successfully and what needs to be troubleshot. You can view what occurred within Lattice by looking at the "Description" column.
The Rippling import log has two event types, a "Rippling Webhook" and a "Rippling Sync". The "Rippling Webhook" is a characteric of real-time data transfers from Rippling to Lattice. For example, if you change an employee's email in Rippling, you may see a "Rippling Webhook" in your import log to reflect that real-time profile change. The "Rippling sync", on the other hand, is an indicator of a full import of all employee information in Rippling. This typically goes hand and hand with a manual sync.
Within the Rippling import log, there are three statuses:
The green checkmark specifies that the Rippling sync was successful, and all employee information was pulled into Lattice.
The orange exclamation point specifies that the Rippling sync was successful, but not all data was pulled over.
The red "X" indicates that the Rippling sync failed, and no users were updated.
If you want to view each status in more detail, click directly into event that you would like to view.
From here, you will have more of a high-level overview of what was updated or what failed to update within your Rippling sync.