Zapier

Trigger Zapier workflows from PeopleForce events

Automation / Requires Professional plan

PeopleForce is in the Zapier app directory. Connect it once with a Company API key, and a change in hiring, people or leave data can start a Zap in the tools your team already works in.

Mechanics

What PeopleForce and Zapier exchange

The PeopleForce app in Zapier offers 13 triggers and 3 actions. PeopleForce pushes each event to Zapier as it happens, so Zapier never has to poll for changes.

What is sentDirectionWhenData
Hiring events
Applicant Created, Vacancy Offer Accepted, Vacancy Offer Rejected
PeopleForce Zapier
as the record is saved
candidates from connected job boards arrive with the board’s scheduled sync
candidate record; offer record
People events
Employee Created, Employee Updated, Employee Terminated, Employee Position Created, Employee Position Updated
PeopleForce Zapier
as the change is saved
future-dated changes: overnight on that date; scheduled termination: overnight once the date has passed
employee profile; position record
Compensation events
Employee Salary Created, Employee Salary Updated
PeopleForce Zapier
as the record is saved
amount, currency, period, effective date, employee
Leave events
Leave Request Approved, Leave Request Rejected, Leave Request Withdrawn
PeopleForce Zapier
when the request reaches that status
leave request record
Create Task
action
Zapier PeopleForce
when the Zap step runs
assigned to the same employee
task name, description, start and end dates
Find Employee, Find Candidate
searches
PeopleForce Zapier
when the Zap step runs
lookup by ID
the employee or candidate record, for the next step

Every read and write a Zap makes goes through the PeopleForce API with your Company key, so the key's permissions decide what a Zap can reach. Changes made through it are recorded under the key's name.

icon
Need an event the Zapier app doesn't offer?
PeopleForce publishes 36 webhook events you can subscribe to directly

Setup

How to connect PeopleForce to Zapier

Three steps, no developer needed. PeopleForce holds the record; Zapier decides what happens next.

1. Create a Company API key

In PeopleForce, open Settings → Security → API keys, select New and choose the Company type. This takes an administrator or a role with the API keys permission. Name the key after the Zap.
1. Create a Company API key

2. Connect the account in Zapier

Add PeopleForce as an app in Zapier and paste the key when Zapier asks to connect the account.
2. Connect the account in Zapier

3. Turn on a Zap

Choose a trigger, pick the app on the other side and turn the Zap on. It subscribes to that one event by itself and appears under Settings → Webhooks, where it can be paused or deleted.
3. Turn on a Zap

Use cases

What teams build with it

Zapier earns its place where PeopleForce hands off to systems the rest of the company runs.

Equipment for a new hire

Employee Created opens a ticket in the IT team’s service desk queue to prepare and ship a laptop before day one.

Access removal on the last day

Employee Terminated closes accounts and paid seats in Okta, AWS or GitHub once the termination date has passed.

Salary data in company analytics

Employee Salary Updated sends each salary change into Power BI or the company data warehouse, next to revenue and budget data.

Frequently asked questions

What administrators ask while connecting Zapier.

Step-by-step guide in the help center

Which plan includes the Zapier integration?

Which API key does Zapier need?

What if the trigger we need isn’t in the list?

See which of your workflows PeopleForce can start

We will walk through the events your team would use, from a new hire to a last working day, and where each one lands in your other tools.