In past articles, I have covered various HR applications and the benefits of native integrations with Jira Service Management (Refer to Appendix for past articles). In this article, I will cover Hi Bob, its integration approach, possibilities, and importing HR data into Assets.
About Hi Bob
Bob is a modern HR and employee management platform designed to streamline HR processes and enhance employee engagement. It offers a centralized employee database, time and attendance tracking, onboarding and offboarding workflows, performance management tools, and features for employee engagement such as surveys and recognition programs. Bob integrates with payroll systems and other business tools, provides robust analytics and reporting capabilities, ensures regulatory compliance, and maintains data security. Its user-friendly interface and mobile app make it accessible for businesses of all sizes, supporting scalable growth and efficient HR operations.
Integrating Hi Bob
Bob provides a comprehensive API to perform various HR services. Please refer to this link for Bob API documentation. Bob API uses Bob’s Service Users for taking API actions. Multiple service users can be created, each with unique permissions, depending on the API you want to access. Please refer to this link for creating an API Service User in Bob.
OnLink supports native integration with Bob. Using the API Service token, a connection is established from within Jira Service Management.
Using Hi Bob Webhooks
Bob provides the ability to subscribe to events that occur in the system and provide a Webhook URL, which will be called whenever an event occurs. Each event will send the information about the event in the event’s payload. Refer to this link for Webhooks documentation. Here are some common events that we can subscribe to:
| Event | Type | Description |
|---|
| Updated | employee.updated | Triggered when updating employee fields or when adding and updating employee tables. |
| Created | employee.created | Triggered when an employee profile is created in Bob. |
| Deleted | employee.deleted | Triggered when deleting the employee’s profile. |
| Inactivated | employee.inactivated | Triggered when setting an employee to be on leave or terminated, and the effective date of the termination is reached. |
| Activated | employee.activated | Triggered when granting access to an employee, and the effective date is reached. |
| Joined | employee.joined | Triggered when granting access to an employee, and the effective date is reached. |
| Terminated | employee.left | Triggered when an employee’s termination effective date is reached and their state is either ‘Terminated’ or ‘Garden leave’, whichever occurs first. |
| On Leave | employee.temporaryLeave | Triggered when setting an employee to be on leave. |
OnLink supports webhooks to capture these events and create respective tasks in Jira Service Management.
HR Service Task Management
Using OnRamp, now we can manage all the HR Workflows such as:
- Employee Onboarding and Offboarding
- Contractor Onboarding and Offboarding
- Contractor to Full time and vice versa
- Employee Relocation or Transfer
- Role Changes
Specific tasks can be created, assigned and automated. E.g We can create a task for Order Laptop and assign it to a specific IT resource. In a similar vein we can create a task for software provisioning and assign it to the IT access team. OnRamp supports setting due dates and task conditions. E.g I can set a due date for software provisioning to be 3 days before hire date of the new employee.
Importing HR data from Bob to Assets
Assets in Jira Service Management can serve as a central repository to manage employee data and organization data. When this is coupled with IT Hardware and Software assets you can get a 360 view of the employee data and associated assets.
OnLink provides a configurable mapping and scheduling options to easily import HR data from Bob.
If you are using Hi Bob as your HRIS, I highly encourage to give this solution a try and let us know your feedback.
Appendix
