Resources · Make integration

Paylocity Make integrationAutomate Paylocity with Make.

Can Make react when someone joins, changes or leaves in Paylocity? Yes. The Paylocity Make integration offers 26 modules: 5 instant triggers, 9 actions and 12 searches. This page walks HR and payroll teams through the connection and a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Paylocity integration on Make See the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Paylocity Make integration automate?

The Paylocity Make integration links your Paylocity account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules where each module is one brick (a trigger, an action or a search). Paylocity tells Make when a hire, a change, a termination, a processed payroll or an approved time off happens, and the next modules read employee, pay and tax data.

Onboarding that starts on its own. Watch New Hire fires when a new employee is added, and Get an Employee pulls that person's information, so the IT ticket tool or the welcome email receives the details without anyone retyping them.

Offboarding nobody forgets. Watch Termination hands the departure to Make as soon as it is recorded. Access removal requests and the exit checklist then start from the same event, and List Deductions (WebLink) can add the employee's deductions to the exit file.

Payroll figures where finance reads them. When Watch Payroll Processed fires, List Employee Pay Statement Summaries by Check Date returns each employee's summaries for that check date, ready to land in a spreadsheet or a report.

One hard limit: Paylocity works in Make on the Enterprise plan alone, and an account on another plan cannot use it. Read the Make pricing breakdown before you commit. If you are weighing another tool, the n8n vs Make comparison sets out the criteria, and the Make agency team can build the first flows with you.

Connect

How do you connect Paylocity to Make?

01
Add a Paylocity module
Open a scenario, click the + and search for Paylocity. Pick any module, Watch New Hire for instance, then click Create a connection. A connection is your Paylocity account linked to Make once and reused by every Paylocity module.
02
Enter the client credentials
Type a name in Connection name if you want one; the field is optional. Then fill Client ID and Client Secret with the client credentials Paylocity provided to your company.
03
Save and confirm access
Click Save. If a window asks you to authenticate your Paylocity account and confirm access, accept it. The connection is then ready for every Paylocity module you add to this scenario or the next ones.

First scenario

Your first scenario: fetch each new hire's record

GoalWhen a new employee is added in Paylocity, Make fetches that employee's information so the next app can use it.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first module decides what starts the whole automation.
02
Add Watch New Hire
Search for Paylocity, choose Watch New Hire and select your connection, or click Create a connection. It is an instant trigger: Paylocity calls Make through a webhook as soon as someone is added.
03
Add Get an Employee
Click the + on the right of the trigger, pick Get an Employee and map the employee data from Watch New Hire into it. Each hire travels as one bundle, the item passed from one module to the next.
04
Test with Run once
Click Run once, then add a test hire in Paylocity. Read the bundles each module received and check that the record Get an Employee returns is the one you expected.
05
Switch the scenario on
Turn the scenario on. With an instant trigger it runs whenever Paylocity sends a hire, and each module run counts as one operation, the unit Make tracks on your plan.

Triggers

What can start a Paylocity scenario?

5 modules start a scenario when something happens in Paylocity. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Paylocity as soon as it happens.

Paylocity1Watch New Hire

Watch New Hire

Instant trigger

In Make“Triggers when a new employee is added.”

Watch New Hire starts your scenario with the record of a person just added in Paylocity, so onboarding tasks begin without anyone copying names between tools.

How it fires

instant. Paylocity calls Make through a webhook as soon as the employee is added, with no schedule to set.

When to use it

you want an IT account request, a welcome message or a row in a tracking sheet to appear for each hire, built from one source instead of three emails.

Watch out

each hire arrives as one bundle, and every module after the trigger spends one operation on it, so keep the chain short while you test.

Paylocity2Watch Employee Change

Watch Employee Change

Instant trigger

In Make“Triggers when an employee’s information is updated.”

Watch Employee Change hands Make the employee whose information was just updated, which keeps your other tools aligned with what HR edits in Paylocity.

How it fires

instant, through a webhook Paylocity sends as soon as the update happens.

When to use it

a new manager, department or address has to reach the company directory or the badge system without anyone entering it a second time.

Watch out

every update becomes a bundle that costs operations in each following module. Use Run once to see what the bundle carries, and add Get an Employee only if you need more.

Paylocity3Watch Termination

Watch Termination

Instant trigger

In Make“Triggers when an employee is terminated.”

Watch Termination gives Make the employee who has just been terminated in Paylocity, so the exit process starts from the HR record rather than from a hallway conversation.

