> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/hris/hibob.md).
# HiBob
Connect HiBob to Siit to sync your employee directory and lifecycle events in real time — so onboarding, offboarding, and every request in Siit uses up‑to‑date HR data from Bob.
### What you get
* **Live People directory** — Bob employees, departments, sites, and reporting lines appear in Siit automatically.
* **Lifecycle triggers** — Start date, End date, Probation end, Work anniversary, and Birthday all flow into Siit as workflow triggers.
* **Manager chain** — Bob's reporting structure powers auto‑selected approvals in Siit workflows.
* **Custom fields** — import any custom Bob field into Siit (cost center, legal entity, work pattern, etc.).
* **Pre‑hires** — future employees with a start date in Bob appear in Siit ahead of Day 1, so pre‑boarding workflows can run early.
### What syncs from HiBob
| Category | Fields |
| --------------- | --------------------------------------------------------------- |
| Identity | Display name, first name, surname, work email, employee ID |
| Role | Job title, department, team, job level |
| Org structure | Manager, site (location), company / legal entity |
| Employment | Employment type (employee, contractor), status (active, leaver) |
| Lifecycle dates | Start date, termination date, date of birth |
| Custom | Any custom Bob field you select during mapping |
Work email is used as the canonical identifier across systems.
### Before you connect
* You'll need **HiBob admin permissions** to approve the connection.
* Make sure work email is filled in for every active employee in Bob.
* Decide whether Bob or your IdP should be the source of truth for overlapping fields (title, department). You can configure this after connecting in **Settings → Context management → People fields**.
#### Connect HiBob
1. In Siit, go to **Settings → Workspace → Integration library**.
2. Find **HiBob** in the HR systems section and click **Connect**.
3. When asked how you'd like to authenticate, choose **Use my credentials (recommended)**.
4. Review the data Siit will have read access to, then click **Next**.
5. On the **Connect Hibob** screen, check that you're about to connect your HiBob production account, then click **Open window**.
6. In the new window, sign in to HiBob with your admin account and approve the connection.
7. You're sent back to Siit, which runs an initial import and shows a preview of imported people.
8. Review the field mapping and click **Finish setup**.
**What Siit can read in HiBob**
Siit gets read access to employees, employments, time off, time off balances, groups, bank information and locations.
> **Good to know**: Siit only reads data from HiBob. It never edits anything in Bob. If nothing happens when you click **Open window**, check that your browser isn't blocking pop-ups.
### After the connection
* **Check your People list** in Siit — the count should match your active + upcoming employees in Bob.
* **Set source of truth** in **Settings → Context management → People fields**, picking HiBob for HR‑owned fields.
* **Map custom fields** — in **Settings → Workspace → Integration library → HiBob**, add any custom category or field you use in Bob.
* **Build workflows** — start with a Day‑1 onboarding workflow using the Start date trigger.
### Sync frequency
HiBob data refreshes automatically every few hours.
### Common workflows
**Day‑1 onboarding.** *Trigger: Start date. Actions: create IdP account, assign app bundles by department, order equipment, DM the hiring manager.*
**Offboarding on leave date.** *Trigger: End date. Actions: revoke sessions, remove app access, open an equipment return request, send handover reminder to manager.*
**Welcome message by site.** *Trigger: Start date, Condition: site = Paris. Action: send the local welcome pack.*
### Troubleshooting
**Manager field empty.** In Bob, confirm the employee has a manager set in the **Work** category. Siit reads from that field.
**Missing employees.** Make sure the employee has a work email in Bob and is either active or has an upcoming start date. If they still don't show up, reconnect HiBob from the Integration library.
**Custom field not imported.** Make sure the custom field is available through the HiBob API, then re-run the mapping in Siit.
**Sync stopped or "Re-link needed".** Reconnect HiBob from **Settings → Workspace → Integration library → HiBob**.
>
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.siit.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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
