TalentHR
HRConnect AI agents to TalentHR, the lightweight all-in-one HRIS by Epignosis. Agents hire, update, and terminate employees, process time off requests, and manage departments and locations so people data stays consistent from onboarding to offboarding.
What This Integration Enables
TalentHR is a lightweight all-in-one HRIS from Epignosis, and its API is refreshingly literal about what it does. It does not model performance cycles or compensation planning. It models the four things a small people operations team actually has to keep straight: who works here, what they are entitled to, how the organization is shaped, and who has applied. Every operation maps to one of those.
Agents hire an employee with the required identity fields, hire date, and employment status, optionally assigning manager, job title, location, division, and department, and can suppress the automatic invitation email when a record is being created ahead of the person's start. They read a single profile, update it, and terminate it as of an effective date with a reason, a type, and a regrettable flag. List Directory pages through the workforce with each person's identifiers for their division, department, location, and job title. Time off is a full loop. Agents list an employee's requests and create a new one over a date range for a given type, with optional preapproval and a per day amount map for partial days. They approve or reject a pending request, read allocated, used, and remaining balances per type per year, and list the configured types with their default budget, accrual period, and paid status. Organization structure operations list and create departments and locations and list divisions and job titles, which is what supplies the IDs the hire and update operations expect. Two recruiting reads, List Job Positions and List Candidates, expose the applicant tracking side including pipeline steps and an optional talent pool filter.
One structural detail shapes how you build updates. Update Employee requires first name, last name, and email even for a partial change, so a flow must pass the current values for anything it is not changing. Read Get Employee first, merge, then write. This connector has no triggers, since the TalentHR Public API exposes neither webhooks nor a change feed, so flows here start from a schedule or from an event in another system.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Accepted Offer to Employee Record
An offer is accepted and countersigned. The agent reads the signed document, resolves the role's department, location, division, and job title to IDs with List Departments, List Locations, List Divisions, and List Job Titles, and runs Hire Employee with the person's name, email, hire date, and employment status plus the resolved assignments and their manager. Because the start date is three weeks out, it suppresses the automatic invitation email and schedules that for the Friday before. It then triggers account provisioning in Okta using the same source record. The HRIS entry and the identity account are built from one input, so the job title in each of them says the same thing.
Time Off Requests Without the Inbox Round Trip
Employees request leave in the tool they already use during the day. The agent receives the request and runs Get Time Off Budgets for the employee to confirm the balance covers it. It resolves the type ID with List Time Off Types, then runs Create Time Off Request over the date range, supplying a per day amount map where the request covers a half day. It posts the request to the manager in Slack with the remaining balance shown, and on the manager's response runs Reply To Time Off Request to approve or reject. The balance check happens before the request exists rather than after someone notices an overdraft.
Directory Reconciliation
Small organizations accumulate drift: a department renamed in one system, a manager who left, a location that closed. On a monthly schedule the agent runs List Directory to page through every employee with their name, email, job title, department, division, and location, and compares each row against the identity directory and the payroll export. Differences are written to a review sheet in Google Sheets with the value from each system side by side, rather than being auto-corrected. People data is exactly the place where an automated merge fixes ten records and quietly breaks one.
Human-in-Loop Highlight
Terminate Employee ends someone's employment record as of an effective date, with a reason, a type, and a regrettable flag, and this connector exposes no operation that undoes it. There is a Hire Employee and there is no un-terminate. In a system that downstream tools read to decide whether an account should exist and whether a paycheck should run, that is the single most consequential call in the surface, and it is the one an agent should never make on the strength of a checklist status alone. So the agent does the preparation and stops. It reads the current record with Get Employee, pulls approved leave crossing the leaving date with List Time Off Requests and Get Time Off Budgets, and routes the staged change to the HR lead: "Ready to terminate [name], effective [date], reason [reason], type [type], regrettable [yes or no]. They have [N] days of approved leave after that date and a remaining balance of [N]. This cannot be reversed through the connector. Approve, change the effective date, or hold." Hires, profile updates, time off requests, and directory reads run on their own. Ending the record waits for a named person, which is what a human-in-the-loop gate is for.
Agent Capabilities
18 actionsEmployee Lifecycle
5- Hire Employee Creates a new employee. First name, last name, email, hire date, and employment status are required. Optionally assigns manager, job title, location, division, and department, and suppresses the automatic invitation email. Email must be unique and the hire date must be formatted as YYYY-MM-DD.
- Get Employee Retrieves the full profile of a single employee by ID, including personal details, job information, contact data, and the identifiers for their division, department, location, and job title. Read this before any update, since the update operation is not a true partial write.
- Update Employee Updates an existing employee's profile. First name, last name, and email are required by the API even for partial updates, so pass the current values for any field you are not changing. Personal email, phone numbers, gender, marital status, address, and LinkedIn URL are optional.
- Terminate Employee Terminates an employee as of an effective date, optionally recording a termination reason, type, and regrettable status. The effective date must be formatted as YYYY-MM-DD. Routed for sign-off, because the connector offers no reversal.
- List Directory Lists employees from the company directory with pagination, returning a total count and rows with each employee's ID, name, email, job title, department, division, and location. Used to browse the workforce or reconcile it against another system.
Time Off
5- List Time Off Requests Retrieves the time off requests submitted by a specific employee, with pagination. Each request includes the time off type, date range, budget consumed, and approval state.
- Create Time Off Request Creates a time off request for an employee over a date range for a given type. Optionally preapproves the request and supplies a per day amount map as a JSON string for partial or hourly days. Dates use YYYY-MM-DD and must fall within one year of the current date.
- Reply To Time Off Request Approves or rejects a pending time off request for an employee. Set Approve to true to grant the request or false to reject it. Run this on a manager's decision rather than on a rule alone.
- Get Time Off Budgets Retrieves an employee's time off budgets, showing allocated, used, and remaining balance per type for each year. Read this before creating a request to confirm the balance covers it.
- List Time Off Types Lists all configured time off types for the company, including each type's name, default budget, accrual period, and whether it is paid. Use the returned IDs when creating requests.
Organization Structure
6- List Departments Lists all departments defined in the company, each with its ID and name. Use the IDs when hiring employees or building org structure filters.
- Create Department Creates a new department. The name must be unique and at most 255 characters.
- List Locations Lists all company locations, each with its ID, name, address, and whether it is a remote location.
- Create Location Creates a new company location with an address and a remote flag. The name must be unique up to 255 characters and the address is required up to 100 characters.
- List Divisions Lists all divisions defined in the company, each with its ID and name.
- List Job Titles Lists all job titles defined in the company, each with its ID and name. Use the IDs when hiring or updating employees.
Recruiting
2- List Job Positions Lists all job positions in the applicant tracking system, including each position's title, status, location, department, and hiring pipeline steps. Used to review open roles and their configuration.
- List Candidates Lists candidates in the applicant tracking system with pagination, sorting, and free text search, optionally restricted to the talent pool. Each candidate includes contact details and the number of applications.
Frequently Asked Questions
What can FlowRunner do with TalentHR?
FlowRunner agents can run Hire Employee, Get Employee, and Update Employee in TalentHR, plus 15 more actions.
Does connecting TalentHR to FlowRunner require OAuth?
No. TalentHR connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can TalentHR trigger a FlowRunner workflow automatically?
TalentHR doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with TalentHR
$100 in credits. No card required. Connect in minutes.