How it fires

instant. Paylocity calls Make by webhook as soon as the termination is recorded.

When to use it

offboarding has to reach several places, such as account deactivation requests, equipment return and a note to payroll, and you want all of them started by the same event.

Watch out

what follows can be hard to undo in other apps. Test with Run once on a test employee before the scenario touches live accounts.

Paylocity4Watch Payroll Processed

Watch Payroll Processed

Instant trigger

In Make“Triggers when payroll is successfully processed for a company.”

Watch Payroll Processed tells Make that payroll was processed successfully for a company, which gives finance a clean moment to pull the figures.

How it fires

instant, by webhook, as soon as Paylocity reports the processed payroll.

When to use it

once payroll is final, you want pay statement summaries collected, a message posted to the finance channel or an accounting step started, instead of someone checking Paylocity by hand.

Watch out

the event concerns a company, while the pay statement searches work per employee. Put List Employees by Company in between and expect operations for every employee it returns.

Paylocity5Watch Time Off Approval

Watch Time Off Approval

Instant trigger

In Make“Triggers when a time off request is approved for an employee.”

Watch Time Off Approval sends Make each time off request that has just been approved for an employee, so calendars and staffing plans follow without extra steps.

How it fires

instant. Paylocity alerts Make through a webhook as soon as the approval happens.

When to use it

a shared team calendar, a staffing sheet or a manager's task list should show the absence the moment it is approved, not when someone remembers to update it.

Watch out

the trigger is described for approved requests only, so do not count on it to remind managers about requests still waiting for a decision.

Modules

What else can Make do in Paylocity?

Paylocity gives you 21 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Employee Demographic

3 modules

Paylocity1

Get an Employee (WebLink)

Action

In Make“Returns information about a specific employee.”

Get an Employee (WebLink) returns the information Paylocity holds about one specific employee, through the variant Make labels WebLink.

When to use it

a trigger or a list gave you an employee, and the next step needs that person's details.

Watch out

Make also offers a module named Get an Employee with the same description. The documentation does not explain the difference, so run both once on the same person and keep the one whose bundle holds what you need.

Paylocity2

Get an Employee

Action

In Make“Returns information about a specific employee.”

Get an Employee brings back the profile of a single employee, turning a bare event into a record the next app can actually use.

When to use it

right after Watch New Hire or Watch Employee Change, to give a ticketing tool or a spreadsheet the full picture of the person concerned.

Watch out

it reads one employee per run, so placed after a search it runs once per bundle and spends one operation each time.

Paylocity3

List Employees by Company

In Make“Returns a list of employees by company.”

List Employees by Company gives you the staff of a company, one bundle per person, a starting point for any task that covers everyone.

When to use it

after Watch Payroll Processed, to feed each employee into a pay statement search, or to rebuild a directory sheet from Paylocity.

Watch out

a search can return zero, one or many bundles, and every following module runs on each of them, so check the count with Run once before adding costly steps.

Company Level Information

1 module

Paylocity4

List Cost Center Codes

In Make“Returns a list of all cost center codes.”

List Cost Center Codes returns every cost center code set up in Paylocity, so finance tools can rely on the same reference as payroll.

When to use it

you keep a mapping table in a spreadsheet or an accounting tool and want it refreshed from Paylocity rather than typed by hand.

Watch out

each code comes out as its own bundle; add an aggregator, the module that groups bundles, if the next app expects one single list.

Other modules

17 modules

Paylocity5

Get a Deduction (WebLink)

Action

In Make“Returns information about a deduction for a specific employee.”

Get a Deduction (WebLink) returns the details of one deduction for a specific employee, handy when a single line matters more than the whole list.

When to use it

a benefits coordinator checks one specific deduction before answering an employee's question about a paycheck.

Watch out

it targets one deduction only; to see everything taken from an employee's pay, List Deductions (WebLink) is the better pick.

Paylocity6

Get an OpenAPI Documentation (WebLink)

Action

In Make“Returns the OpenAPI document customized for a specific company.”

Get an OpenAPI Documentation (WebLink) hands you the OpenAPI document Paylocity tailors to one given company: the technical description of the Paylocity API that company can reach.

When to use it

a developer prepares a request for Make an API Call (WebLink) and needs to see which requests Paylocity accepts.

Watch out

the output is reference material for people, not business data, so it rarely belongs in a scenario that runs unattended.

Paylocity7

