Resources · Zapier integration

PeopleForce Zapier integrationAutomate PeopleForce with Zapier.

The PeopleForce Zapier integration gives you 13 triggers, 1 action and 2 searches. Every trigger is instant, so hiring, leave and salary events reach your Zap without waiting for a timed check, even on the free plan of Zapier.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PeopleForce Zapier integration actually does

It links your PeopleForce account to Zapier so that an HR event, a new hire, an approved leave, an accepted offer, starts an automation on its own. PeopleForce mostly talks: it reports 13 kinds of events. It only listens in one way, by creating a task for an employee.

Three results people build with it. An onboarding to-do for every hire: Employee Created starts the Zap, Create Task puts the first item on that person's list. A live absence board: Leave Request Approved and Leave Request Withdrawn keep a shared calendar or a channel in step with what managers decide. A recruiting log that fills itself: Applicant Created, Vacancy Offer Accepted and Vacancy Offer Rejected each write a line wherever your team tracks hiring.

What Zapier does not do here matters just as much. There is no action to create an employee, approve a leave request or change a salary: the single write is Create Task. Both searches work from an ID only (Candidate ID, Employee ID), so a Zap holding just a name cannot look anyone up. And since the free plan stops at two steps, any Zap that needs one of those searches, or a filter, runs on a paid plan.

Before you commit, compare the tools side by side in n8n vs Zapier. For the overall picture of the tool, read the Zapier review.

Vocabulary

The Zapier words you will meet on this page

Eight terms, one line each. They come back on every screen of the editor.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in PeopleForce that starts the Zap, such as a hire or a rejected offer. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like Create Task.
Task
The unit Zapier bills. One action that completes successfully is one task; your plan's allowance counts those.
Instant vs polling trigger
An instant trigger is reported by the app itself the moment the event happens. A polling one is checked by Zapier on a timer.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Connection
Your PeopleForce account linked to Zapier once, then reused by every step that touches PeopleForce.
Cost

What a PeopleForce Zap really costs

The trigger never costs a task. Only a completed action does, and a failed one is not counted against your plan.

  • Trigger fires0 tasks
  • Create Task succeeds1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on Free

PeopleForce is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps per Zap. The polling grid below does not touch you here, because all 13 triggers are instant. A filter or a search makes the Zap multi-step, and that needs a paid plan. Every extra action counts on its own: a Zap with three successful actions uses three tasks per run, so a busy hiring month shows up on your count. A few apps and actions take more than one task each.

Connect

Connect PeopleForce to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a PeopleForce account first, plus access to any records you do not own but want the Zap to touch.

  2. 02

    Pick PeopleForce

    Type PeopleForce in the search box of the dialog, select it, then click Add connection. A new tab opens on the PeopleForce side, where the rest of the connection happens.

  3. 03

    Sign in and allow access

    Log in to PeopleForce in that tab and grant Zapier access to the account. The connection is then saved and every PeopleForce step of every Zap reuses it.

First Zap

Your first Zap: an onboarding task for each new hire

GoalWhen HR adds an employee in PeopleForce, give that person a first task, but only when your condition passes.

  1. 01

    Pick the trigger

    Build: choose PeopleForce as the app that starts the Zap and Employee Created as the event, then select your PeopleForce connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent employees of the account, so you map the next steps on a real record, not a blank one.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and set the field, the rule and the value. A text rule only works on text: pick the wrong type and the filter never passes.

  4. 04

    Add Create Task

    Pick PeopleForce again and Create Task. Map the Employee ID from the trigger, then write the Name and the Description of the onboarding task.

  5. 05

    Test, then publish

    Test each step and read what came back. Then click Publish. The filter makes this a multi-step Zap, so it runs on a paid plan; drop it to stay on Free.

Triggers

PeopleForce triggers: 13 events, all instant

13 events start a Zap when something happens in PeopleForce, and 13 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Applicant Created

Instant trigger

In Zapier“Triggers when a new applicant is created.”

A fresh applicant lands in PeopleForce and the Zap wakes up with that applicant's record, ready to pass along to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a recruiter wants every new applicant copied into the team's hiring tracker without retyping anything.
Watch out
applicants who were already in PeopleForce before you publish the Zap are never picked up.
2

Employee Created

Instant trigger

In Zapier“Triggers when a new employee is created.”

This one starts when HR adds someone to the employee list, which makes it the natural opening of any onboarding Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an office manager wants an onboarding task created with Create Task for each hire, in a two-step Zap that fits the free plan.
Watch out
a bulk import of staff arrives as one large batch, and Zapier's flood protection can hold it back.
3

