The Rippling integration automates employee lifecycle management by syncing HR data directly into Atomicwork, eliminating manual updates across systems.
With this integration, your IT and HR teams can automate onboarding and offboarding workflows, sync employee data in real time, and manage leave requests. This reduces data errors, accelerates employee transitions, and ensures access provisioning stays in sync with HR changes.
Usescases
By connecting Rippling, you can automate:
Leave management: Allow employees to check leave balances and request time off through Atom. You can also automatically create, approve, reject, or cancel time-off requests.
Worker management: Retrieve employee, department, and work location data to power workflows.
Permissions
To connect Rippling with Atomicwork, you need:
Org admin access on Atomicwork
An API access token from the Rippling developer platform or admin console. Ensure your token has the following scopes:
Permission | Purpose |
workers.read | To sync user profiles and ensure workflows have access to the necessary user data. |
departments.read | To retrieve organizational department data. |
work_locations.read | To retrieve work location data. |
leave_requests.read | To list leave requests for workers and get details of specific leave requests. |
leave_requests.write | To create new time-off requests and approve, reject, or cancel leave requests. |
leave_balances.read | To check remaining leave balances for workers. |
leave_types.read | To list available leave types (Vacation, Sick, WFH, etc.). |
Setup
Generate a new API token in Rippling admin console:
Log in to Rippling as an admin and click on Tools > Developer
Navigate to API Tokens > Create API Token
Enter a name for your token and click on Continue
Select the required permissions and click on Save
Copy the API token and store it securely
In your Atomicwork account, navigate to Settings > App Store > Rippling.
Enter your API key and click on Test to test the connection.
Click on Connect to activate the integration.
Supported workflow actions
Once connected, you can automate the following Rippling actions within your Atomicwork workflows:
Action | Description |
Get departments | Retrieve organizational department data from Rippling. |
Get users | Retrieve user information from Rippling. |
Get work locations | Retrieve work location data from Rippling. |
List workers | List all workers with pagination support. |
Get worker by email | Retrieve a specific worker's details using their email address. |
List leave requests | List leave requests for a specific worker. |
Get leave request | Get details of a specific leave request. |
Create leave request | Create a new time-off request for a worker. |
Update leave request | Update an existing leave request (approve, reject, or cancel). |
Get leave balances | Retrieve leave balances for a worker in minutes. |
Get leave types | Get all configured leave types (such as Vacation, Sick, or WFH). |
Call API | Execute a generic API call to any Rippling endpoint for custom operations. |
Troubleshoot common errors
If you encounter issues while using the Rippling integration, review the following common scenarios:
Error | Cause | Resolution |
"access_token is null" | The integration configuration is missing the access token. | Re-enter your token in the integration settings. |
401 Unauthorized | Your access token has expired or been revoked. | Generate a new token from the Rippling admin console and update your connection. |
Leave request status errors | You can only change the status of PENDING leave requests. | Note that you can only update the status of pending requests. You can still update comments on non-pending requests. |
Pagination limits | Attempting to retrieve more than the maximum allowed items per page. | All list endpoints use cursor-based pagination. Use the cursor from the previous response's |