Rippling
Visualize Rippling users, workers, and organizational structure, map workers to employees and managers, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
Installation
Configuration In Rippling
For this integration, you will need to generate an API Token in Rippling.
- Log in to your Rippling account.
- Navigate to Company Settings > Developer.
- Select the API Tokens tab.
- Create an API Token.
- Copy and securely save the generated API Token for use in JupiterOne.
As described in the Rippling documentation, API tokens use the permissions of the owner, so they should be treated as if they were a password. The user must have sufficient permissions to create an API token and access user and worker data. API tokens expire after 30 days of inactivity, or when the user is no longer active with the company. You will need to regenerate the token if it expires.
Configuration in JupiterOne
To complete the Rippling integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Rippling. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Rippling account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
The Rippling API Token generated for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Organization | rippling_organization | Account |
| User | rippling_user | User |
| Worker | rippling_worker | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
rippling_organization | HAS | rippling_user |
rippling_organization | HAS | rippling_worker |
rippling_user | IS | rippling_worker |
rippling_worker | MANAGES | rippling_worker |
Rippling Organization
rippling_organization inherits from Account
Rippling User
rippling_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
locale | string | ||
number | string | ||
preferredFamilyName | string | ||
preferredGivenName | string | ||
preferredLanguage | string | ||
timezone | string |
Rippling Worker
rippling_worker inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
country | string | ||
departmentId | string | ||
employmentTypeId | string | ||
endedOn | number | ||
isManager | boolean | ||
legalEntityId | string | ||
levelId | string | ||
overtimeExemption | string | ||
startedOn | number | ||
status | string | Any of: INITHIREDACCEPTEDACTIVETERMINATED | |
teamsId | string | ||
title | string | ||
titleEffectiveOn | number |