Rippling
Bring new starters, changes and leavers from Rippling into every system that needs them, with HR approving each change.
33 ways to read, 14 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Rippling, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create departmentApproval by rule
- Create job codeApproval by rule
- List leave balancesRead
Example flow
- Rippling · List leave balancesDone
- Rippling · Create departmentNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Rippling.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Rippling
- Rippling's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read Rippling workers, users, compensation, legal entities, supergroups and leave; create and update departments, teams, work locations, levels, job codes and leave requests.
Rippling People Center Inc. API docs- Source actions
- 33
- Destination actions
- 14
- Data types
- 22
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Companies1
- List companiesSource
The company bound to the token.
Compensations2
- Get compensationSource
One compensation by ID.
- List compensationsSource
Worker compensation: salary, hourly wage, bonus targets and commission (read only).
Custom fields1
- List custom fieldsSource
Custom field definitions with type and options.
Departments4
- Create departmentDestinationNot retried automaticallyApproval before production
Creates a department, optionally under a parent.
- Get departmentSource
One department by ID.
- List departmentsSource
Departments with parent and reference code.
- Update departmentDestinationProvider duplicate protectionApproval before production
Renames or re-parents a department.
Employment types1
- List employment typesSource
Employment types such as salaried full time or contractor.
Job codes4
- Create job codeDestinationNot retried automaticallyApproval before production
Creates a job code under a job dimension.
- Get job codeSource
One job code by ID.
- List job codesSource
Job codes with dimension, pay rate, department and location.
- Update job codeDestinationProvider duplicate protectionApproval before production
Renames, archives or re-rates a job code.
Job dimensions3
- Create job dimensionDestinationNot retried automaticallyApproval before production
Creates a job dimension.
- List job dimensionsSource
Job dimensions (for example Store or Role) that group job codes.
- Update job dimensionDestinationProvider duplicate protectionApproval before production
Changes a job dimension.
Job functions1
- List job functionsSource
Job functions defined for the company.
Leave accruals1
- List leave accrualsSource
Leave accrual and adjustment entries per worker and leave type (read only).
Leave balances1
- List leave balancesSource
Balances per worker and leave type, in minutes and days.
Leave requests4
- Create leave requestDestinationNot retried automaticallyApproval before production
Submits a pending leave request for a worker.
- Get leave requestSource
One leave request by ID.
- List leave requestsSourceIncremental
Leave requests with status, dates and reviewer.
- Update leave requestDestinationProvider duplicate protectionApproval before production
Changes the dates, times, reason or comments of a leave request.
Leave types1
- List leave typesSource
Leave types with paid flag.
Legal entities2
- Get legal entitySource
One legal entity by ID.
- List legal entitiesSource
Company legal entities with country, level, management type and addresses.
Levels4
- Create levelDestinationNot retried automaticallyApproval before production
Creates a job level on a track.
- Get levelSource
One level by ID.
- List levelsSource
Job levels with rank and track.
- Update levelDestinationProvider duplicate protectionApproval before production
Changes a level's name, track, global level or description.
Supergroup members1
- List supergroup membersSource
Workers who are members of a supergroup.
Supergroups2
- Get supergroupSource
One supergroup by ID.
- List supergroupsSource
Attribute-based groups used for policies, apps and workflows.
Teams4
- Create teamDestinationNot retried automaticallyApproval before production
Creates a team, optionally under a parent team.
- Get teamSource
One team by ID.
- List teamsSource
Teams with their parent team.
- Update teamDestinationProvider duplicate protectionApproval before production
Renames or re-parents a team.
Titles1
- List titlesSource
Job titles defined for the company.
Tracks1
- List tracksSource
Career tracks that levels belong to.
Users2
- Get userSource
One user by ID.
- List usersSourceIncremental
People and login profiles: names, work email, locale and time zone.
Work locations4
- Create work locationDestinationNot retried automaticallyApproval before production
Creates a work location with its address.
- Get work locationSource
One work location by ID.
- List work locationsSource
Work locations with address.
- Update work locationDestinationProvider duplicate protectionApproval before production
Renames a work location or changes its address.
Workers2
- Get workerSource
One worker by ID.
- List workersSourceIncremental
Employment records with status, title, manager, department, level and custom fields.
Access and limits
- Authentication
- Rippling API token (REST API v2)
- Plans and access
- Rippling customers; API tokens are created in Tools → Developer → API Tokens. A token sees the intersection of its scopes and its owner's permission profile; hidden fields return null and are listed in __meta.redacted_fields. Tokens are revoked when unused for 30 days or when the owner is terminated.
- Test environment
- Rippling does not offer a public sandbox for customer API tokens.
- Rate limits
- 300 requests per IP per 10-second sliding window; over the limit every request gets HTTP 429 for 10 seconds.
- Pagination
- limit (max 100) and cursor, following the absolute next_link until it is null.
- Provider events
- Rippling in-product webhooks and App Shop partner webhooks for employee and leave events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Uses the v2 REST API on rest.ripplingapis.com; the legacy V1 platform API (/platform/api) is not used.
- Third-party groups (V1 /groups) are not implemented: they require a partner OAuth app, and v2 offers Supergroups instead.
- Leave requests are created as PENDING so they follow Rippling's approval flow; approvals are not automated.
- Null values can mean the token cannot see a field; check redactedFields.
- Compensation is read only and returns only what the token owner's permission profile can see. SSNs, dates of birth and home addresses are not mapped.
- Deletes, worker terminations, leave approvals, leave accrual grants, supergroup membership changes and payroll runs are intentionally not implemented.
- Scope names for teams, work locations, levels, tracks, titles, job functions, legal entities, compensations, job dimensions, job codes, supergroups and leave accruals follow Rippling's <object>.read / <object>.read-write convention; the scope reference page could not be machine-read, so confirm them when creating the token.
Developer reference
- Create the Rippling People Center Inc. credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Rippling, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/rippling and the Connections API.