How does the Rippling integration work?

Through SCIM, the standard for provisioning. OrgOrg issues a bearer token, and you add a custom SCIM integration in Rippling with the base URL https://orgorg.com/api/scim and the token. Rippling then pushes each hire, change, and departure to OrgOrg.

Does OrgOrg need a Rippling login?

No. Rippling calls OrgOrg; OrgOrg holds no Rippling credential and polls nothing. The only secret is the bearer token OrgOrg issued, which you can replace at any time.

What happens when someone leaves in Rippling?

Rippling deactivates the user over SCIM, and OrgOrg marks the person as departed, which removes them from the org chart, the rosters, and the groups that read the directory.

Can I use Rippling and Google Workspace together?

Yes. Rippling provisions the people and their manager lines; Google Workspace adds the calendar, the groups, and sign-in. A person who exists in both is one profile, matched by email.

Integration

Rippling integration: provisioning from Rippling to OrgOrg over SCIM

The Rippling integration provisions people from Rippling into OrgOrg over SCIM. A hire in Rippling gets a profile, a change updates it, and a departure deprovisions it, with the manager line and the departments along. One bearer token, a custom SCIM integration in Rippling, and the directory keeps itself current.

What connects

Provisioning: a new hire in Rippling gets an OrgOrg profile the day their account is created.
Updates: a title, a department, or a manager change in Rippling reaches the profile and the org chart.
Deprovisioning: a departure in Rippling removes the person from the org chart, the rosters, and the groups.
Standard SCIM: Rippling pushes the changes; OrgOrg polls nothing and holds no Rippling credential.

The apps that use it

How to set it up

Make the token in OrgOrg. In Settings, then Connectors, click Connect on the Rippling tile. OrgOrg shows a bearer token once, right after you connect: copy it then. If you lose it, click Make a new token.
Add a SCIM integration in Rippling. In Rippling, open Custom integrations, then Manage integrations, click Add Integration, and select SCIM.
Enter the details. The base URL is https://orgorg.com/api/scim, and the bearer token is the one OrgOrg generated for your org.
Save and activate. Review the details and click Save or Activate Integration. Rippling provisions the people it manages, and the directory fills.

The full guide, with screenshots, is at the help page.

The permissions it asks for

Permission	What OrgOrg does with it
A bearer token issued by OrgOrg	Rippling presents it on each SCIM call. Revoke it in OrgOrg to end the connection.
SCIM users and groups	Rippling creates, updates, and deactivates users, with their manager and department attributes.

See OrgOrg plansFree for teams of up to five, every integration included.

Frequently asked questions

How does the Rippling integration work?: Through SCIM, the standard for provisioning. OrgOrg issues a bearer token, and you add a custom SCIM integration in Rippling with the base URL https://orgorg.com/api/scim and the token. Rippling then pushes each hire, change, and departure to OrgOrg.
Does OrgOrg need a Rippling login?: No. Rippling calls OrgOrg; OrgOrg holds no Rippling credential and polls nothing. The only secret is the bearer token OrgOrg issued, which you can replace at any time.
What happens when someone leaves in Rippling?: Rippling deactivates the user over SCIM, and OrgOrg marks the person as departed, which removes them from the org chart, the rosters, and the groups that read the directory.
Can I use Rippling and Google Workspace together?: Yes. Rippling provisions the people and their manager lines; Google Workspace adds the calendar, the groups, and sign-in. A person who exists in both is one profile, matched by email.