Rippling Connector
Description
Rippling makes it easy to manage your company's Payroll, Benefits, HR, and IT—all in one, modern platform.
Connections
OAuth 2.0
key: authorizationCodeTo authenticate with Rippling using OAuth 2.0, create and deploy an App Listing in the Rippling partner company dashboard. Refer to the Developer Portal documentation for detailed guidance, including the Partner Requirements and Installation OAuth Guide.
Prerequisites
- A Rippling partner account (apply via Partner Requirements)
- Access to the partner company dashboard at app.rippling.com
Setup Steps
- Log in to the Rippling partner company at app.rippling.com and navigate to Partner > Client Command Center
- Create an App Listing with the following configuration:
- Set the Redirect URI to:
https://oauth2.prismatic.io/callback - Note the Authorization URL (typically in the format
https://app.rippling.com/apps/PLATFORM/{AppName})
- Set the Redirect URI to:
- Deploy the App Listing (sandbox first for testing)
- Retrieve the Client ID and Client Secret from the deployed App Listing
- Determine the required scopes for the integration (space-delimited values like
employees:read departments:read)
Configure the Connection
- Enter the Client ID and Client Secret from the deployed App Listing
- Enter the Authorization URL from step 2
- For Scopes, enter the space-delimited scopes determined in step 5. Refer to Rippling's scopes documentation for available scope values
- The Token URL is automatically set to
https://app.rippling.com/api/o/token/and does not require modification
| Input | Notes | Example |
|---|---|---|
| Authorization URL | The OAuth 2.0 authorization URL for your Rippling app. Replace {AppName} with your actual app name. Learn more | https://app.rippling.com/apps/PLATFORM/YourAppName |
| Client ID | The OAuth 2.0 client ID for your Rippling partner app. Found in your app configuration in the Rippling admin console. | |
| Client Secret | The OAuth 2.0 client secret for your Rippling partner app. Keep this value secure and do not share it. | |
| Scopes | Space-separated list of OAuth permission scopes. Scopes are configured in your Rippling app settings and determine which resources your integration can access. | employees:read departments:read teams:read |
| Token URL | The OAuth 2.0 token URL for Rippling's API. | https://app.rippling.com/api/o/token/ |
Bearer API Key
key: bearerApiKeyTo authenticate with Rippling using a bearer API key, generate an API key from the Rippling admin console and enter it into the connection configuration.
Prerequisites
- Access to the Rippling admin console
- Authority to generate API keys
Setup Steps
To generate an API key:
- Navigate to the Rippling admin console
- Open the Settings or API section
- Locate the API Keys area
- Click Generate New API Key or Create API Key
- Copy the generated API key value
The API key is used for authenticating API requests on behalf of the organization. Keep the API key secure and do not share it publicly.
Configure the Connection
- Enter the API key into the API Key field in the connection configuration
Refer to Rippling's API documentation for additional information on API key management and API authentication.
Verify Connection
After saving the connection, the API key is ready for use in integration actions.
| Input | Notes | Example |
|---|---|---|
| API Key | API key from the Rippling admin console. Navigate to <strong>Admin > Settings > API</strong> in Rippling to generate your API key. Learn more |
Triggers
New and Updated Records
Checks for new and updated records in Rippling on a configured schedule. | key: pollChangesTrigger
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Resource Type | The type of Rippling resource to poll for changes. | workers |
| Show New Records | When true, includes newly created records in the results. | true |
| Show Updated Records | When true, includes updated records in the results. | true |
This trigger polls the Rippling API for new and updated records on a scheduled basis.
How It Works
- The trigger runs on the configured schedule
- It fetches records from Rippling for the selected resource type — Workers and Users are queried with a server-side
updated_at gt lastPolledAtfilter for efficiency; Departments and Teams fetch all records and apply timestamp comparison client-side - Records are categorized as created or updated based on their timestamps relative to the last poll time
- The trigger updates its internal state after each poll
Configuration
Configure the following inputs:
- Connection: The Rippling connection used to authenticate API requests
- Resource Type: The type of records to monitor — Workers, Users, Departments, or Teams
- Show New Records: When enabled, includes newly created records in the results. Defaults to
true - Show Updated Records: When enabled, includes modified records in the results. Defaults to
true
Returned Data
The trigger returns an object with two arrays — created for new records and updated for modified records.
Example Response
{
"data": {
"created": [
{
"id": "wrk_01H9ZQ2KBCDEF12345",
"name": "Jane Smith",
"workEmail": "jane.smith@example.com",
"department": "Engineering",
"startDate": "2024-01-15"
}
],
"updated": [
{
"id": "wrk_01H9ZQ2KBCDEF67890",
"name": "John Doe",
"workEmail": "john.doe@example.com",
"department": "Product",
"startDate": "2023-06-01"
}
]
}
}
Notes
- All four resource types — Workers, Users, Departments, and Teams — support both new and updated record detection
- Workers and Users use a server-side filter (
updated_at gt lastPolledAt) for efficient retrieval; Departments and Teams fetch all records and filter client-side by comparing timestamps - Refer to the Rippling API documentation for rate limit details and available fields per resource type
Data Sources
Select Business Partner Group
Select a business partner group from your Rippling account. | key: selectBusinessPartnerGroup | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Department
Select a department from your Rippling account. | key: selectDepartment | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Employment Type
Select an employment type from your Rippling account. | key: selectEmploymentType | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Job Function
Select a job function from your Rippling account. | key: selectJobFunction | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Object Category
Select an object category from your Rippling account. | key: selectObjectCategory | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Supergroup
Select a supergroup from your Rippling account. | key: selectSupergroup | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Team
Select a team from your Rippling account. | key: selectTeam | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select User
Select a user from your Rippling account. | key: selectUser | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Work Location
Select a work location from your Rippling account. | key: selectWorkLocation | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Select Worker
Select a worker from your Rippling account. | key: selectWorker | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Actions
Create Business Partner (V2)
Create a new business partner. | key: createBusinessPartner
| Input | Notes | Example |
|---|---|---|
| Business Partner Group ID | The unique identifier of the business partner group to associate with. | bpg_abc123xyz |
| Connection | The Rippling connection to use. | |
| Worker ID | The ID of the worker to associate with the business partner. | wkr_abc123xyz |
Example Payload for Create Business Partner (V2)⤓
Create Business Partner Group (V2)
Create a new business partner group. | key: createBusinessPartnerGroup
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Default Business Partner ID | The unique identifier of the default business partner for this group. | bp_abc123xyz |
| Name | The name of the business partner group. | Engineering Department |
Example Payload for Create Business Partner Group (V2)⤓
Create Custom Object (V2)
Create a new custom object. | key: createCustomObject
| Input | Notes | Example |
|---|---|---|
| Category | The category for the custom object. | Operations |
| Connection | The Rippling connection to use. | |
| Description | A description of the custom object. | Department responsible for product development and technical infrastructure |
| Name | The name of the custom object. | Engineering Department |
Example Payload for Create Custom Object (V2)⤓
Create Object Category (V2)
Create a new object category. | key: createObjectCategory
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Description | A description of the object category. | Department responsible for product development and technical infrastructure |
| Name | The name of the object category. | Engineering Department |
Example Payload for Create Object Category (V2)⤓
Delete Business Partner (V2)
Delete a business partner by ID. | key: deleteBusinessPartner
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Business Partner ID | Unique identifier for the business partner to delete. | bp_abc123xyz |
Example Payload for Delete Business Partner (V2)⤓
Delete Business Partner Group (V2)
Delete a business partner group by ID. | key: deleteBusinessPartnerGroup
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Business Partner Group ID | Unique identifier for the business partner group to delete. | bpg_abc123xyz |
Example Payload for Delete Business Partner Group (V2)⤓
Delete Custom Object (V2)
Delete a custom object by API name. | key: deleteCustomObject
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Custom Object API Name | The API name of the custom object to delete. | CustomProject__c |
Example Payload for Delete Custom Object (V2)⤓
Delete Groups Group Id (V1)
DELETE Group. | key: deleteGroupsGroupId
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Group ID | The unique identifier for the group in Rippling. | 12345 |
Example Payload for Delete Groups Group Id (V1)⤓
Delete Object Category (V2)
Delete an object category by ID. | key: deleteObjectCategory
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Object Category ID | Unique identifier for the object category to delete. | cat_abc123xyz |
Example Payload for Delete Object Category (V2)⤓
Get Business Partner (V2)
Retrieve a specific business partner by ID. | key: getBusinessPartner
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: business_partner_group, worker, client_group. | business_partner_group,worker,client_group |
| Business Partner ID | The unique identifier for the business partner. | bp_abc123xyz |
Example Payload for Get Business Partner (V2)⤓
Get Business Partner Group (V2)
Retrieve a specific business partner group by ID. | key: getBusinessPartnerGroup
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: default_business_partner. | default_business_partner |
| Business Partner Group ID | The unique identifier for the business partner group. | bpg_abc123xyz |
Example Payload for Get Business Partner Group (V2)⤓
Get Companies (V1)
GET Current Company. | key: getCompanies
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Example Payload for Get Companies (V1)⤓
Get Company Activity (V1)
GET Company Activity. | key: getCompanyActivity
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| End Date | ISO 8601 timestamp to list activity before (inclusive). | 2024-12-31T23:59:59Z |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. | |
| Start Date | ISO 8601 timestamp to list activity after (inclusive). | 2024-01-01T00:00:00Z |
Example Payload for Get Company Activity (V1)⤓
Get Custom Fields (V1)
GET Custom Fields. | key: getCustomFields
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Custom Fields (V1)⤓
Get Custom Object (V2)
Retrieve a specific custom object by API name. | key: getCustomObject
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Custom Object API Name | The API name of the custom object. | CustomProject__c |
Example Payload for Get Custom Object (V2)⤓
Get Department (V2)
Retrieve a specific department by ID. | key: getDepartment
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: parent, department_hierarchy. | parent,department_hierarchy |
| Department ID | The unique identifier for the department. | dept_abc123xyz |
Example Payload for Get Department (V2)⤓
Get Departments (V1)
GET Departments. | key: getDepartments
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Departments (V1)⤓
Get Employees (V1)
GET Employees. | key: getEmployees
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Employees (V1)⤓
Get Employees Employee Id (V1)
GET Employee. | key: getEmployeesEmployeeId
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Employee ID | The unique identifier for the employee in Rippling. | 123456 |
Example Payload for Get Employees Employee Id (V1)⤓
Get Employees Include Terminated (V1)
GET Employees (Including Terminated). | key: getEmployeesIncludeTerminated
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| EIN | Employer Identification Number (EIN), also known as the Federal Employer Identification Number or Federal Tax Identification Number. | 123456789 |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Employees Include Terminated (V1)⤓
Get Employment Type (V2)
Retrieve a specific employment type by ID. | key: getEmploymentType
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Employment Type ID | The unique identifier for the employment type. | emp_type_abc123xyz |
Example Payload for Get Employment Type (V2)⤓
Get Groups (V1)
GET Groups. | key: getGroups
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Example Payload for Get Groups (V1)⤓
Get Job Function (V2)
Retrieve a specific job function by ID. | key: getJobFunction
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Job Function ID | The unique identifier for the job function. | job_func_abc123xyz |
Example Payload for Get Job Function (V2)⤓
Get Leave Requests (V1)
GET Leave Requests. | key: getLeaveRequests
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Date Range Filters | Optional inclusive date-range filters to narrow results by date. | |
| ID | The unique identifier of the leave request. | lr_123456 |
| Leave Policy | The leave policy identifier or name. | PTO |
| Processed By | The identifier or email of the person who processed the leave request. | manager@example.com |
| Requested By | The identifier or email of the person who requested the leave. | john.doe@example.com |
| Role | The role associated with the leave request. | Manager |
| Status | The status of the leave request. | APPROVED |
Example Payload for Get Leave Requests (V1)⤓
Get Levels (V1)
GET Levels. | key: getLevels
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Levels (V1)⤓
Get Me (V1)
GET Current User. | key: getMe
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Example Payload for Get Me (V1)⤓
Get Object Category (V2)
Retrieve a specific object category by ID. | key: getObjectCategory
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Object Category ID | The unique identifier for the object category. | cat_abc123xyz |
Example Payload for Get Object Category (V2)⤓
Get Saml Idp Metadata (V1)
GET SAML Metadata. | key: getSamlIdpMetadata
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Example Payload for Get Saml Idp Metadata (V1)⤓
Get SSO Me (V2)
Retrieve SSO information of the current user. | key: getSsoMe
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: company. | company |
Example Payload for Get SSO Me (V2)⤓
Get Supergroup (V2)
Retrieve a specific supergroup by ID. | key: getSupergroup
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Supergroup ID | The unique identifier for the supergroup. | sgrp_abc123xyz |
Example Payload for Get Supergroup (V2)⤓
Get Team (V2)
Retrieve a specific team by ID. | key: getTeam
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: parent. | parent |
| Team ID | The unique identifier for the team. | team_abc123xyz |
Example Payload for Get Team (V2)⤓
Get Teams (V1)
GET Teams. | key: getTeams
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Teams (V1)⤓
Get User (V2)
Retrieve a specific user by ID. | key: getUser
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| User ID | The unique identifier for the user. | usr_abc123xyz |
Example Payload for Get User (V2)⤓
Get Work Location (V2)
Retrieve a specific work location by ID. | key: getWorkLocation
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Work Location ID | The unique identifier for the work location. | loc_abc123xyz |
Example Payload for Get Work Location (V2)⤓
Get Work Locations (V1)
GET Work Locations. | key: getWorkLocations
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Page and page-size controls. |
Example Payload for Get Work Locations (V1)⤓
Get Worker (V2)
Retrieve a specific worker by ID. | key: getWorker
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: user, manager, legal_entity, employment_type, compensation, department, teams, level, custom_fields, business_partners. | user,manager,department |
| Worker ID | The unique identifier for the worker. | wkr_abc123xyz |
Example Payload for Get Worker (V2)⤓
List Business Partner Groups (V2)
Retrieve a list of business partner groups. | key: listBusinessPartnerGroups
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: default_business_partner. | default_business_partner |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Business Partner Groups (V2)⤓
List Business Partners (V2)
Retrieve a list of business partners. | key: listBusinessPartners
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: business_partner_group, worker, client_group. | business_partner_group,worker,client_group |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Filter | Filterable fields: worker_id, business_partner_group_id. Example: worker_id eq 'abc123'. | worker_id eq 'abc123' |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Business Partners (V2)⤓
List Companies (V2)
Retrieve a list of companies. | key: listCompanies
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: parent_legal_entity, legal_entities. | parent_legal_entity,legal_entities |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Companies (V2)⤓
List Custom Fields (V2)
Retrieve a list of custom fields. | key: listCustomFields
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Custom Fields (V2)⤓
List Custom Objects (V2)
Retrieve a list of custom objects. | key: listCustomObjects
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Custom Objects (V2)⤓
List Departments (V2)
Retrieve a list of departments. | key: listDepartments
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: parent, department_hierarchy. | parent,department_hierarchy |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Departments (V2)⤓
List Employment Types (V2)
Retrieve a list of employment types. | key: listEmploymentTypes
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Employment Types (V2)⤓
List Entitlements (V2)
Retrieve a list of entitlements. | key: listEntitlements
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Entitlements (V2)⤓
List Job Functions (V2)
Retrieve a list of job functions. | key: listJobFunctions
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Job Functions (V2)⤓
List Object Categories (V2)
Retrieve a list of object categories. | key: listObjectCategories
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Object Categories (V2)⤓
List Supergroups (V2)
Retrieve supergroups matching the input parameters. | key: listSupergroups
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Filter | Filterable fields: app_owner_id, group_type. Example: app_owner_id eq 'abc123'. | app_owner_id eq 'abc123' |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Supergroups (V2)⤓
List Teams (V2)
Retrieve a list of teams. | key: listTeams
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: parent. | parent |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Teams (V2)⤓
List Users (V2)
Retrieve a list of users. | key: listUsers
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Users (V2)⤓
List Work Locations (V2)
Retrieve a list of work locations. | key: listWorkLocations
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Work Locations (V2)⤓
List Workers (V2)
Retrieve a list of workers with filtering, expansion, and sorting support. | key: listWorkers
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Expand | Comma-separated fields to expand: user, manager, legal_entity, employment_type, compensation, department, teams, level, custom_fields, business_partners. | user,manager,department |
| Fetch All | When true, automatically fetches all pages of results using pagination. | false |
| Filter | Filter expression. Filterable fields: status, work_email, user_id, created_at, updated_at. Example: status eq 'ACTIVE'. | status eq 'ACTIVE' |
| Pagination | Sort order and cursor controls for paging through results. |
Example Payload for List Workers (V2)⤓
Patch Groups Group Id (V1)
PATCH Group. | key: patchGroupsGroupId
| Input | Notes | Example |
|---|---|---|
| Additional Fields | Additional optional fields: includes Name, Spoke ID, Users, and Version. | |
| Connection | The Rippling connection to use. | |
| Group ID | The unique identifier for the group in Rippling. | 12345 |
Example Payload for Patch Groups Group Id (V1)⤓
Post Ats Candidates Push Candidate (V1)
POST New Candidate. | key: postAtsCandidatesPushCandidate
| Input | Notes | Example |
|---|---|---|
| Additional Fields | Additional optional fields: includes Job Title, Start Date, Department, Employment Type, and Attachments. | |
| Candidate ID | The unique identifier of the candidate from your ATS (Applicant Tracking System). | cand_123456 |
| Compensation | Optional compensation package details: salary, bonus, equity, and currency. | |
| Connection | The Rippling connection to use. | |
| Name & Contact Information | Name, email, and phone contact details. |
Example Payload for Post Ats Candidates Push Candidate (V1)⤓
Post Groups (V1)
POST Groups. | key: postGroups
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Name | The name of the group. | Engineering Team |
| Spoke ID | The external unique identifier for the group entity in your application. | ext_group_123 |
| Users | An array of Rippling user IDs to include in the group. | [123456, 789012] |
Example Payload for Post Groups (V1)⤓
Post Mark App Installed (V1)
Mark App Installed. | key: postMarkAppInstalled
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. |
Example Payload for Post Mark App Installed (V1)⤓
Process Leave Requests (V1)
POST Process Leave Request. | key: processLeaveRequests
| Input | Notes | Example |
|---|---|---|
| Action | The action to take on the leave request. | |
| Connection | The Rippling connection to use. | |
| ID | The unique identifier of the leave request to be processed. | lr_123456 |
Example Payload for Process Leave Requests (V1)⤓
Put Groups Group Id (V1)
PUT Group. | key: putGroupsGroupId
| Input | Notes | Example |
|---|---|---|
| Additional Fields | Additional optional fields: includes Name, Spoke ID, Users, and Version. | |
| Connection | The Rippling connection to use. | |
| Group ID | The unique identifier for the group in Rippling. | 12345 |
Example Payload for Put Groups Group Id (V1)⤓
Raw Request (V1)
Send raw HTTP request to Rippling API. | key: rawRequest
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Data | The HTTP body payload to send to the URL. | {"exampleKey": "Example Data"} |
| File Data | File Data to be sent as a multipart form upload. | [{key: "example.txt", value: "My File Contents"}] |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Form Data | The Form Data to be sent as a multipart form upload. | [{"key": "Example Key", "value": new Buffer("Hello World")}] |
| Header | A list of headers to send with the request. | User-Agent: curl/7.64.1 |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Method | The HTTP method to use. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Timeout | The maximum time that a client will await a response to its request | 2000 |
| URL | Input the path only (/companies/current), The base URL is already included (https://api.rippling.com/platform/api). For example, to connect to https://api.rippling.com/platform/api/companies/current, only /companies/current is entered in this field. | /companies/current |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
Example Payload for Raw Request (V1)⤓
Raw Request (V2)
Send raw HTTP request to Rippling API. | key: rawRequestV2
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Data | The HTTP body payload to send to the URL. | {"exampleKey": "Example Data"} |
| File Data | File Data to be sent as a multipart form upload. | [{key: "example.txt", value: "My File Contents"}] |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Form Data | The Form Data to be sent as a multipart form upload. | [{"key": "Example Key", "value": new Buffer("Hello World")}] |
| Header | A list of headers to send with the request. | User-Agent: curl/7.64.1 |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Method | The HTTP method to use. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Timeout | The maximum time that a client will await a response to its request | 2000 |
| URL | Input the path only (/workers), The base URL is already included (https://rest.ripplingapis.com). For example, to connect to https://rest.ripplingapis.com/workers, only /workers is entered in this field. | /workers |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
Example Payload for Raw Request (V2)⤓
Update Custom Object (V2)
Update an existing custom object. | key: updateCustomObject
| Input | Notes | Example |
|---|---|---|
| Additional Fields | Additional optional fields: includes Name, Description, Category, Plural Label, and Owner Role. | |
| Connection | The Rippling connection to use. | |
| Custom Object API Name | The API name of the custom object to update. | CustomProject__c |
Example Payload for Update Custom Object (V2)⤓
Update Object Category (V2)
Update an existing object category. | key: updateObjectCategory
| Input | Notes | Example |
|---|---|---|
| Connection | The Rippling connection to use. | |
| Description | The new description for the object category. | Department responsible for product development and technical infrastructure |
| Object Category ID | Unique identifier for the object category to update. | cat_abc123xyz |
| Name | The new name for the object category. | Engineering Department |
Example Payload for Update Object Category (V2)⤓
Changelog
2026-09-01
Grouped related optional inputs into structured objects for clearer configuration:
- All list actions: grouped pagination inputs (Limit and Offset on V1 actions; Order By and Cursor on V2 actions; Next and Limit on Get Company Activity (V1)) into a Pagination object; Fetch All remains a top-level toggle
- Post Ats Candidates Push Candidate (V1): grouped Name, Email, and Phone Number into a Name & Contact Information object; Salary Unit, Salary Per Unit, Signing Bonus, Equity Shares, and Currency into a Compensation object; and Job Title, Start Date, Department, Employment Type, and Attachments into an Additional Fields object
- Get Leave Requests (V1): grouped Start Date, End Date, From, and To into a Date Range Filters object
- Put Groups Group Id (V1) and Patch Groups Group Id (V1): grouped Name, Spoke ID, Users, and Version into an Additional Fields object
- Update Custom Object (V2): grouped Name, Description, Category, Plural Label, and Owner Role into an Additional Fields object
2026-05-14
Added bulk pagination support to V1 and V2 list actions, allowing users to fetch all pages of results in a single action invocation
2026-04-30
Updated spectral version
2026-04-21
Added New and Updated Records polling trigger that checks for new and updated workers, users, departments, and teams in Rippling on a configured schedule
2026-03-05
Added inline data sources for workers, departments, teams, users, work locations, employment types, job functions, supergroups, business partner groups, and object categories to enable dynamic dropdown selection
2026-02-25
Added comprehensive V2 API actions with improved filtering, expansion, and sorting support:
- Business Partner Groups - List, Get, Create, and Delete business partner groups
- Business Partners - List, Get, Create, and Delete business partners
- Companies - List companies
- Custom Fields - List custom fields
- Custom Objects - List, Get, Create, Update, and Delete custom objects
- Departments - List and Get departments
- Employment Types - List and Get employment types
- Entitlements - List entitlements
- Job Functions - List and Get job functions
- Object Categories - List, Get, Create, Update, and Delete object categories
- Supergroups - List and Get supergroups
- Teams - List and Get teams
- Users - List and Get users
- Work Locations - List and Get work locations
- Workers - List and Get workers
- Get SSO Me - Retrieve current user information
- Raw Request (V2) - Make custom V2 API requests