Integrating with Rippling (via API Key)

Overview

What is the value of the integration?

The Rippling–Drivetrain integration automatically syncs your workforce data from Rippling into Drivetrain, ensuring that headcount and employment changes stay fully up-to-date in your financial models and workforce plans.

This removes manual data entry, reduces errors, and helps Finance and People Ops maintain a single source of truth for workforce planning.

Why should customers use the integration?

Use this integration if you want to:

• Keep headcount models automatically current.

• Build accurate workforce planning scenarios that reflect hires, exits, and promotions.

• Avoid manual CSV uploads or reconciliations between HR and Finance systems.

• Reduce planning cycle time and improve forecast accuracy.

When should customers use this integration?

Customers should use this integration when:

• Rippling is the system of record for HR.

• Workforce-related drivers significantly impact budgets, forecasts, and scenario plans.

• Multiple teams depend on accurate employee data for planning (Finance, HR, FP&A, Operations).

If your organization manually manages workforce information or uses another HRIS as the primary source of truth, this integration may not be required.

Installation

Prerequisites

Before setting up the integration, ensure:

• You have admin permissions in Rippling to install and authorize API access.

• You have permissions in Drivetrain to configure integrations.

How to Install the Integration

Log in to Drivetrain: Navigate to Data → + Add Data Source → HRIS → Rippling.

Choose “API Key”

To connect using an API key, first generate a key in Rippling, then paste it into the Drivetrain connector.

How to get your Rippling API key

Using Rippling’s API requires the Rippling API Key Package. If it is not already enabled on your account, contact your Rippling account representative to turn it on.

1. Sign in to your Rippling account at app.rippling.com.

2. Go to Company Settings → API access. (Alternatively, open Tools → Developer → API Access.)

3. Click Create API key.

4. Enter a Description (for example, Drivetrain Integration).

5. Under Permissions, grant Drivetrain read access to all of the following scopes. Missing any one of these (for example level) will cause the sync to fail:

   • compensation

   • user

   • department

   • teams

   • level

   • employment_type

   • manager

   • legal_entity

   • custom_fields

Grant read access for every scope listed above. A common cause of failed syncs is the level scope not being enabled, so please double-check it is included before saving the API key.

1. Click Save — you will be redirected to the API access page.

2. Copy the generated API token and store it securely (you may not be able to view it again).

Then paste the API token into the Drivetrain Rippling connector’s API Key field and click Submit to start the sync.

Data Flows

What data flows are available?

The integration supports the following flows:

1. Employee Directory Sync Imports employee profiles, status, start/end dates, departments, and reporting structure.

2. Job Sync Imports job titles, job levels.

3. Org Structure Sync Imports departments and managers for modeling reporting and cost allocation.

When and how do data flows trigger?

• Automatic Syncs: Trigger based on the frequency chosen during setup (default is daily; other sync frequencies can also be set).

• Event-based Changes (Rippling): When changes occur in Rippling, such as new hires, terminations, promotions, Drivetrain picks them up during the next scheduled sync.

• Manual Sync: Users can trigger an immediate resync anytime from the Drivetrain Data page.

How to manually trigger a sync

1. Go to Data page

2. Click Resync icon

3. Select Rippling from the list and click Sync

   

FAQs

What happens if I update an employee field in Rippling?

The next scheduled sync will automatically update the employee record in Drivetrain. You can also manually trigger a sync for an immediate refresh.

Does Drivetrain write any data back to Rippling?

No. The integration is read-only. Drivetrain does not modify or push data into Rippling.

Can I choose which fields to sync?

Yes. During setup, you can select the entities and fields relevant to your planning models.

What if a field required by my Drivetrain model does not exist in Rippling?

Please contact your customer success manager. A joint request to access the scope(s) needed needs to raised with Rippling.

If I change sync frequency later, will it affect my existing data?

No. Only the timing changes. Historical data stays intact.

The sync failed—what should I do?

The reason for sync failure is displayed on the dataset page for Rippling.

Common issues are:

• Rippling access needs to be reauthorized.

• One or more of the required fields were deleted or renamed or the datatype was modified in Rippling—you can correct this from the Manage Schema page.

In case of additional queries, please reach out to your dedicated Customer Success Manager (CSM) or send an email to [e-mail].

Support

If you encounter any issues not covered here, please contact your dedicated Customer Success Manager (CSM) or reach out to [e-mail].