/

Rippling

Identity connector

Rippling

Read workers, departments and employment changes from Rippling and turn them into typed events. Use them to start onboarding before day one and to run offboarding on the last day.

Connect Rippling
Connect Rippling
See setup steps
See setup steps

Identity

Category

Polling

Sync mode

Every 5 min

Latency

5 min

Setup time

What it can do

Triggers · 4
  • Worker hiredPoll
  • Start date reachedPoll
  • Worker terminatedPoll
  • Department changedPoll
Actions · 3
  • Look up a workerRead
  • List workers by departmentRead
  • Read a manager chainRead

Overview

The Rippling connector reads workers and their employment status from the Rippling REST API on a schedule. Changes become typed events with the worker, manager, department and dates attached, and each one appears in the trace of the run it started.

Teams use it to create Okta and Google Workspace accounts a week before a start date, to order equipment through Jamf, and to remove access the evening a termination takes effect.

Supported objects

  • Workers, including employment type, status and start and end dates

  • Departments, teams and work locations

  • Managers, read as a chain up to the top of the org

How polling works

Every five minutes Tessel lists workers updated since its last cursor and compares each record with the version it saw before. A changed status, date or department becomes the matching event. Date triggers such as start date reached fire once, at the time zone of the worker's work location.

GET https://rest.ripplingapis.com/workers
  ?filter=updated_at gt '2026-10-06T08:55:00Z'
  &expand=department,manager
  &order_by=updated_at
Authorization: Bearer <api token

GET https://rest.ripplingapis.com/workers
  ?filter=updated_at gt '2026-10-06T08:55:00Z'
  &expand=department,manager
  &order_by=updated_at
Authorization: Bearer <api token

GET https://rest.ripplingapis.com/workers
  ?filter=updated_at gt '2026-10-06T08:55:00Z'
  &expand=department,manager
  &order_by=updated_at
Authorization: Bearer <api token

Rate limits

Rippling limits requests per token. Tessel pages through results, waits when it sees a 429 and resumes from the same cursor, so a busy hiring week never drops a change. Each poll is shown in the trace with its cursor and page count.

Permissions needed

Create an API token in Rippling with read-only scopes. Tessel does not write to Rippling, so no write scopes are needed. Fields your token cannot see are left out of the event schema.

  • workers.read for worker records and employment status

  • departments.read for departments and teams

  • users.read for work email and manager links

Setup

Four steps. About five minutes.

Most of the time goes into choosing token scopes. Tessel shows which fields each scope unlocks.

  1. Create an API token with read-only scopesRippling2 min
  2. Paste the token into TesselTessel1 min
  3. Pick triggers and the start date lead timeTessel2 min
  4. Update a test worker and wait for the next pollVerify5 min

Onboarding that starts on hire.

Connect Rippling on the free plan. Up to three builders and 10,000 runs a month, no card required.

Connect Rippling
Connect Rippling
All integrations
All integrations

One email a month. Only what shipped.

A1

Product

C1

Layouts

D1

Company

E1

Template

F1

All systems operational
fra41 ms
iad38 ms
sin52 ms

C2

Elsewhere

XLinkedInGitHubYouTube

E2

Move across the wordmark168 blocks · iso 30°

One email a month. Only what shipped.

A1

Product

C1

Layouts

D1

Company

E1

Template

F1

All systems operational
fra41 ms
iad38 ms
sin52 ms

C2

Elsewhere

XLinkedInGitHubYouTube

E2

Move across the wordmark168 blocks · iso 30°

One email a month. Only what shipped.

A1

Product

C1

Layouts

D1

Company

E1

Template

F1

All systems operational
fra41 ms
iad38 ms
sin52 ms

C2

Elsewhere

XLinkedInGitHubYouTube

E2

Move across the wordmark168 blocks · iso 30°

Create a free website with Framer, the website builder loved by startups, designers and agencies.