Rippling

Unthread's Rippling integration helps keep employee support workflows accurate by connecting two parts of your HR system:

• HRIS employee sync: keeps employee profile, status, and group data current in Unthread as Rippling changes.
• Time off request sync: brings Rippling leave requests into Unthread so assignment logic can avoid teammates who are currently away.

You can use either component on its own, but they work best together. Directory sync keeps Unthread's user records current, while time off sync adds availability context when work is assigned.

What the HRIS employee sync does

The HRIS sync connects Rippling to Unthread through the HR Directory Sync integration. Once connected, Unthread receives employee updates in real time, including new employees, profile changes, deactivations, group changes, and group membership updates.

Depending on the fields available from Rippling and mapped during setup, Unthread can use employee data such as:

• Name and email
• Job title
• Department
• Employee number
• Organization, division, and cost center
• Location fields
• Manager
• Employee type and start date
• Directory groups and group membership

Why it matters

Real-time employee data makes Unthread more reliable as your company changes. New employees can be recognized automatically, departing employees can be marked inactive, and user groups can stay aligned with the source of truth in Rippling.

This is especially useful for internal support teams that route, prioritize, or report on work by department, location, group, manager, or employee attributes.

What the time off sync does

The Rippling PTO integration syncs leave requests from Rippling into Unthread. Unthread matches time off requests to users by employee email and uses active, approved PTO as availability context.

When a teammate is currently out on approved leave, Unthread can factor that into assignment checks so new work is routed to someone available.

Why it matters

Time off sync helps teams avoid assigning urgent requests to people who are away. It reduces manual status updates, keeps coverage cleaner, and helps support queues continue moving when teammates are on vacation, sick leave, or other approved time off.

Before you start

You need:

• Admin access in Unthread.
• Permission to connect HRIS or directory sync in Rippling.
• A Rippling API token with read access to employees and leave requests for PTO sync.

Set up HRIS employee sync

1. In Unthread, go to Settings > Integrations.
2. Open the HR Tools section.
3. Select HR Directory Sync.
4. Click Connect.
5. Open the generated configuration link.
6. In the setup flow, select Rippling as the HRIS or directory provider.
7. Complete the Rippling authorization and field mapping steps.
8. Return to Unthread after the setup flow completes.

After the directory is connected, Unthread will begin receiving real-time employee, group, and membership updates from Rippling.

Set up Rippling time off sync

1. In Rippling, create an API token with read access to:
   • Employees
   • Leave requests
2. In Unthread, go to Settings > Integrations.
3. Open the HR Tools section.
4. Select Rippling PTO.
5. Click Connect to Rippling.
6. Paste your Rippling API token into the API Token field.
7. Choose whether to Automatically sync PTO daily.
8. Set the sync window:
   • Look back days: how many past days Unthread should refresh. The default is 30.
   • Look ahead days: how many future days Unthread should sync. The default is 180.
9. Save the integration.

Unthread validates the token before saving it. After the integration is connected, Unthread starts an initial PTO sync in the background.

Recommended settings

For most teams, keep automatic daily sync enabled and use the default sync window:

• Look back days: 30
• Look ahead days: 180

These defaults keep current and upcoming leave data fresh while still refreshing recent changes, cancellations, or corrections.

How matching works

Unthread matches Rippling time off requests to Unthread users by employee email. If a Rippling employee's work email matches a user in Unthread, that time off request is associated with the user.

If a request cannot be matched to a user, Unthread still records the request data from Rippling, but it cannot use that request for that user's assignment availability until the employee email matches a Unthread user.

Troubleshooting

The Rippling PTO token is rejected

Make sure the token has read access to both employees and leave requests. Unthread validates both endpoints when the token is saved.

PTO is not affecting assignments

Confirm that:

• The Rippling PTO integration is enabled.
• The employee's Rippling email matches their Unthread user email.
• The leave request is approved.
• The leave request is active during the time work is being assigned.
• The request falls within the configured lookback/lookahead sync window.

Employee records are not updating

Confirm that:

• HR Directory Sync is connected and enabled.
• The Rippling directory setup was completed in the configuration flow.
• The expected fields are shared or mapped from Rippling.
• The employee exists in the connected directory and has a valid email address.

FAQ

Do I need both HR Directory Sync and Rippling PTO?

No. You can connect only the component you need. However, using both gives Unthread the most accurate picture of who employees are and whether they are available.

Does Unthread create PTO requests in Rippling?

No. Unthread reads time off requests from Rippling. Employees should continue requesting and managing time off in Rippling.

Which time off requests affect assignment availability?

Active, approved leave requests affect assignment availability. Other synced requests may be stored for context, but they do not block assignment unless they are approved and active for the relevant time.

How often does PTO sync?

If automatic sync is enabled, Unthread syncs PTO daily. An initial sync runs when the integration is connected.