RIPPLING SETUP GUIDE
Time, leave and schedules.
Each with a clear review.
Connect the right company, match the right people and verify each workflow before relying on the result in Rippling.
Connect the intended Rippling company
Open Company Settings → Integrations → Rippling.
- Read the displayed setup requirements. Have your Rippling administrator provide a dedicated API token with the company-wide access required by the workflows you intend to use.
- Enter the Rippling company ID and token in the connection form. Confirm the token owner's access and select Verify and save connection.
- Save the company feature preferences for the data you want to share. Each optional workflow also has its own settings.
- Confirm the recorded time zone used by existing TakeUrTime clock records and select Save time settings.
The saved token is encrypted and is not displayed again. Replace it when revoked or when its owner changes. Disconnecting in TakeUrTime does not revoke the token in Rippling; coordinate that with your administrator.
Match workers and recorded break types
- Select Load Rippling workers and choose the matching TakeUrTime employee and active Rippling worker.
- Check the full legal name and an email; they must match.
- Verify that the worker uses Rippling Time & Attendance and does not require job codes. This workflow sends timestamped shifts without job codes.
- Confirm and select Verify and save employee match.
- For that employee, select Load Rippling break types. Match each recorded paid or unpaid type to the corresponding Rippling type.
- Verify the worker is assigned to the appropriate Rippling break policy, then select Save employee break mapping.
The provider's break-type list does not confirm that the selected worker is assigned to that policy. Verify assignment and paid/unpaid treatment in Rippling before saving the match.
Review approved time and breaks
- Choose completed dates that include entire shifts, and select up to 25 matched employees.
- Select Prepare Rippling time review.
- Review each employee/date, payable hours, break totals and proposed action. Expand supporting records to compare previous and proposed timestamps and break types.
- Confirm that the period is unprocessed and nobody will edit or approve it in Rippling while delivery runs.
- Select Queue reviewed drafts. Follow Delivery history and use Check live Rippling results to compare the destination.
Shifts are grouped by employee and calendar date. Overnight shifts and breaks split at midnight. Full timestamped shifts are sent; Rippling deducts unpaid breaks, while paid breaks remain in payable time. This time workflow excludes PTO, holidays, monetary adjustments and local pay rates.
How are previously sent time corrections handled?
Eligible draft corrections update the original entry. Approved, paid, externally changed or removed entries require review in Rippling. Do not repeatedly send a correction over a provider change. Inspect the previous and proposed records and coordinate the correction there.
Why do overtime totals differ?
The review shows TakeUrTime's hour classifications for comparison, but Rippling calculates overtime using its own policies. Verify the worker's Rippling rules and the delivered timestamps and breaks before payroll approval.
Deliver approved leave and cancellations
Use the separate Rippling leave and balances section. This does not add PTO to the worked-time delivery above.
- Enable Deliver approved leave, verify the time-zone and worker calendar dates, and select Save leave preferences.
- Select Load Rippling leave types. Map paid types to paid types and unpaid types to unpaid types, checking employee policy eligibility.
- Choose the matched employee and dates, then select Find approved leave and cancellations.
- Prepare and inspect the saved leave review. Check each day, its hours, the destination type and available balance in Rippling.
- Confirm that the affected payroll is unprocessed and the provider requests will not be edited during delivery. Select Queue reviewed leave.
- Use Check live leave results and Delivery history to verify the outcome.
One Rippling request is created per approved calendar day using that day's hours. Private reasons and clock intervals stay in TakeUrTime. Pending requests and pending amendments are not delivered.
TakeUrTime controls approvals for requests created through this integration. Verify that it is authorized to manage those requests for the selected Rippling leave type.
Compare balances without overwriting them
Enable Show Rippling balances if you want provider values alongside TakeUrTime balances. Select an employee, then choose Show last balance snapshot or Refresh from Rippling.
Neither balance is overwritten. Provider hours and days are shown separately. Different policies, units or treatment of future leave can produce different totals; do not assume a provider day equals the configured TakeUrTime full-day hours.
When totals differ, review when the provider values were refreshed, the leave type, hours versus days and future approved requests before making a local balance adjustment.
Share published schedules
- Enable Employees and Schedules in the company feature controls.
- In Rippling published schedules, choose whether to include employee-visible notes. They are off by default. Confirm the recorded time zone and save schedule preferences.
- Select Load Rippling schedules. Map each TakeUrTime worksite to an existing Rippling schedule. Unassigned worksites have a separate mapping.
- Confirm the schedule's time zone and that the intended employees are members, then select Save schedule mapping.
- Choose dates and select Find published shifts and corrections. Review up to 100 results at a time.
- Inspect the published assignment, worksite and shared notes. Confirm nobody will edit the affected shift during delivery, then select Queue published assignment.
- Use Check live assignment and Delivery history to verify the result.
| Shared or handled | Kept separate |
|---|---|
| Published assignments, titles and planned unpaid-break minutes. Employee-visible notes only when enabled. | Manager-only notes, client/contract details and worked hours are not included. |
| Reassignment updates the original Rippling assignment. | Moving a delivered shift to another provider schedule requires manual correction. |
Draft edits stay in TakeUrTime until published. Planned break minutes are reference text, not timed break records. Unresolved linked cancellations and moved shifts may appear outside the chosen dates so they can still be resolved.
Complete schedule cancellations manually when prompted
This integration uses a manual completion workflow for removing a delivered schedule assignment.
- Open the saved schedule review and identify the exact original Rippling assignment and company.
- Remove that assignment in Rippling.
- Return to TakeUrTime, enter the removal reference or explanation and confirm that you removed the exact assignment.
- Select Record manual cancellation.
Check results and resolve problems
New writes require a saved review less than 30 minutes old. Original reviews, receipts and manual completion records remain available. If source data or mappings change, prepare a fresh review as instructed.
A delivery timed out or its outcome is uncertain.
Use Reconcile in Delivery history to check the original operation. Do not create another shift, request or assignment to work around an unknown result. An empty lookup does not prove failure. See the recovery guide.
A connection worked before but now fails.
Have your administrator check token validity, the owner's current access and permissions for the selected workflow. Do not paste tokens into support messages. After replacing credentials, review mappings and outstanding results before sending again.
A leave request did not appear in the delivery list.
Check approval status, employee and leave-type matches, dates and saved leave preferences. Pending amendments are not delivered. For an approved amendment, complete original cancellations before preparing the replacement.
A schedule edit is missing.
Confirm the edit was published, the worksite mapping is correct and the employee belongs to the Rippling schedule. Check whether a move requires manual correction rather than another queued assignment.
The provider result differs from the review.
Compare the exact worker, dates, original record and proposed action. Check whether someone changed or approved the provider record while delivery was running. Keep the delivery held until the mismatch is understood.
What should I include when asking for help?
Provide the workflow, connected company, worker, affected dates, review/delivery ID, exact error and provider record reference. Exclude API tokens, passwords and other secrets.