Factorial

Connect AI agents to Factorial HR. Agents onboard employees, create and track leave requests, review attendance shifts, and pull team and leave-type data to keep HR workflows moving.

8 actions API key available

Factorial website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A signed offer arrives from the ATS or an intake form

List Employees confirms the person is not already in the directory

Create Employee adds them with name, email, and personal details from the intake

List Teams resolves which team the role belongs to for the manager's records

The HR manager verifies the new profile and its team assignment before downstream systems consume it

The confirmed record fans out to payroll, IT provisioning, and the org chart sheet

The hiring manager gets a summary with the start date and directory link

What This Integration Enables

An HRIS earns its keep by being the one place where employee facts are true, and Factorial only holds that position if the facts arrive on time. FlowRunner agents are the arrival mechanism. They create employee records from intake forms and ATS events, record leave with the correct type against the absence calendar, pull attendance shifts for payroll and audit, and read team structure so every downstream automation knows who reports where. - Onboard new hires into the directory from an ATS event or intake form - Sync the employee directory into a spreadsheet, CRM, or internal tool on a schedule - Turn chat and email time-off requests into structured leave records with the right leave type - Alert managers by [Slack](/integrations/slack) DM before a report's absence begins - Export attendance shifts to [Google Sheets](/integrations/google-sheets) for payroll review - Mirror directories across systems, for example reconciling against [BambooHR](/integrations/bamboohr) during a migration The leave-type detail is worth pausing on: Factorial distinguishes paid from unpaid types with accrual settings, and an agent that reads List Leave Types before writing gets that classification right, which is the difference between a tidy calendar and a payroll correction.

Without FlowRunner

The directory trails reality New hires exist in the ATS for weeks before anyone creates their HR record

Leave lives in inboxes Time-off requests arrive by chat and email, and some never reach the calendar

Attendance data goes unread Clock-in records accumulate in the HRIS and get looked at only when payroll disputes them

With FlowRunner

One intake, one record, everywhere The signed offer creates the Factorial profile, and every downstream system reads from it

Every absence is on the calendar Requests become structured leave records with the right type, reviewed before they bind

Attendance feeds payroll weekly Shifts export to the timesheet sheet on a schedule, anomalies flagged for a human

Use Case Scenarios

Offer signed Friday, directory current Monday

The ATS marks a candidate hired. The agent checks List Employees for duplicates, creates the profile with Create Employee using the intake's details, and resolves the destination team from List Teams. The HR manager approves the profile, and the flow fans the confirmed record out: a payroll row, an IT provisioning ticket, an org chart update. One intake event, every system current, no retyping.

The leave request that never gets lost

An employee messages their manager: "Taking the 12th through the 15th off." The manager forwards it to the flow, or the request arrives from a form. The agent matches the employee via the directory, proposes the leave type from List Leave Types, and drafts the request. Once HR confirms, Create Leave records it against the absence calendar, and a [Slack](/integrations/slack) DM reminds the manager two days before it starts, with coverage suggestions drawn from List Teams. Requests stop dying in scrollback.

Payroll review from attendance, not memory

Each Monday, List Attendance Shifts pulls the prior week's clock-ins and clock-outs per employee. Rows land in the payroll review tab in [Google Sheets](/integrations/google-sheets). The agent cross-references List Leaves for the same window and flags the contradictions that eat payroll time: shifts recorded on approved leave days, workdays with no shift and no leave. The payroll reviewer starts from a short exception list instead of a raw export.

Human-in-Loop Highlight

Create Leave binds three things at once when it writes: the employee's absence calendar, the team's coverage math, and, when the leave type is paid, the payroll calculation for that period. A wrong date range or a mistyped leave type is not a cosmetic error, it is a record that other systems and other people immediately treat as fact, and unwinding it means corrections in payroll and awkward reversals on a calendar the whole team can see. FlowRunner flows therefore split the work at the judgment line: the agent parses the request, matches the employee, proposes the type from List Leave Types with its paid or unpaid status shown, and lays out the dates against existing team leave from List Leaves. The HR manager looks at one card, "Sick leave, paid, March 12 to 15, two other team members already out on the 14th," and confirms, adjusts, or declines. The record that becomes company fact is always one a person has seen first.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Employees

List Employees Retrieves the paginated company directory with names, contact details, job information, and status. The duplicate check before onboarding and the base read for every directory sync.
Get Employee Retrieves one employee's full profile by ID: personal details, job title, manager, team assignments, and status. The on-demand lookup behind routing, approvals, and escalations.
Create Employee Creates a new employee record with name and email plus optional personal details, adding them to the directory ready for team and manager assignment. The onboarding write.

Leaves

List Leaves Retrieves time-off leaves, optionally filtered by employee, with type, date range, and approval status. The read behind coverage checks, manager reminders, and payroll cross-referencing.
Create Leave Creates a time-off request for an employee with a leave type and date range, recorded against their absence calendar and subject to company approval policy. The write this connector gates with human confirmation.
List Leave Types Retrieves the company's configured leave types with names, paid status, and accrual settings. The reference read that keeps agents from ever guessing whether an absence is paid.

Attendance

List Attendance Shifts Retrieves clock-in and clock-out shifts filtered by employee and date window, each tied to its workday. The payroll feed and the raw material for anomaly flags.

Organization

List Teams Retrieves the company's teams with names, descriptions, and member employee IDs. The structural read behind team assignment, coverage suggestions, and org chart syncs.

Frequently Asked Questions

What can FlowRunner do with Factorial?

FlowRunner agents can run List Employees, Get Employee, and Create Employee in Factorial, plus 5 more actions.

Does connecting Factorial to FlowRunner require OAuth?

No. Factorial connects to FlowRunner with an API key, no OAuth flow required.

Can Factorial trigger a FlowRunner workflow automatically?

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

Start building with Factorial

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

Start Building Free Talk to us