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. |
Actions
Each action below lists the fields you configure, along with whether each field is required.
Apply Leave Request
Submits a new leave request in Rippling on behalf of a specific employee (role). The leave type is selected from a fixed list of company leave types.
| Field | Description | Validation |
|---|---|---|
| Role | The Rippling role ID or employee identifier for whom the leave request is being submitted. | Required · Text |
| Start Date (YYYY-MM-DD) | The first day of the leave period (for example, 2025-08-01). |
Required · Text |
| End Date (YYYY-MM-DD) | The last day of the leave period (for example, 2025-08-05). |
Required · Text |
| Company Leave Type | The category of leave being requested. Allowed choices: Vacation leave, Sick leave, Jury Duty leave. |
Required · Selection (pick one) |
| Leave Type Policy | The specific leave policy under which the request should be filed. Required when Managed By is PTO or LEAVES; not required when Managed By is TILT. |
Optional · Text |
| Reason | A brief description explaining the purpose of the leave. | Optional · Text |
| Managed By | The system or policy framework that manages this leave type. Determines whether a Leave Type Policy is needed. Allowed choices: PTO, LEAVES, TILT. |
Optional · Selection (pick one) |
Note: If Managed By is set to
PTOorLEAVES, you must also provide a Leave Type Policy — the action fails without it. If Managed By isTILT, leave Leave Type Policy blank.
Process Leave Request
Approves or declines an existing Rippling leave request by its ID.
| Field | Description | Validation |
|---|---|---|
| Leave Request ID | The Rippling ID of the leave request to process. | Required · Text |
| Action (Approve/Decline Request) | The decision to apply to the leave request. Allowed choices: APPROVE REQUEST, DECLINE REQUEST. |
Required · Selection (pick one) |
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.