Paylocity

Connect AI agents to Paylocity payroll and HCM. Agents add and update employee records, manage earnings lines, audit local tax setup, and look up department codes to keep payroll in sync with your HR source of record.

8 actions OAuth available

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

The HR system of record marks a candidate as hired

List Employees confirms the person is not already on the Paylocity roster

List Departments resolves the correct department code for the role

Add Employee creates the payroll record with demographics, hire date, and department

The payroll administrator verifies the record and the proposed base pay line, code, rate, and frequency, before anything is payable

Add Earning writes the approved base pay line

List Local Taxes confirms the local withholding setup matches the employee's work location

The payroll channel gets the onboarding summary with anything unresolved flagged

What This Integration Enables

Payroll systems punish drift like no other software: every mismatch between the HR source of record and Paylocity eventually becomes a wrong paycheck, a tax notice, or an audit finding. FlowRunner agents exist to eliminate the drift. They add and update employee records from the system of record, stage earning lines for approval, audit local city, county, and school district tax setup per employee, and resolve department codes so classifications are correct at write time instead of corrected at close. - Onboard new hires from [BambooHR](/integrations/bamboohr) into payroll with the record and base pay staged in one flow - Push demographic updates from the source of record so Paylocity never lags the HRIS - Build payroll audit sheets in [Google Sheets](/integrations/google-sheets) with each employee's earning lines attached - Sweep local tax configuration and alert the payroll administrator by [Slack](/integrations/slack) DM on gaps - Classify employees with real department codes at add and update time This connector is deliberately conservative. Payroll is the one system where "the automation did something surprising" is never an acceptable sentence, so every write here is designed to run staged, reviewed, and logged.

Without FlowRunner

Payroll onboarding is re-entry The hire exists in the HRIS, and someone retypes it all into Paylocity

Pay lines set up from memory Earning codes and rates get keyed in under deadline, checked only when the first paycheck is wrong

Local tax gaps surface at year end A missing city or school district tax quietly compounds until the W-2 correction

With FlowRunner

The HRIS event creates the record Demographics, hire date, and department land in Paylocity the day of the hire

Pay lines are staged and approved The agent drafts the earning line and a payroll administrator confirms it before it pays

Tax setup is audited continuously Local tax sweeps flag missing or misconfigured codes while they are still cheap to fix

Use Case Scenarios

Hire to payable, with a checkpoint in the middle

[BambooHR](/integrations/bamboohr) marks a new hire. The agent pulls their record, resolves the department from List Departments, and calls Add Employee with demographics and hire date. It then stages the base pay line, earning code REG, the offer letter's rate, and presents both to the payroll administrator. On approval, Add Earning writes the line. The first paycheck is right because the setup was reviewed once, calmly, instead of keyed in five times, quickly.

The quarterly payroll audit that builds itself

Each quarter, List Employees pulls the roster, and for each person List Earnings attaches their configured pay lines. The agent writes the audit sheet to [Google Sheets](/integrations/google-sheets): employee, status, department, each earning code with amount or rate and frequency. Terminated employees with active earning lines and active employees with none rise to the top. The payroll team reviews a prioritized exception list instead of eyeballing a full roster export.

The local tax gap caught in October, not January

A monthly sweep runs List Local Taxes for every employee against their work location on file. An employee who moved to a city with a local levy, but whose record shows no matching tax code, becomes a [Slack](/integrations/slack) DM to the payroll administrator with the employee ID and the expected code. The fix is a routine update in October. The same discovery in January is amended filings and an unhappy employee with a surprise balance due.

Human-in-Loop Highlight

Add Earning writes a line that the next payroll run will pay. An earning code with a rate attached is not a draft or a suggestion once it lands in Paylocity, it is an instruction to move wages, and wages are the hardest money in business to move back: overpayment recovery is legally constrained, morale-expensive, and slow. A transposed digit in a bonus amount, or an OT code where a REG code belonged, ships in the next check and then has to be clawed out of it. So no FlowRunner flow lets an agent write earnings unattended. The agent assembles the line, code, amount or rate, frequency, effective dates, alongside the source that justifies it, the offer letter, the approved bonus sheet, and the payroll administrator confirms before the write. Update Employee sits behind the same gate whenever the fields touched feed pay or tax calculation. The agent's job is to make the review take thirty seconds. The administrator's job is to be the reason the paycheck is right.

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 all employees for the configured company with core demographic and status information. The roster read behind dedup checks, audits, and syncs.
Get Employee Retrieves a single employee record by ID with demographic, employment, and status details. The verification step before any update or earning change.
Add Employee Adds a new employee with ID, name, and optional hire date, status, department, job title, and email, plus any additional Web Link API fields. The payroll onboarding write.
Update Employee Updates an existing employee record, sending only the fields provided. The sync tool that keeps Paylocity aligned with the source of record, gated when the change touches pay or tax.

Earnings

List Earnings Lists an employee's configured earnings, such as salary, hourly, and additional pay lines, with earning code, amount or rate, and frequency. The audit read behind every pay review.
Add Earning Adds an earning line to an employee with an earning code such as REG, OT, or BON, a fixed amount or rate, and optional start and end dates. The write that becomes wages, and the reason this connector's human gate exists.

Taxes

List Local Taxes Lists the local city, county, and school district taxes configured for an employee, with each code and its rate or amount. The sweep that catches withholding gaps while they are still cheap.

Company Codes

List Departments Lists the company's department codes and descriptions via the Paylocity Open API. The reference data that keeps classifications correct at write time.

Frequently Asked Questions

What can FlowRunner do with Paylocity?

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

Does connecting Paylocity to FlowRunner require OAuth?

Yes. Paylocity connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Paylocity trigger a FlowRunner workflow automatically?

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

Start building with Paylocity

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

Start Building Free Talk to us