HiBob

In flight

The HiBob connector ships with the Conversational FP&A recipe build. This page is a stub of the planned spec — file an issue if you need it sooner.

Connect to HiBob to import the canonical org structure: employees, departments, employment status, comp & benefits, and the hiring plan. HiBob is the source-of-truth for org hierarchy and drives realm-based access scoping in the FP&A recipe.

Setup

1. In HiBob, create a Service User with the relevant permissions (read on People, Org, Compensation, Reports).
2. Generate an API token for the Service User.
3. Note the service_user_id and the bearer token.

Configuration

curl -X POST $API/api/v1/sources \
  -H "authorization: Bearer $TOKEN" -H 'content-type: application/json' \
  -d '{
    "name": "hibob-prod",
    "connector": "hibob",
    "realm": "fin-master",
    "config": {
      "service_user_id": "SVC-…",
      "api_token": "<bearer>",
      "base_url": "https://api.hibob.com/v1"
    }
  }'

Field	Type	Required	Description
service_user_id	string	Yes	HiBob Service User identifier.
api_token	secret	Yes	Bearer token for that service user.
base_url	string	No	Defaults to https://api.hibob.com/v1.

Tools (planned)

• hibob.list_employees(filters?) — active roster with department, role, manager
• hibob.get_employee(id)
• hibob.get_org_chart() — full hierarchy
• hibob.list_departments()
• hibob.get_hiring_plan(quarter)
• hibob.list_compensation(scope) — gated by role

Realm mapping

HiBob's department field is the canonical scoping key. Map it to Agentcy realms once at setup:

curl -X POST $API/api/v1/realms/mappings \
  -H "authorization: Bearer $TOKEN" -H 'content-type: application/json' \
  -d '{
    "source": "hibob-prod",
    "by_property": "department",
    "rules": [
      { "value": "Engineering", "realm": "fin-eng" },
      { "value": "Sales",       "realm": "fin-sales" }
    ]
  }'

Used by

• Recipe: Conversational FP&A