Get Company Information

Action

In Make“Returns details about a specific Payroll entity.”

Get Company Information returns the details of a specific payroll entity, the company-level data sitting behind every employee record.

When to use it

a report or a document must carry the entity's details, or one scenario serves several companies and has to label each result.

Watch out

it reads one entity per run; pair it with List Company Codes when your group manages more than one.

Paylocity8

Get Direct Deposits (WebLink)

Action

In Make“Returns main direct deposit and all additional direct deposits for the selected employee”

Get Direct Deposits (WebLink) returns an employee's main direct deposit together with all the additional ones, so you see where every part of the pay goes.

When to use it

payroll support reviews an employee's deposit setup after a change request, before the next payroll is processed.

Watch out

this is banking data. Send it only to tools and people allowed to see it, and keep it out of shared sheets.

Paylocity9

Get Local Taxes (WebLink)

Action

In Make“Returns all local taxes with the provided tax code for the selected employee.”

Get Local Taxes (WebLink) returns the local taxes of the selected employee that match a tax code you provide, a precise lookup when one tax is in question.

When to use it

an employee asks about a specific local tax, and payroll wants that line and nothing else.

Watch out

you need the tax code before the module runs; without it, List Local Taxes (WebLink) returns the employee's full set.

Paylocity10

Get Sensitive Data (WebLink)

Action

In Make“Returns sensitive data information for a specific employee.”

Get Sensitive Data (WebLink) returns the sensitive data information Paylocity stores for a specific employee.

When to use it

a compliance or HR process genuinely requires it, for example a secured file handled by a small, restricted team.

Watch out

whatever this module returns travels through every module placed after it. Keep the scenario short, send the output only to secured destinations and share the scenario with as few people as possible.

Paylocity11

Make an API Call (WebLink)

Action

In Make“Perform an arbitrary authorized API call”

Make an API Call (WebLink) performs an authorized request of your choice against Paylocity, for the cases no ready-made module covers.

When to use it

you need data missing from this list, and someone on the team can read API documentation.

Watch out

you write the request yourself. Start from the document returned by Get an OpenAPI Documentation (WebLink), then read the response with Run once before relying on it.

Paylocity12

List Company Codes

In Make“Returns a list of company codes.”

List Company Codes returns the company codes set up in Paylocity, the natural first step when your payroll covers more than one entity.

When to use it

you want the same steps, a staff export or a cost center check, to run for every company in the group.

Watch out

every code becomes a bundle, and the modules after it repeat for each one, which multiplies operations.

Paylocity13

List Deductions (WebLink)

In Make“Returns all deductions for the selected employee.”

List Deductions (WebLink) returns all deductions for the selected employee, the complete picture of what comes off that paycheck.

When to use it

a benefits review, or an exit file started by Watch Termination that must list every deduction taken from the employee's pay.

Watch out

each deduction is its own bundle; aggregate them if the destination expects a single row per employee.

Paylocity14

List Earnings by Code (WebLink)

In Make“Returns a list of earnings with the provided earning code for the selected employee.”

List Earnings by Code (WebLink) returns the selected employee's earnings that match an earning code you supply, so you isolate one type of pay.

When to use it

finance follows one earning category for a given employee and does not want the rest of the pay in the way.

Watch out

the code has to exist in your Paylocity setup; run List Earnings (WebLink) once to see which codes appear before filtering.

Paylocity15

List Earnings (WebLink)

In Make“Returns all earnings for the selected employee.”

List Earnings (WebLink) returns all earnings for the selected employee, the full view of what makes up that person's pay.

When to use it

a compensation review, or a first exploration to discover which earning codes an employee has before you narrow down with List Earnings by Code (WebLink).

Watch out

one employee can produce several bundles, and each of them counts in the modules that follow.

Paylocity16

List Employee Pay Statement Details by Check Date (WebLink)

In Make“Returns a list of employee pay statement records for a specified company, employee, year, and check date.”

List Employee Pay Statement Details by Check Date (WebLink) returns the detailed pay statement records of one employee for a given company, year and check date.

When to use it

an employee disputes one specific paycheck, and payroll needs every line of it to answer.

Watch out

the module expects all four inputs: company, employee, year and check date. Map them from earlier modules rather than typing them.

Paylocity17

List Employee Pay Statement Details By Year (WebLink)

In Make“Returns a list of pay statement records for a specified company, employee, and year.”

