Rippling

Manage employees, departments, and company data via the Rippling Platform API.

Detail	Value
Category	HR
Base URL	https://api.rippling.com/platform/api
Authentication	OAuth2
Endpoints	6
Connector key	rippling

Using Rippling in a workflow

1. Go to Connections and click New Connection.
2. Pick Rippling from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /employees	List employees
GET /employees/{employeeId}	Get an employee
GET /departments	List departments
GET /teams	List teams
GET /leave_requests	List leave requests
GET /company	Get company info

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /employees

List employees

Detail	Value
Operation ID	hr.listEmployees
Method	GET
Path	/employees

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Rippling connection from the Connection dropdown.
3. In the Operation dropdown, select hr.listEmployees.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Rippling API reference.

GET /employees/{employeeId}

Get an employee

Detail	Value
Operation ID	hr.getEmployee
Method	GET
Path	/employees/{employeeId}

Parameters

Name	Location	Type	Required
employeeId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Rippling connection from the Connection dropdown.
3. In the Operation dropdown, select hr.getEmployee.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Rippling API reference.

GET /departments

List departments

Detail	Value
Operation ID	hr.listDepartments
Method	GET
Path	/departments

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Rippling connection from the Connection dropdown.
3. In the Operation dropdown, select hr.listDepartments.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Rippling API reference.

GET /teams

List teams

Detail	Value
Operation ID	hr.listTeams
Method	GET
Path	/teams

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Rippling connection from the Connection dropdown.
3. In the Operation dropdown, select hr.listTeams.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Rippling API reference.

GET /leave_requests

List leave requests

Detail	Value
Operation ID	hr.listLeaveRequests
Method	GET
Path	/leave_requests

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Rippling connection from the Connection dropdown.
3. In the Operation dropdown, select hr.listLeaveRequests.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Rippling API reference.

GET /company

Get company info

Detail	Value
Operation ID	hr.getCompany
Method	GET
Path	/company

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Rippling connection from the Connection dropdown.
3. In the Operation dropdown, select hr.getCompany.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Rippling API reference.