> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/hris/hibob.md).
# HiBob
HiBob (Bob) is a modern HR management platform designed for dynamic, distributed workforces. Connecting Bob to Harmony enables automated IT provisioning based on HR events, intelligent employee lifecycle management, and seamless synchronization of organizational data for optimal IT operations.
A demo mock provider is also available, allowing teams to test and validate employee sync configurations before connecting a live HiBob account.
#### What the HiBob integration enables
| Capability | Description |
| --------------------- | ------------------------------------------------------------------------------ |
| Employee Data Sync | Sync employee profiles, departments, roles, position levels, and org structure |
| Automated Onboarding | Trigger IT provisioning when new employees are added |
| Offboarding Workflows | Automate access revocation when employees are terminated |
| Department Routing | Route IT requests based on employee department and location |
| Lifecycle Automation | Automate IT tasks for role changes, transfers, and promotions |
#### Prerequisites
* **HiBob Administrator Access**: Admin role with API access permissions
* **HiBob Subscription**: Active Bob account for your organization
* **Harmony Account**: Active Harmony workspace
#### Connect HiBob to Harmony
**Step 1: Create Service User in HiBob**
1. Log in to Bob at `https://app.hibob.com`
2. Navigate to **Settings** > **People** > **Service users**
3. Click **Add service user**
4. Configure:
* **Name**: "Harmony Integration"
* **Email**: `harmony-integration@yourcompany.com`
* **Access level**: System Administrator (or custom role)
5. Select **Data permissions** (view permissions for):
* **people - About**: View selected employees' About sections
* **people - Basic info**: View selected employees' Basic info sections
* **people - Email**: Edit selected employees' email addresses
* **people - Employment**: View selected employees' Employment sections
* **people - User data**: View selected employees' User data sections
* **people - Work**: View selected employees' Work sections
* **people - Work contact details**: View selected employees' Work contact details sections
6. Click **Create** and copy the **Service User ID** and **Token**
**Step 2: Navigate to Integrations**
1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **HiBob** under **HRIS** and click **Connect**
**Step 3: Enter API Credentials**
1. Enter your **Service user ID**
2. Enter your **Service user token**
3. Click **Connect**
#### What Harmony Syncs
**From HiBob:**
* Employee profiles and personal information
* Employment details (job title, department, employment type)
* Organizational data (manager, direct reports, hierarchy)
* Work information (location, phone, time zone)
* Employment dates (start date, end date)
* Custom fields relevant to IT operations
* Department structure and sub-departments
* Status changes (active, terminated, etc.)
* Position level (Individual Contributor, Management, Senior Management, or Executive Leadership), mapped from HiBob's org level data
#### Position Level Sync
Harmony automatically syncs each employee's position level from HiBob into their Harmony profile. Levels are standardised into four categories mapped directly from HiBob's org level data:
| HiBob Org Level | Harmony Position Level |
| ---------------------- | ---------------------- |
| Individual Contributor | Individual Contributor |
| Management | Management |
| Senior Management | Senior Management |
| Executive Leadership | Executive Leadership |
This means your support workflows and automations can reference an employee's seniority tier without any manual data entry.
#### Using HiBob Blocks in Agent Workflows
HiBob blocks in the Agent workflow builder expose proper inputs and outputs, making it straightforward to connect them to other steps in your workflows. You can:
* **Pass data into HiBob blocks** - supply context from earlier steps to filter or enrich queries
* **Use results downstream** - feed employee data returned by a HiBob block into subsequent workflow logic
* **Resolve employees automatically** - blocks support Employee ID resolution, so Harmony can identify and look up the right employee record as part of a running workflow
HiBob blocks behave consistently with all other blocks in the builder, giving you a reliable and predictable building experience.
#### Use Cases
Automated New Hire Provisioning
Trigger complete IT setup when HR adds new employees to HiBob
Role-Based Access Management
Automatically adjust access permissions when employee roles change
Department-Based Request Routing
Route IT tickets to appropriate teams based on employee department
Seamless Offboarding
Automate access removal and asset recovery when employees are terminated
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.harmony.io/integrations/hris/hibob.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.