# Rippling integrations

> Call the Rippling API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/rippling-integrations/
**Categories:** Human resources
**Connects through:** HTTP Connector

## Overview

Rippling is a workforce platform that runs HR, payroll, time off, and employee records for a company in one system. Tray.ai connects to Rippling through the HTTP Connector, so your workflows can call the Rippling API alongside the rest of your stack.

## Use cases

### Workers

Read workers in Rippling from any Tray.ai workflow. The Rippling API covers calls such as list workers and retrieve a worker.

- List workers
- Retrieve a worker

### Users

Read users in Rippling from any Tray.ai workflow. The Rippling API covers calls such as list users and retrieve a user.

- List users
- Retrieve a user

### Departments

Read and create departments in Rippling from any Tray.ai workflow. The Rippling API covers calls such as list departments and create a department.

- List departments
- Create a department

### Work locations

Read, create, and update work locations in Rippling from any Tray.ai workflow. The Rippling API covers calls such as list work locations and create a work location.

- List work locations
- Create a work location
- Update a work location

### Leave requests

Read and create leave requests in Rippling from any Tray.ai workflow. The Rippling API covers calls such as list leave requests and create a leave request.

- List leave requests
- Create a leave request

### Custom objects

Read and create custom objects in Rippling from any Tray.ai workflow. The Rippling API covers calls such as list custom objects and create a custom object.

- List custom objects
- Create a custom object
- List custom object records

## Challenges Tray.ai solves

### Keeping Rippling credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Rippling credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Rippling API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Rippling API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Rippling?

Yes. Tray.ai connects to Rippling through the HTTP Connector, which calls the Rippling API directly. Any call the Rippling API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Rippling?

The Rippling API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Rippling connector?

Rippling runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Rippling connector from the Rippling API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/