> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# HiBob workflow actions for time-off automations

> Use HiBob workflow actions in Ravenna to check employee time-off balances and create time-off requests directly from tickets and automations.

Use HiBob actions in workflows to check employee time-off balances and create time-off requests directly from Ravenna.

## Actions

<AccordionGroup>
  <Accordion title="Get Time-off Balance">
    Retrieves the current time-off balance for an employee from HiBob. Returns balances and usage across all time-off policy types.

    **Output data:**

    * Vacation balance and used hours
    * Sick leave balance and used hours
    * Personal time balance and used hours
    * Jury duty balance and used hours
    * Volunteer time balance and used hours
    * Bereavement leave balance and used hours

    **Common use cases:**

    * Check remaining PTO before approving time-off requests
    * Display balance information in agent responses
    * Validate sufficient balance before creating time-off requests
    * Include balance details in approval workflows
  </Accordion>

  <Accordion title="Request Time Off">
    Submits a time-off request in HiBob on behalf of an employee using HiBob's native time-off API. Use this action to let employees file PTO from Slack, web tickets, or automated approval workflows without leaving Ravenna.

    **Input fields:**

    * `User` - Ravenna user the request is for. Ravenna resolves this to the linked HiBob employee using synced HRIS data
    * `Policy Type` - Time-off policy to request against (for example, Vacation, Sick). Options are pulled from your HiBob policy types
    * `Start Date` - First day of the time-off period
    * `End Date` - Last day of the time-off period
    * `Approver` - Optional. Ravenna user who should approve the request in HiBob. When omitted, the request is submitted with manager approval skipped
    * `Description` - Optional reason or note attached to the request. Supports rich text formatting (bold, lists, links) so you can include structured context for approvers

    **Output data:**

    * `requestId` - HiBob time-off request ID, useful for follow-up actions or audit logging

    **Common use cases:**

    * Submit time-off requests from a Slack or web ticket form
    * Automate PTO submissions after a manager approves in Ravenna
    * File time off as part of onboarding or leave-of-absence workflows

    **Example**

    Pair `Get Time-off Balance` with `Request Time Off` to validate balance before submitting:

    ```yaml Example workflow theme={"system"}
    - action: HiBob - Get Time-off Balance
      input:
        userId: {{ ticket.requester.id }}
    - action: HiBob - Request Time Off
      input:
        userId: {{ ticket.requester.id }}
        hibobPolicyTypeId: Vacation
        startDate: {{ ticket.fields.start_date }}
        endDate: {{ ticket.fields.end_date }}
        approver: {{ ticket.requester.manager.id }}
        description: {{ ticket.fields.reason }}
    ```
  </Accordion>
</AccordionGroup>

## Semantic fields

Employee data synced from HiBob is available as semantic fields in workflows. You can reference these fields using dynamic values to personalize workflow actions.

**Available fields:**

* Employee name and email
* Job title
* Department
* Manager
* Hire date
* Employment status

<Callout icon="link" color="#6B7280">
  Learn more about [building workflows](/documentation/automate/workflows/publish)
</Callout>