> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-rippling-sftp.md).

# Integrating with Rippling (SFTP)

This guide walks you through sending your Rippling data to Drivetrain on an automated daily schedule using SFTP. You'll pick a Rippling report and use Rippling's **Workflow Studio** to export it as a CSV and deliver it to Drivetrain's secure SFTP server — so your headcount models and workforce plans always reflect the latest data, with no manual uploads.

Prefer a direct connection? Use the [API Key method](/integration-guide/readme/hris-and-ats/integrating-with-rippling-via-api-key.md).

{% hint style="info" %}
Choose the **SFTP method** when your team standardizes on scheduled file feeds, or when **direct API access isn't available.**
{% endhint %}

### How it works

1. You pick (or build) a Rippling report with the employee fields Drivetrain needs.
2. In Workflow Studio, a **daily schedule** triggers a **Send a report via SFTP** action.
3. Rippling exports the report as a **CSV** and drops it into Drivetrain's SFTP folder every day.
4. Drivetrain ingests the file and refreshes your models automatically.

### Prerequisites

* **Admin access** to Rippling — required to build reports and workflows in Workflow Studio.
* The **SFTP connection details** from your Drivetrain customer success manager (CSM):
  * SFTP Hostname
  * SFTP Username
  * SFTP Password
  * Destination folder (example: `/sftp-XXX/rippling`)
  * Port: `22`

{% hint style="info" %}
Request these **SFTP credentials** from your **Drivetrain CSM** before you begin, and treat them like passwords — share and store them only through a secure channel.
{% endhint %}

#### Step 1 — Identify the report to send

Choose (or create) the Rippling report that contains the workforce data you want in Drivetrain. Typical fields include:

* Employee name, Preferred name, Employee ID, Work email
* Job title, Employee type, Department, Location
* Start date and End / Termination date
* Manager name, Manager email, Manager ID

#### Step 2 — Build the scheduled workflow in Workflow Studio

1. Open **Workflow Studio** — use the **search bar at the top** of Rippling to search for “Workflow Studio”, then open it.

<figure><img src="/files/5RahjB25xpgQVZ7wHLHu" alt=""><figcaption></figcaption></figure>

2. From the left sidebar, add a **Schedule trigger** and pick a suitable time for the workflow to run **daily**.
3. Drag the **Send a report via SFTP** action onto the canvas, between the desired steps.
4. Click the step you just added to open its settings, then configure it as follows:
   1. **Select the report** you want to send (from Step 1).
   2. Select **password-based authentication**.
   3. Enter the **SFTP hostname** provided by your CSM.
   4. Enter the **SFTP username** provided by your CSM.
   5. Enter the **SFTP password** provided by your CSM.
   6. Set **Port** to `22`.
   7. Set a **filename** — keep it **without spaces** (for example, `rippling_employees`).
   8. Set the **Destination folder** as provided (for example, `/sftp-XXX/rippling`).
   9. Set **File type** to **CSV**.
   10. **Skip** the date and time format.
   11. **Skip** the total and subtotal rows.
   12. Click **Test step** to confirm the connection and delivery.
   13. Click **Save** to activate the workflow.

{% hint style="info" %}
If the test fails, re-check the hostname, username, and password, confirm the **port is 22**, and make sure the **destination folder path exactly matches** what your CSM provided (no trailing spaces).
{% endhint %}

#### Step 3 — Notify Drivetrain

Inform the Drivetrain team that the workflow is live so they can verify the file lands in the SFTP folder and complete the setup on the Drivetrain side.

### What happens next

Once verified, the report is delivered to Drivetrain's SFTP **automatically every day at your scheduled time** — no manual work required. Drivetrain ingests each file and keeps your models up to date.

### Troubleshooting

* **Test step fails:** double-check the credentials and that the port is `22`; confirm the destination path is exact.
* **File doesn't arrive:** make sure the workflow is turned **on** and the schedule trigger is enabled, and that the filename has no spaces.
* **Columns look wrong or missing in Drivetrain:** keep the report structure stable and notify your CSM before changing report columns.

### Support

If you run into any issues not covered here, contact your Drivetrain CSM or email [**support@drivetrain.ai**](mailto:support@drivetrain.ai).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-rippling-sftp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.