---
title: "Connect Rippling to Rig — Rig guide"
description: "Connect Rippling to Rig with an API token and sync workers, departments, compensation, leave, time entries and recruiting data into your warehouse."
canonical: "https://rig.so/guides/connect-rippling"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Rippling to Rig

Sync workers, org structure, compensation, leave, time tracking and recruiting data from Rippling into Rig. Each Rippling API scope maps to its own table, so you grant only the data you want shared.

## Before you start

- You need the **Manage the API Tokens app** permission, or **Create and manage API Tokens** in the API credentials tab of the Developer app.
- A token can only see what its owner can see, so create it as someone whose permission profile covers the data you want.
- Decide which objects to share. Rig skips a stream whose scope you do not grant.

## Step 1: Create a Rippling API token

1. In Rippling, go to **Developer** → **API credentials**.
2. Click **New API token**.
3. Tick the `.read` scope of each object you want synced, for example `workers.read` for workers. Rippling's permissions reference lists the names.
4. Finish the flow and copy the token straight away. Rippling does not show it again.

Tokens expire when unused
Rippling revokes a token that goes unused for more than 30 days or whose owner is terminated. A scheduled sync keeps it in use, but create a new token if the connection has been paused for a month.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **Rippling**, open the card and click `Connect`.
3. **API token**: Paste the token you copied.
4. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

Rippling lands in its own `rippling` schema in your warehouse:

- **People**: workers, users, employment types and compensations.
- **Org structure**: companies, departments, teams, levels, tracks and work locations.
- **Time and leave**: leave requests and types, schedules, shift assignments, time cards and time entries.
- **Headcount and recruiting**: headcount positions and priorities, job requisitions, candidates and candidate applications.

Only streams whose scope the token holds are synced. A field the token owner may not see arrives empty and is listed in a `__meta__redacted_fields` child table, so an empty column can be told apart from a redacted one.

## Good to know

- Rippling returns a 403 for an endpoint whose scope is missing. Rig marks that stream as missing a scope and syncs the rest.
- Every table is re-read in full on each sync and swept for deletions.
- Employment type and hours worked are on the employment types table, so you do not need the compensation scope to tell contractors from employees.
- To disconnect Rippling, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Report on headcount and org structure
- Understand leave and working time
- Track hiring against headcount plans
- Analyse compensation by level

[More ideas for using Rippling](https://rig.so/integrations/rippling)

## Rippling documentation

- [Rippling: API tokens and permissions](https://developer.rippling.com/documentation/rippling-platform/developer/api-tokens)
- [Rippling REST API](https://developer.rippling.com/documentation/rest-api)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-rippling)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)