Employee Position Created

Instant trigger

In Zapier“Triggers when an employee position is created.”

Adding a new position to an employee's record sets this Zap off, and the Zap receives that new position.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a team lead wants word of every new role so that access rights get reviewed.
Watch out
it reacts to a position being added, not to edits of an existing one; those belong to Employee Position Updated.
4

Employee Position Updated

Instant trigger

In Zapier“Triggers when an employee position is updated.”

Here the Zap waits for changes to a position already on file, rather than for new ones being added.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
whoever runs payroll wants a heads-up each time a role on record is corrected.
Watch out
neither position trigger covers the other, so catching both cases means two Zaps.
5

Employee Salary Created

Instant trigger

In Zapier“Triggers when an employee salary is created.”

Recording a new salary for someone in PeopleForce is the event behind this trigger, and the Zap receives that salary entry.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a finance lead keeps a restricted log of salary decisions for the accountant.
Watch out
salary data is sensitive, so check who can open the place your next step writes into.
6

Employee Salary Updated

Instant trigger

In Zapier“Triggers when an employee salary is updated.”

Any change to a salary entry that already exists starts this Zap, which keeps a correction from slipping past the people who need to know.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
HR wants the payroll provider's contact told whenever an amount on file is edited.
Watch out
only edits made after the Zap is published count; older adjustments stay where they are.
7

Employee Terminated

Instant trigger

In Zapier“Triggers when an employee is terminated.”

When HR records a departure in PeopleForce, this trigger turns that moment into the start of an offboarding run.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an IT admin wants a checklist opened to collect the laptop and close the accounts of the leaver.
Watch out
the test brings back the three most recent items of the account, so have a real recent termination on hand to map from.
8

Employee Updated

Instant trigger

In Zapier“Triggers when an employee is updated.”

Edits to an employee's record are what this trigger listens for, so a changed detail on someone's profile is enough to start the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a company directory kept in another tool should follow every change made in PeopleForce.
Watch out
records that change often mean many runs, and each successful action in each run counts as a task.
9

Leave Request Approved

Instant trigger

In Zapier“Triggers when a leave request is approved.”

A manager signing off on time off is the signal here: the approved request reaches the Zap with it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a team calendar should show who is off, without anyone copying approvals by hand.
Watch out
a request withdrawn after approval comes through Leave Request Withdrawn, so the calendar needs that second Zap to stay accurate.
10

Leave Request Rejected

Instant trigger

In Zapier“Triggers when a leave request is rejected.”

Turned-down leave requests start this Zap, which gives HR a trace of refusals that would otherwise stay in a manager's inbox.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
HR counts rejected requests in a sheet to spot teams that are short-staffed.
Watch out
keeping only one team's refusals takes a filter, and a filter means a multi-step Zap on a paid plan.
11

Leave Request Withdrawn

Instant trigger

In Zapier“Triggers when a leave request is withdrawn.”

The employee pulled the request back: that is what this trigger reports, so a plan built on that request can be undone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
clear the absence from the shared calendar that an earlier Zap filled on approval.
Watch out
removing that calendar entry needs an action in the calendar tool, not in PeopleForce, which offers no delete action.
12

Vacancy Offer Accepted

Instant trigger

In Zapier“Triggers when a vacancy offer is accepted.”

A candidate saying yes to an offer sets this Zap off, the point where hiring turns into onboarding.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
start the first-day paperwork and tell the hiring manager once the yes is in.
Watch out
the person is a candidate here, not yet an employee, and Create Task needs an Employee ID; that task belongs in an Employee Created Zap.
13

Vacancy Offer Rejected

Instant trigger

In Zapier“Triggers when a vacancy offer is rejected.”

Declined offers are what this one watches for, so a no from a candidate never goes unnoticed by the people still recruiting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a recruiter wants the runner-up flagged for a call the same day the first choice declines.
Watch out
pulling the candidate's full record with Find Candidate needs a Candidate ID and makes the Zap multi-step.
Actions

The PeopleForce action: Create Task

PeopleForce gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Task

Action

In Zapier“Creates a Task for an employee”

Puts a task on one employee's list in PeopleForce, with a name and a description you type or fill from earlier steps.

When to use it
after Employee Created, hand each new hire a first onboarding to-do.
Watch out
Employee ID, Name and Description are all required, so the Zap must carry the employee's ID from a previous step; a name alone will not do.
Searches

