Rippling
Connect Rippling to Ploy to bring your workers into Ploy as an HR source of truth, see who has access to Rippling, see who is in each Rippling supergroup, and add people to or remove them from supergroups from Ploy.
This integration is in beta
The Rippling integration is in beta. It was built from Rippling's API documentation and has not yet been proven against a live Rippling company. It works the same way as any other integration, but you may find rough edges. If something looks wrong, tell us and we will fix it.
Before you start
You need:
A Rippling account with administrator access. A Rippling API token acts with the permissions of the administrator who creates it, so it must belong to someone who can see every worker and manage supergroups.
Access to Tools, then Developer, then API Tokens in Rippling.
Step 1: Accept the beta terms
When you open the Rippling setup in Ploy, the first step is a checkbox asking you to accept the beta terms. While the integration is in beta, Ploy records a redacted copy of any error Rippling returns so we can fix problems quickly. Redacted means personal details such as names, email addresses and tokens are removed before anything is stored. Tick the box to continue.
Step 2: Create a Rippling API token
Sign in to Rippling as an administrator.
Go to Tools, then Developer, then API Tokens, and create a new token.
Give the token a name you will recognise, such as Ploy.
Give it read access to workers, users, departments and supergroups.
If you want Ploy to add people to and remove them from supergroups, also give it write access to supergroups.
Copy the token. You will paste it into Ploy in the next step.
Rippling stops a token working if it goes unused for 30 days or if the administrator who created it leaves the company, and a token cannot be moved to another administrator. Ploy uses the token every hour while the integration is connected.
Step 3: Connect Rippling in Ploy
In Ploy, go to Integrations and choose Rippling.
Paste the API token.
Select Test to check the connection, then save.
Ploy reads your workers straight away and then every hour, and your supergroups every six hours.
What Ploy reads
Workers: every worker, with name, work email, job title, department, manager and start and end dates.
Access to Rippling: who can use Rippling. Active workers have access. Workers who have been hired but have not started yet show as pending. Terminated workers show as no longer having access from the day after their end date.
Supergroups: every supergroup, and who is in each one. Groups Rippling hides from its own admin console are not read.
Ploy does not read social security or other national ID numbers, dates of birth, gender, race, ethnicity, citizenship, compensation or personal email addresses.
What Ploy can change
Add a person to a supergroup. Ploy adds them as a manual inclusion, so they are in the group whatever its rule says, and removes any manual exclusion Ploy or someone else set for them.
Remove a person from a supergroup. Ploy removes any manual inclusion and adds a manual exclusion, so they are out of the group whatever its rule says.
You will see these as inclusions and exclusions on the group in Rippling. Rippling may refuse changes to groups that are read-only or managed by an app.
Rippling's API cannot create, update, terminate or delete workers, so do those in Rippling.
Troubleshooting
Rippling rejected that API token: the token was not copied in full, has been revoked, went unused for 30 days, or its owner has left. Create a new one and paste it again.
That API token cannot read workers: the token is missing read access to workers, users or departments. Edit the token's access in Rippling, or create a new one.
Rippling refused the change: the token is missing write access to supergroups, or the group cannot be changed by hand.