List Employee Pay Statement Details By Year (WebLink) returns the detailed pay statement records of one employee across a whole year, for a given company.

When to use it

an employee or an auditor asks for the full detail of a year, not just one paycheck.

Watch out

a year of detail means many bundles; if totals per paycheck are enough, the summary version keeps the scenario lighter.

Paylocity18

List Employee Pay Statement Summaries by Check Date (WebLink)

In Make“Returns a list of pay statement summaries for a specified company, employee, year, and check date.”

List Employee Pay Statement Summaries by Check Date (WebLink) returns the pay statement summaries of one employee for a given company, year and check date.

When to use it

after Watch Payroll Processed, to push a short recap per employee into the finance spreadsheet.

Watch out

a summary is not the detail; when someone questions a line, switch to the Details by Check Date module.

Paylocity19

List Employee Pay Statement Summaries by Year (WebLink)

In Make“Returns a list of pay statement summaries for a specified company, employee, and year.”

List Employee Pay Statement Summaries by Year (WebLink) returns the pay statement summaries of one employee over a year, for a given company.

When to use it

an employee needs a yearly overview of pay, for a loan application or a personal record, without every line.

Watch out

the employee and company must be set first; feed them from List Employees by Company or a trigger.

Paylocity20

List Employees (WebLink)

In Make“Returns a list of employees by company.”

List Employees (WebLink) returns the employees of a company through the variant Make labels WebLink, one bundle per person.

When to use it

you need the whole staff as input for a directory refresh or a batch of pay statement lookups.

Watch out

List Employees by Company carries the same description. Run each once and compare the bundles before deciding which one your scenario keeps.

Paylocity21

List Local Taxes (WebLink)

In Make“Returns all local taxes for the selected employee”

List Local Taxes (WebLink) returns all local taxes attached to the selected employee, useful when you do not know in advance which one matters.

When to use it

an employee moves and payroll wants to review every local tax on file before the change.

Watch out

the result can hold several bundles; once you know the tax code you need, Get Local Taxes (WebLink) is more targeted.

Need help

Need help automating Paylocity with Make?

A person reads every message.

FAQ

Questions about Paylocity and Make

01Is the Paylocity Make integration free?

No. Make reserves Paylocity to its Enterprise plan, so the Free plan cannot run it. Free still exists for standard apps, with 2 active scenarios and a 15-minute minimum interval between scheduled runs, but enterprise apps like Paylocity are reserved to Enterprise. On paid plans, usage is counted in credits, one operation for each module run on each bundle. Your Paylocity subscription is a separate matter with Paylocity, and this page gives no price for either tool.

02What do you need to connect Paylocity to Make?

Three things: a Paylocity account, the Client ID and Client Secret that Paylocity provided, and a Make account on the Enterprise plan. In the editor, add any Paylocity module and click Create a connection. Naming the connection is optional. Paste the Client ID and Client Secret, click Save, then authenticate your account and confirm access if Make prompts you. The connection is created once and reused by every Paylocity module in your scenarios.

03Do Paylocity triggers fire in real time in Make?

Yes. All 5 Paylocity triggers are instant: Paylocity calls Make through a webhook as soon as an employee is hired, updated or terminated, as soon as payroll is processed or as soon as time off is approved. There is no polling interval to tune for them. The searches and actions, such as the pay statement lists, do not start anything on their own; they run when a trigger or a scheduled module placed before them passes them a bundle.

04What if a Paylocity module is missing in Make?

It depends on the need. First scan the 26 modules: several lookups exist in two versions, one of them labeled WebLink. For data none of them covers, the list includes Make an API Call (WebLink), which sends an authorized request you write yourself, with Get an OpenAPI Documentation (WebLink) as the reference. If writing requests is beyond your team, another app in your stack may already hold the same data, or the Hack'celeration team can scope the request with you.

05Should you pick Make or n8n for Paylocity?

It depends on your criteria. In Make, Paylocity comes with 26 modules and 5 instant triggers, but only on the Enterprise plan, so the plan question settles the Make side first. n8n often has a node for the same app: check what it covers for Paylocity, then compare against the events and data your HR process actually needs. The last criterion is people, meaning who on the team will build and maintain the scenarios. The comparison page linked in the section above lays out the other points.

Add a Paylocity module

Enter the client credentials

Save and confirm access

Create the scenario

Add Watch New Hire

Add Get an Employee

Test with Run once

Switch the scenario on

Need help automating Paylocity with Make?