This article describes the actions available when you connect Rippling to HappyFox Workflows, and lists the leave management operations you can automate with this integration.
Triggers
The Rippling integration does not provide triggers. Workflows that include Rippling actions are started by a HappyFox Help Desk trigger or another connected app.
Actions
| Action | What it does |
|---|---|
| Apply Leave Request | Submits a new leave request in Rippling on behalf of an employee. |
| Process Leave Request | Processes an existing leave request in Rippling — for example, approving or declining a pending request. |
Use cases
Submit a leave request when an employee raises an HR ticket: When an employee submits a leave request through HappyFox Help Desk, automatically use Apply Leave Request to submit the corresponding request in Rippling — removing the manual step of re-entering the request in two systems and ensuring the HRIS record is created at the point the ticket is raised.
Approve a leave request when an HR ticket is resolved: When an HR agent reviews and approves a leave request ticket in HappyFox Help Desk, automatically use Process Leave Request to approve the corresponding request in Rippling — keeping the approval action and the HRIS update in sync without requiring a separate step in Rippling.
Decline a leave request and close the ticket together: When an HR agent declines a leave request based on staffing or policy grounds, automatically use Process Leave Request to decline the request in Rippling at the same time as the ticket is updated — ensuring the employee's HRIS record reflects the decision without a manual admin step.
Process bulk leave requests during peak periods: When a category of tickets — such as annual leave requests submitted around a public holiday — are resolved in HappyFox Help Desk, automatically process each corresponding Rippling leave request in sequence — reducing the administrative backlog during high-volume periods without agents switching between systems.