Create a Rippling API token that can read your employees, enter it in this setup, and we read your employee list every few minutes.
The values in braces, such as {acs_url}, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.
-
Choose directory sync from the HRIS
Section titled “Choose directory sync from the HRIS”Use this guide when you want this app to read people straight from Rippling’s employee records. If you manage app access with Rippling’s SCIM provisioning instead, follow the Rippling SCIM guide.
-
Create an API token
Section titled “Create an API token”As a Rippling admin, create an API token in Rippling’s API access settings with read access to employee records. Copy the token when it is shown.
-
Enter the credentials in this setup
Section titled “Enter the credentials in this setup”Paste the API token in this setup. We check it with one read from Rippling before saving it encrypted; if the check fails, nothing is saved.
-
Wait for the first sync
Section titled “Wait for the first sync”The first sync starts right away. After that we read Rippling every 5 minutes; after a failure we wait longer between tries, up to an hour.
-
Know who is synced
Section titled “Know who is synced”We read the full employee list on every sync. People Rippling no longer returns are removed from the directory, and changes to names, titles or departments are updated.
-
Replace the credentials when needed
Section titled “Replace the credentials when needed”If you revoke the token or it expires, syncs fail and this setup shows the error. Create a new token and enter it here again.
-
Check the first users
Section titled “Check the first users”After the first sync, check in this setup that the people you expect are listed with the right names and emails.
Sources
Section titled “Sources”- Rippling developer documentation, read on 2026-10-29