Install from the HiBob Marketplace
In the dashboard, HiBob appears as a row under Settings → People → Connect with the description “Allows Risotto to manage HR operations like addresses and time off requests” and an Install button on the right. Risotto connects to HiBob through the HiBob Marketplace, it handles authentication and persists OAuth tokens automatically.1
Start the install from Risotto
In the dashboard, go to Settings → People → Connect and click Install next to HiBob. You’ll be redirected to the HiBob Marketplace.
2
Approve the install in HiBob
Sign in to HiBob as an admin if prompted, then approve the requested
permissions for the Risotto app. HiBob redirects you back to the dashboard
once the install is complete.
3
Confirm the connection
The HiBob row in People Connect updates to show the integration is connected. A toast confirms
HiBob connected successfully.Only HiBob admins can install marketplace apps. If the Install button
redirects you to HiBob without an approval screen, ask an admin in your
workspace to complete the install.
Requested Permissions
Risotto requests the following HiBob OAuth scopes during install:Supported Actions
HiBob supports the following People Actions:Get Employee Info
Look up the requesting employee’s profile, title, department, work location,
and start date. Turn it on in Support agent >
Context.
Get Home Address
View the home address on file for the requesting employee.
Get PTO Balance
Retrieve balances for each policy type the employee is assigned to.
Request PTO
Submit a time off request for the requesting employee in days mode.
Terminated Employees
When HiBob marks an employee as having left the company, Risotto receives a webhook from HiBob and immediately stops People Actions from running for that employee. Requests from former employees are escalated, even if their Slack account is still active.Automation triggers
HiBob employee events can start a Risotto automation. HiBob sends the events to the Risotto app that you installed from the HiBob Marketplace, so you do not configure a webhook. If the connection is missing or needs a new install, the trigger picker shows the HiBob events as unavailable, with “HiBob is not connected, or needs to be reinstalled.”Triggers
In the trigger picker, open HiBob and choose an event:- Employee joined and Employee left arrive on the effective date, not when HR enters the change in HiBob.
- A rehire sends Employee joined again with the new start date, and the automation runs again.
- If HiBob sends the same event again for the same date, Risotto runs the automation only once.
- If the employee has no valid work email, the automation still runs, with an empty
employee_email. Risotto never uses the personal email.
What the automation receives
Troubleshooting
HiBob does not always fail loudly. With valid credentials but missing grants, a people search comes back empty and a profile comes back with fields removed, while the connection still shows as connected. Risotto names the cause in the tool result and, for the sticky cases, sends one admin alert until the grant is fixed.Risotto finds no employee, or finds one with only an email
Risotto finds no employee, or finds one with only an email
If the connection cannot see any employee at all, Risotto says so: “The HiBob connection is authenticated but cannot see any employees at all.” In Bob, add the connection’s service user to a permission group whose viewing scope covers employees.If HiBob returns the employee but the name and other profile fields are missing, Risotto reports that HiBob withheld them. In Bob, grant the connection’s permission group view access on the People’s data categories (Basic info and Work).
Time off requests fail with a permission error
Time off requests fail with a permission error
HiBob accepted the credentials but refused the time off read (HTTP 403). In
Bob, grant the connection’s permission group view access on the Time Off
category.
Risotto says HiBob rejected the connection's credentials
Risotto says HiBob rejected the connection's credentials
HiBob answered with HTTP 401. An org admin must reconnect HiBob under
Settings > People > Connect.