HiBobSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The HiBob connection the step signs in with. |
| First nameRequired | text |
| SurnameRequired | text |
| Work e-mailRequired | Bob requires this to be unique in the company — it is the person's login. |
| SiteRequired | Must be a value from Bob's site list — the display value, not the id. The Read company list node with site shows them. |
| Start dateRequired | YYYY-MM-DD. |
| Department | text |
| Job title | text |
| Manager | The manager's employee id, as Bob's own work.manager field holds it. |
| Other Bob fields | Any other Bob field, in the same nested shape a search answer uses — for example {"home":{"mobilePhone":"0612345678"}} or {"userData":{"custom":{"field_17257492283795":"…"}}}. The List employee fields node gives you every id. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `hibob`) |
firstName | text |
surname | text |
email | text |
site | text |
startDate | text |
department | text |
title | text |
manager | text |
extraFields | object (any keys), by default {} |
Output
| Field | Type |
|---|---|
employeeId | string |
employee | object |
Sample output, and the expression for each field
- employee
- id"33328"
- employeeId"33328"
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"department": "",
"email": "<work e-mail>",
"extraFields": {},
"firstName": "<first name>",
"manager": "",
"site": "<site>",
"startDate": "<start date>",
"surname": "<surname>",
"title": ""
},
"label": "Create employee",
"type": "hibob.createEmployee",
"version": 1
}