Rippling with Flexopus: Automatically synchronize absences
With the Rippling integration in Flexopus, employee absence data flows automatically into workspace planning—eliminating manual entry and data silos.
What is Rippling synchronization?
The Rippling integration is a one-way data interface: absence information from Rippling is automatically transferred to Flexopus. Flexopus reads the absence data from Rippling and saves it for the respective user accounts.
Only information relevant to space planning is transferred: employee ID, absence period (start and end date), status, and optionally the absence type (e.g., vacation, illness, parental leave). The data is processed via a certified integration provider and synchronized regularly.
What is the purpose of the integration?
The integration ensures that absences from Rippling are directly visible in Flexopus, without employees or administrators having to enter data twice.
Typical use cases for the integration:
- View absence status: Approved absences from Rippling are automatically displayed in the relevant person's Flexopus profile. Colleagues can see at a glance who is available.
- Improve attendance planning: The Flexopus overview shows who is working in the office, who is remote, and who is absent. This makes planning joint in-office days easier.
- Optimize resources: Absence data helps to realistically estimate available workspaces and manage bookings effectively.
How easy is the integration?
Setting up the Rippling integration is straightforward and requires no technical expertise. As an administrator, select the HRIS integration in the Flexopus settings and connect your Rippling account. After granting the required API permissions once, synchronization runs automatically in the background.
A complete step-by-step guide for setup can be found in our Help Center.
What are the benefits of the integration?
- Automatic synchronization: Absence data from Rippling is updated in Flexopus regularly without manual effort.
- Team transparency: All employees see at a glance who is available – directly in the Flexopus interface.
- Fewer errors: Automatic data reconciliation eliminates manual entries and associated sources of error.
- Data protection compliant: Only the absence data necessary for planning is transferred. Sensitive details like the exact reason for absence can optionally be hidden.
- Seamless integration: The integration fits into your existing IT infrastructure – without additional software or complex configurations.
- Additional module: The HRIS integration is available as an optional module and upon request for all Flexopus customers.
Additional integrations
.svg)
Questions and answers
What data is transferred from Rippling?
Only absence-related data is synchronized: employee ID, approval status, start and end times, and optionally the absence type (e.g., vacation or sick leave). Personal or confidential information from Rippling is not transferred. You can also configure whether the absence type is displayed or simplified to "absent."
What happens if an absence is changed or deleted in Rippling?
The integration synchronizes data regularly. Changes or deletions in Rippling are automatically applied in Flexopus during the next synchronization. Manual adjustments in Flexopus are not required.
Can absences be edited directly in Flexopus?
No. The synchronization is one-way: Flexopus reads data from Rippling but does not make any changes to it. Absences must still be managed directly in Rippling.
Is the HRIS integration included in the standard subscription?
The HRIS integration is an optional add-on module and is not included in the standard subscription. It is available to all Flexopus customers upon request. If you are interested, please contact the Flexopus team.
How is data protection ensured during transmission?
Data transfer is handled via a certified external integration provider. Only the data required for displaying absences in Flexopus is transmitted. Processing is carried out in compliance with GDPR.