People HR
HRConnect AI agents to People HR, the Access PeopleHR management platform for UK businesses. Agents create and update employees, book holidays, and pull absence and salary data so HR records stay current across systems.
What This Integration Enables
People HR, now Access PeopleHR, is the HR system of record for a large number of UK businesses, and its API is unusually blunt about how it works. Every call posts to one endpoint with an Action name inside the request body, and every response comes back in the same envelope with the payload under Result. What that means in practice is that the connector's reach is not defined by a long list of scopes. It is defined by one account level key and by what an administrator has configured inside the product.
FlowRunner agents use that surface across four areas. On employee records they read one person by Employee ID and export the full directory, with an option to include leavers. They create a new starter under a unique Employee ID, update personal and job details with a required Reason For Change that is written into the record's change history, and mark someone as a leaver with their final employment date and reason. On annual leave they read an employee's bookings within a date range, add a booking as full days or as a morning or afternoon half day, delete a booking that falls in a given range, and read entitlement showing days entitled, taken, and remaining. On absence and pay they read absence records such as sickness within a range, and read current salary with an option to include the history. And Run Saved Query executes a report defined in People HR's own reporting screens by its exact name, returning whatever cross employee dataset that report was built to produce.
That last one is the most powerful operation here and the one worth thinking hardest about. The query lives in People HR, not in your flow. Its definition can be edited by an administrator who has no idea an automation depends on it, and it can return compensation columns. Combined with an API key that is shared across the whole account and carries no per operation scoping, the honest description of this connector is that it is broad by design. FlowRunner's connectors are built and verified against each vendor's official API, and the boundary that matters here is not the connector's, it is the one you draw around what leaves the system.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The Monthly Report That Checks Its Own Columns
Finance needs a headcount and cost center report every month. Someone used to export it, strip the columns finance should not see, and email the rest. Now the agent runs Run Saved Query against the report an HR administrator built, reads the column headers that actually came back, and compares them against the approved list for this flow. If the columns match, the rows are written to Google Sheets and finance is notified. If a column has appeared or changed name since last month, the flow stops and the HR owner is asked before anything is written. The manual step that used to be stripping data becomes confirming that nothing new needs stripping.
New Starter Created Once, From the Offer
An offer is accepted and countersigned in DocuSign. The agent reads the signed document, allocates the next Employee ID under the account's own scheme, and runs Create Employee with the start date, job title, department, and location taken straight from the offer. It then reads the record back with Get Employee and posts the confirmed profile to the hiring manager in Slack so any mistake is caught while it is cheap to fix. Later corrections go through Update Employee, which requires a Reason For Change and writes that reason into the record's history. The change history stays readable because every automated change explains itself.
Leave Booked From the Channel People Actually Use
An employee asks for time off in the team's chat tool. The agent resolves them, runs Get Holiday Entitlement to read days entitled, taken, and remaining, and runs Get Holidays to check whether the requested dates overlap with an existing booking or with someone else's approved leave in the same team. The manager sees the request and the balance in one message and answers. On approval the agent runs Add Holiday, choosing days or a morning or afternoon half day as requested. If the employee later withdraws the request, Delete Holiday removes the booking for that date range. The balance is part of the decision instead of a follow up question.
Human-in-Loop Highlight
The gate here sits on the export, not on any write. Run Saved Query is powerful precisely because the flow does not define the query. An administrator does, inside People HR, and Get Salary sits in the same connector behind the same account wide key. So when the monthly report flow detects a column it has not seen before, it stops and asks: "The saved query People Monthly Extract returned 412 rows with a new column, Annual Salary, that was not present in last month's run. This flow writes its output to the finance workbook. Send as is, send without that column, or hold until the query is reviewed?" The HR owner answers in the channel they already work in. What makes this a real automation exception rather than a checkbox is that the agent could not have resolved it alone. It can see that the shape of the data changed. Only a person can decide whether the new shape is allowed to travel.
Agent Capabilities
12 actionsEmployee Records
5- Get Employee Return the full detail record for one employee by Employee ID, including personal details, job role, department, location, and contact information.
- Get All Employees Return detail records for every active employee, with an option to include leavers. Used to export the directory or to reconcile People HR against another system.
- Create Employee Create a new starter record with a unique Employee ID and the core identity and start details, plus optional job, location, and department fields.
- Update Employee Update personal and job details for an existing employee. A Reason For Change is required and is recorded against the change history. Only the fields you supply are changed.
- Mark Employee as Leaver Record a final employment date and reason for leaving against an existing employee. Used to process an offboarding.
Annual Leave
4- Get Holidays Return all annual leave bookings for an employee within a date range, with start and end dates, duration, and status.
- Add Holiday Book annual leave for an employee, as whole days or as a morning or afternoon half day.
- Delete Holiday Delete an employee's annual leave booking that falls within the given date range. Used when a request is withdrawn.
- Get Holiday Entitlement Return an employee's entitlement and balance for a period, including days entitled, taken, and remaining. Used to put the balance in front of an approver before the decision.
Absence and Pay
2- Get Absences Return an employee's absence records, such as sickness, within a date range, with dates, type, and duration.
- Get Salary Return an employee's current salary detail including pay amount, deductions, and entitlements, with an option to include previous records. Treat any flow that moves this data as an export decision.
Reporting
1- Run Saved Query Run a saved report defined in your People HR account by its exact name and return the result rows. The query definition lives in People HR, so read the columns you receive rather than assuming the ones you asked for.
Frequently Asked Questions
What can FlowRunner do with People HR?
FlowRunner agents can run Get Employee, Get All Employees, and Create Employee in People HR, plus 9 more actions.
Does connecting People HR to FlowRunner require OAuth?
No. People HR connects to FlowRunner with an API key, no OAuth flow required.
Can People HR trigger a FlowRunner workflow automatically?
People HR doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with People HR
$100 in credits. No card required. Connect in minutes.