FlowRunner
PricingContact
Theme
Start Free

HiBob

HR

Connect AI agents to HiBob, the HRIS for mid-size companies. Agents search and retrieve employee profiles, onboard new hires by creating people records, sync time-off changes incrementally, submit leave requests, and read company named lists.

6 actions Basic auth available
HiBob website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A signed offer completes in the applicant tracking system
Search People filtered on the work email confirms the hire does not already exist in Bob
List Named Lists pulls the valid department, site, and employment-type values so the record is created with real options, not free text
Create Person writes the employee record with name, work email, job title, department, site, and start date
Get Person reads the new profile back and verifies every field landed
The HR manager reviews the record before payroll, IT provisioning, and benefits flows consume it
IT and the hiring manager get the confirmed start date and profile link in their channel

What This Integration Enables

HiBob is where a mid-size company's org actually lives: who works here, where they sit, who they report to, and when they are away. Every other system, payroll, provisioning, capacity planning, is downstream of those facts. This connector lets FlowRunner agents keep the facts flowing without the re-keying. Agents search and read profiles to answer people questions inside any workflow, onboard hires from the ATS, sync leave incrementally using change-based reads, and discover the company's own configured vocabulary before writing anything. - Look up profiles, departments, managers, and start dates by name, email, or ID - Onboard hires by creating people records from ATS or upstream HR data - Sync time-off changes incrementally by passing the last sync timestamp - Submit leave requests on an employee's behalf, routed through policy approval - Read named lists so writes use valid departments, sites, and employment types

Without FlowRunner

New hires are typed in twice The offer data lives in the ATS and someone re-keys it into Bob, usually the week before start
Leave syncs by full export Absence reporting means pulling everything and diffing by eye
Department values drift Free-text entries spawn "Eng", "Engineering", and "engineering" as three departments

With FlowRunner

The ATS feeds Bob directly Signed offers become verified people records the same day, reviewed once by a human
Leave syncs incrementally Flows pull only what changed since the last run, and downstream systems stay current
Writes use the company's real vocabulary Named lists supply the valid values before any record is created

Use Case Scenarios

Onboarding without the re-keying week

A hire finalizes in [Greenhouse](/integrations/greenhouse). The agent checks for an existing record with Search People, resolves department and site against List Named Lists, and stages Create Person with the work section populated. The HR manager approves, the record is created, and Get Person verifies the result. A welcome email goes out through [Gmail](/integrations/gmail), and the returned employee ID kicks off IT provisioning. The new hire exists in Bob correctly on day one because a flow did the typing and a person did the checking.

The absence picture that is never out of date

Every hour, an agent calls List Time-Off Changes with the previous run's timestamp and processes only the delta: new requests, approvals, cancellations. Each change appends to the absence tracker in [Google Sheets](/integrations/google-sheets), and approved leave for the coming two weeks posts to the team's planning channel in [Slack](/integrations/slack). Project leads see coverage gaps while sprint planning, not on the Monday someone fails to show up. The sync stays fast because it never re-reads the whole leave history.

People answers inside other workflows

An escalation flow needs a manager. The agent calls Search People on the employee's email with fields restricted to work.department and the reporting line, pulls the manager's profile with Get Person, and routes the approval to the right person in Slack. The same pattern powers the compliance flow that checks a contractor's site before granting building access, and the finance flow that validates cost-center assignment at expense time. Bob stops being a tab HR checks and becomes the answer source every flow can ask.

Human-in-Loop Highlight

Create Person writes a new employee into the HRIS, and the HRIS is the system every other system believes. The record created here becomes the payroll entry, the provisioning trigger, the benefits enrollment, and the org-chart node; a wrong start date or a mistyped email replicates into all of them before the first coffee. Create Time-Off Request carries a subtler weight: it files leave in a named employee's name against a real policy, and depending on configuration it may be created directly rather than routed for approval, which means an agent error becomes an official absence on someone's record. So FlowRunner flows stage both writes for review. The agent does the assembly, dedup check, named-list validation, field mapping, and presents the complete record or request to the HR manager before committing. Profile reads and incremental leave syncs run unattended around the clock. Writing facts into the system the whole company trusts is the step that keeps a human signature.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

6 actions

People

3
  • Search People Searches and lists employees via the People Search API, returning all matches in one response. Fields can be restricted with dot notation like root.email or work.department, filters can narrow to one employee by ID or email, and human-readable named-list labels can be included. The lookup behind dedup checks, manager resolution, and people answers in any flow.
  • Get Person Retrieves one employee's full profile by HiBob employee ID, across the identity, work, and other sections visible to the service user. The verification read after onboarding writes and the enrichment step in routing flows.
  • Create Person Creates a new employee record with first name, surname, and work email, plus job title, department, site, and start date for the employment section. Returns the generated employee ID. The write this page's human gate exists for.

Time Off

2
  • List Time-Off Changes Lists time-off requests created, updated, cancelled, or approved since a given timestamp. The incremental sync primitive: pass the last run's timestamp and process only the delta, with policy, dates, and status on each change.
  • Create Time-Off Request Submits a leave request for an employee against a company policy with start and end dates. Depending on policy configuration it is created directly or routed for approval, which is why agents stage it for human review.

Company

1
  • List Named Lists Retrieves the company's configurable enumerations, departments, sites, employment types, and custom lists, with their allowed values. The vocabulary check that keeps automated writes consistent with how the company actually names things.

Frequently Asked Questions

What can FlowRunner do with HiBob?

FlowRunner agents can run Search People, Get Person, and Create Person in HiBob, plus 3 more actions.

Does connecting HiBob to FlowRunner require OAuth?

No. HiBob connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can HiBob trigger a FlowRunner workflow automatically?

HiBob doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with HiBob

$100 in credits. No card required. Connect in minutes.