PeopleForce searches: find by ID

2 search steps look for data that already exists in PeopleForce, so a later step can use it.

Searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step, so it needs a paid plan. Whether a search wants the exact value is decided by PeopleForce, not by Zapier.

1

Find Candidate

Search

In Zapier“Finds a Candidate by ID.”

Looks up one candidate in PeopleForce from a Candidate ID and hands that record to the steps that follow.

When to use it
a Zap that starts in another tool holds a candidate's ID and needs the rest of the profile.
Watch out
the Candidate ID is required and is the only way in, so a Zap holding just a name cannot use this search.
2

Find Employee

Search

In Zapier“Finds an Employee by ID.”

Fetches an employee's record from an Employee ID, so a later step can use details the trigger did not carry.

When to use it
just before Create Task, when the Zap needs to confirm who the task is for.
Watch out
on its default setting, an ID that matches nobody stops the Zap at this step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. PeopleForce offers no find-or-create, so its two searches never show it.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When a PeopleForce Zap breaks

Zapier attaches no help article to PeopleForce, and no rate limit specific to it is documented. What breaks is what breaks on any Zap.

  • The past is never replayed

    A Zap reacts only to what happens after it is published. Employees hired last month or leave approved yesterday will not come through; moving that backlog is a separate job.

  • A big import gets held back

    Add a whole team at once and the trigger receives a huge batch. Zapier's flood protection can hold it back instead of running every item.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches starts itself again and again, and burns through the task count fast.

  • A search that finds nobody

    With the default setting, a Find Employee or Find Candidate on an unknown ID stops the run there, and Create Task after it never happens.
Need help

Need help automating PeopleForce with Zapier?

A person reads every message.

FAQ

PeopleForce and Zapier: common questions

01Is the PeopleForce Zapier integration free?
Yes, on Zapier's side. PeopleForce is not a premium app, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: the free plan only builds two-step Zaps, one trigger and one action. Employee Created followed by Create Task fits. Add a filter, a second action or one of the two searches, and the Zap becomes multi-step, which needs a paid plan. Your PeopleForce subscription is a separate matter that Zapier does not handle.
02How many tasks does a PeopleForce Zap use?
One per successful action, and nothing for the trigger. A Zap that starts on Leave Request Approved and runs Create Task once uses one task per approved request. A Zap with three actions uses three each time it runs. An action that fails is not counted against your plan. Since PeopleForce has a single action of its own, most of your count will come from the actions you add in other tools after the trigger, so the number of HR events you expect is the number to watch.
03Is PeopleForce on Zapier real time?
Yes, for all 13 triggers. Each one is instant: PeopleForce reports the event to Zapier itself, so the Zap starts right away whatever your plan. The polling intervals of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, only apply to polling triggers, and PeopleForce has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. Keep in mind that this speed covers the start of the Zap; each following step still has to run and succeed.
04What do you need to connect PeopleForce to Zapier?
A PeopleForce account, and read or write access on anything you do not own but want the Zap to touch. The connection itself takes three moves: open the Apps page of your Zapier account and click + Add connection, search for PeopleForce and click Add connection, then sign in to PeopleForce in the tab that opens and grant Zapier access. The connection is saved once and every PeopleForce step reuses it. Use an account that can see the employees and candidates your Zaps will work on.
05Why can't Create Task find an employee by name?
Because Create Task asks for an Employee ID, not a name, and that field is required along with Name and Description. The same goes for the searches: Find Employee takes an Employee ID, Find Candidate a Candidate ID. In practice, start the Zap on a PeopleForce trigger that concerns an employee, such as Employee Created, and map the ID from it. A Zap that starts in another tool and only knows someone's name has no way to look that person up through these two searches.
06What if the PeopleForce operation you need isn't there?
Then Zapier cannot do it for this app today. The list is short on the writing side: Create Task is the only action, and Find Candidate and Find Employee are the only searches. Creating employees, approving leave or editing salaries from a Zap is not offered. Check the operation list on Zapier's app page before you plan a workflow around a missing step, and plan for a person to do that step in PeopleForce while the Zap handles the rest.
07Zapier, Make or n8n for PeopleForce?
Decide by criteria rather than by brand. On Zapier, PeopleForce gives 13 instant triggers, one action and two ID searches, works on the free plan, and the free plan stops at two-step Zaps. So ask three things of each tool: does it offer the PeopleForce events you need, can it write what you need written back into PeopleForce, and what does a Zap with a filter or a search cost you there. The answer depends on your workflow, not on a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations