> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/hris/rippling.md).

# Rippling

Connect Rippling to Siit to sync your workforce and lifecycle events. Rippling is often a single source of truth for HR, IT, and payroll.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FWhYS6GYoOM9f59Ff1u9P%2FSiit_Rippling.jpg?alt=media&amp;token=e55c7599-bc29-46fc-a1b1-d51933304f45" alt=""><figcaption></figcaption></figure>

Rippling's directory and lifecycle events drive Day-1 onboarding, offboarding, and access workflows, with Rippling-managed roles flowing into Siit's workflow conditions.

### What you get

* **Live People directory** — Rippling employees and contractors appear in Siit with their full profile.
* **Lifecycle triggers** — Start date, End date, Work anniversary, and Birthday flow into Siit as workflow triggers.
* **Manager resolution** — Rippling's reporting structure drives auto‑selected approvers.
* **Department, team, and location hierarchies** — preserved in Siit for routing, audiences, and reporting.
* **Multi‑entity support** — for customers with multiple Rippling legal entities, each worker's entity is attached.

### What syncs from Rippling

| Category        | Fields                                                                         |
| --------------- | ------------------------------------------------------------------------------ |
| Identity        | Preferred name, legal name, work email, Rippling Employee ID                   |
| Role            | Job title, job level, department, team                                         |
| Org structure   | Manager, work location, legal entity, cost center                              |
| Employment      | Employment type (Employee / Contractor), status (active, on leave, terminated) |
| Lifecycle dates | Start date, termination date, date of birth                                    |
| Custom          | Selected custom fields (Custom Field Groups you enable in Rippling)            |

Work email is the canonical identifier.

### Before you connect

* You'll need **Rippling admin access** with permission to install third‑party apps.
* Siit is installed via Rippling's app directory — your Rippling admin policy must allow this.
* Decide which Rippling role / Custom Field Groups Siit should be able to read.

### Connect Rippling

1. In Siit, go to **Settings → Workspace → Integration library**.
2. Find **Rippling** in the HRIS section and click **Connect**. You'll be redirected to Rippling.
3. Sign in to Rippling if prompted.
4. Review and approve the requested data scopes:
   * Read employees and contractors
   * Read departments, teams, work locations, legal entities
   * Read custom fields (if enabled)
5. Confirm the install. Rippling redirects you back to Siit.
6. Siit runs an initial import and shows a preview.
7. Review the field mapping and click **Finish setup**.

> **Tip** — If you manage access strictly via Rippling Custom Roles, check with your Rippling admin that the admin performing the install has access to every employee you want synced. The scope is inherited at install time.

### After the connection

* **Check your People list** in Siit — confirm the count matches Rippling's active employees + contractors.
* **Set source of truth** — in **Settings → Context management → People fields**, pick Rippling for HR fields (department, manager, legal entity, employment type).
* **Map custom fields** — in **Settings → Workspace → Integration library → Rippling**, select which custom fields you want in Siit.
* **Build workflows** — Rippling customers often want onboarding and offboarding workflows that pair HR data (Rippling) with provisioning steps (IdP, apps).

### Sync frequency

Rippling data refreshes automatically every few hours. Force a manual sync from **Settings → Workspace → Integration library → Rippling → Synchronize**. The action hides itself while a sync is running and for 15 minutes after the last one.

### Common workflows

**Day‑1 onboarding.** *Trigger: Start date. Actions: create IdP account, assign department‑specific app bundle, ship equipment, notify manager.*

**Offboarding on termination.** *Trigger: End date. Actions: revoke sessions, remove app access, create equipment pickup request, DM manager with handover reminder.*

**Department‑aware routing.** *Condition: Requester's department = Engineering → Route to IT Ops; else → Route to general helpdesk.*

**Contractor onboarding.** *Trigger: Start date, Condition: Employment Type = Contractor. Actions: create limited IdP account, assign contractor app bundle only.*

### Note on Rippling IT

If you use **Rippling IT** for provisioning apps and devices in addition to HRIS, Siit currently consumes Rippling as an HR source of truth — provisioning actions triggered from Siit still flow through your IdP or the target apps directly. Reach out via in‑app chat if you'd like Rippling IT actions exposed natively in Siit workflows.

### Troubleshooting

**Missing employees.** The installing admin's scope limits what Siit can see. Ask an admin with unrestricted scope to re‑authorize the connection from **Settings → Workspace → Integration library → Rippling → Reauthorize**.

**Custom field didn't appear.** Confirm the custom field is enabled at the API level in Rippling and included in the install scope, then re‑run mapping.

**Manager is empty.** In Rippling, confirm a reporting manager is assigned on the employee's profile.

**"App not authorized" on reconnect.** Rippling may have revoked the token after an admin change. Go through the install flow again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/integrations/hris/rippling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.