Resources · Zapier integration

Factorial Zapier integrationAutomate Factorial with Zapier.

The Factorial Zapier integration gives you 111 triggers, 228 actions and 206 searches. Every trigger is instant and the app is not premium. Below: what it really costs, how to connect the account, a first Zap to copy, and what breaks.

See the 545 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Factorial Zapier integration does for you

The Factorial Zapier integration links your HR platform for small and mid-sized companies to the rest of your tools, with no code. A Zap waits for an event in Factorial, such as a new application or an approved leave, then acts in Factorial or elsewhere. All 111 triggers are instant, so nothing waits for a timer.

Three results come up again and again. A hiring pipeline that moves on its own: Creates an Application starts the Zap and Creates a Task hands the screening to the right person. Onboarding without the checklist chase: Creates an Employee fires as soon as someone joins, and Creates a Membership puts them in their team. Time and absence data that travels: Approves a Leave or Clock Out for Shift passes what happened in Factorial to whoever needs it, the moment it happens, instead of waiting for someone to export a report.

What Zapier does not do here: it never picks up records created before the Zap was switched on, and none of the 206 searches offers a create-if-missing option. Every trigger also asks for your company identifier, which is easy to miss the first time.

Weighing another tool for the same job? The Factorial Make integration page covers this app on Make, and n8n vs Zapier compares the two platforms.

Vocabulary

Zapier vocabulary in one minute

Seven words, and the rest of the page reads easily.

Zap: The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger: The event in Factorial that starts the Zap, such as a new candidate. 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, in Factorial or elsewhere.
Task: The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Instant vs polling: An instant trigger is reported by the app the moment it happens; a polling one is checked on a timer. Factorial's are all instant.
Filter: A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step: A step that looks up something that already exists in an app, so the steps after it can use what it found.

Cost

What a Factorial Zap really costs

Short version: the trigger is free, each action that works is one task.

Trigger0 tasks
Action that works1 task
Free plan100 tasks a month, 2 steps
Premium appNo

Factorial is not a premium app, so it works on the free plan. That plan gives you 100 tasks a month and Zaps of two steps: one trigger, one action, nothing more. The trigger never costs a task, and an action that fails is not counted. A second action, a filter or a search makes the Zap multi-step, which needs a paid plan. The interval grid below only concerns polling triggers: every Factorial trigger is instant, so it starts right away whatever your plan.

Connect

Connect Factorial to Zapier in three steps

01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need an existing Factorial account, plus read or write access to anything you do not own and want the Zap to touch.
02
Pick Factorial
Type Factorial in the search box of the dialog and select it, then click Add connection. Factorial's sign-in opens in a new tab, so keep your login at hand.
03
Sign in and grant access
Sign in to Factorial in that tab and grant Zapier access to the account. From then on, every Factorial step of every Zap reuses this connection, so you only do this once.

First Zap

Your first Zap: screen each new application

GoalEach new application in Factorial creates a screening task, but only when it meets your rule.

01
Build: pick the trigger
In Build, pick Factorial as the app that starts the Zap and Creates an Application as the event, then choose the connection you just made.
02
Set and test the trigger
Fill in your company identifier, the one required field. Then test: Zapier brings back the three most recent applications of the account, so you map on a real one.
03
Add the filter
Click the plus icon, add Filter, then set the field to look at, the rule and the value. Use a text rule on text and a number rule on numbers, or it never passes.
04
Add the action
Add Factorial again and choose Creates a Task. Name and status are required; map details from the trigger into the name so the hiring manager knows which application it is about.
05
Test, then publish
Run Test on each step and read what came back. When it looks right, click Publish to switch the Zap on. With a filter it is multi-step, so it needs a paid plan.

Factorial gives you 228 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

Deletes a Webhook Subscription

Action

In Zapier“Deletes a Webhook subscription”

Delete a webhook subscription from Factorial.

When to use it

At a SaaS company where IT audits each data flow, it removes the webhook subscription once another tool says it is no longer needed.

Watch out

The step needs the ID of the webhook subscription; a search such as Reads All Webhook Subscriptions placed just before can find it.

Updates a Webhook Subscription

Action

In Zapier“Updates a Webhook subscription”

Update a webhook subscription that already exists in Factorial.

When to use it

For a consultant wiring Factorial into a client's stack of tools, it keeps the webhook subscription in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the webhook subscription; a search such as Reads All Webhook Subscriptions placed just before can find it.

Creates a Webhook Subscription

Action

In Zapier“Creates a Webhook subscription”

Create a webhook subscription in Factorial from data another step brings in.

When to use it

For an in-house ops engineer who owns every HR integration, it creates the webhook subscription from what the trigger just brought in, with no double entry.

Watch out

company_id is required here; a run that leaves it empty fails, and a failed action costs no task.

Applies an Application

Action

In Zapier“Apply to a job posting”

Submit an application to a job posting on behalf of a candidate, with their name and email.

When to use it

At a seed-stage startup with a one-person talent team, it takes this chore off someone's list for good.

Watch out

Four fields are required here, including first_name and last_name; a run that leaves one empty fails, and a failed action costs no task.

Deletes an Application

Action

In Zapier“Deletes an Application”

Delete an application from Factorial.

When to use it

For a staffing firm juggling several hiring managers, it removes the application once another tool says it is no longer needed.

Watch out

The step needs the ID of the application; a search such as Reads All Applications placed just before can find it.

Updates an Application

Action

In Zapier“Updates an Application”

Update an application that already exists in Factorial.

When to use it

For a remote-first agency hiring across time zones, it keeps the application in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the application; a search such as Reads All Applications placed just before can find it.

Creates an Application

Action

In Zapier“Creates an Application”

Create an application in Factorial from data another step brings in.

When to use it

At a seed-stage startup with a one-person talent team, it creates the application from what the trigger just brought in, with no double entry.

Watch out

ats_job_posting_id is required here; a run that leaves it empty fails, and a failed action costs no task.

Deletes a Candidate

Action

In Zapier“Deletes a candidate from the ATS”

Delete a candidate from Factorial.

When to use it

For a staffing firm juggling several hiring managers, it clears out the candidate instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the candidate; a search such as Reads All Candidates placed just before can find it.

Updates a Candidate

Action

In Zapier“Updates ATS Candidates data”

Update a candidate that already exists in Factorial.

When to use it

For a remote-first agency hiring across time zones, it brings the candidate up to date when the information changes in another tool.

Watch out

The step needs the ID of the candidate; a search such as Reads All Candidates placed just before can find it.

Creates a Candidate

Action

In Zapier“Creates candidates related to a particular company in an ATS”

Create a candidate in Factorial from data another step brings in.

When to use it

At a seed-stage startup with a one-person talent team, it saves someone from typing the candidate into Factorial by hand.

Watch out

Three fields are required here, including first_name and last_name; a run that leaves one empty fails, and a failed action costs no task.

Saves as Template an Evaluation Form

Action

In Zapier“Save an evaluation form as a template.”

Save an existing evaluation form as a reusable template.

When to use it

For a staffing firm juggling several hiring managers, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the evaluation form; a search such as Reads All Evaluation Forms placed just before can find it.

Deletes a Feedback

Action

In Zapier“This endpoint allows to delete a specific feedback entry associated with a candidate's application.”

Delete an interview feedback from Factorial.

When to use it

For a remote-first agency hiring across time zones, it clears out the interview feedback instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the interview feedback; a search such as Reads All Feedbacks placed just before can find it.

Updates a Feedback

Action

In Zapier“This endpoint allows to update existing feedback entries associated with candidates' applications.”

Update an interview feedback that already exists in Factorial.

When to use it

At a seed-stage startup with a one-person talent team, it brings the interview feedback up to date when the information changes in another tool.

Watch out

Every field is optional here, so run one test with real values before you publish.

Creates a Feedback

Action

In Zapier“This endpoint allows to create new feedback entries for candidates.”

Create an interview feedback in Factorial from data another step brings in.

When to use it

For a staffing firm juggling several hiring managers, it saves someone from typing the interview feedback into Factorial by hand.

Watch out

ats_candidate_id is required here; a run that leaves it empty fails, and a failed action costs no task.

Duplicates a Job Posting

Action

In Zapier“Duplicate an existing job posting.”

Copy an existing job posting to open a new one from it.

When to use it

For a remote-first agency hiring across time zones, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the job posting; a search such as Reads All Job Postings placed just before can find it.

Deletes a Job Posting

Action

In Zapier“Delete a job posting.”

Delete a job posting from Factorial.

When to use it

At a seed-stage startup with a one-person talent team, it clears out the job posting instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the job posting; a search such as Reads All Job Postings placed just before can find it.

Updates a Job Posting

Action

In Zapier“Update a job posting.”

Update a job posting that already exists in Factorial.

When to use it

For a staffing firm juggling several hiring managers, it brings the job posting up to date when the information changes in another tool.

Watch out

The step needs the ID of the job posting; a search such as Reads All Job Postings placed just before can find it.

Creates a Job Posting

Action

In Zapier“Create a new job posting.”

Create a job posting in Factorial from data another step brings in.

When to use it

For a remote-first agency hiring across time zones, it saves someone from typing the job posting into Factorial by hand.

Watch out

Six fields are required here, including title and status; a run that leaves one empty fails, and a failed action costs no task.

Creates a Message

Action

In Zapier“Creates a Message”

Add a candidate message to Factorial without opening the app.

When to use it

At a seed-stage startup with a one-person talent team, it creates the candidate message from what the trigger just brought in, with no double entry.

Watch out

Seven fields are required here, including content and sent_by_id; a run that leaves one empty fails, and a failed action costs no task.

Updates a Break Configuration

Action

In Zapier“Updates a Break configuration”

Update an attendance break setting that already exists in Factorial.

When to use it

For a field-service company with technicians on the road, it keeps the attendance break setting in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the attendance break setting; a search such as Reads All Break Configurations placed just before can find it.

Creates a Break Configuration

Action

In Zapier“Creates a Break configuration”

Create an attendance break setting in Factorial from data another step brings in.

When to use it

For a warehouse running early and late crews, it creates the attendance break setting from what the trigger just brought in, with no double entry.

Watch out

Three fields are required here, including time_settings_break_configuration_id and attendance_employees_setting_id; a run that leaves one empty fails, and a failed action costs no task.

Deletes an Edit Timesheet Request

Action

In Zapier“Deletes an edit timesheet.”

Delete a timesheet edit request from Factorial.

When to use it

At a coffee chain where baristas clock in on a tablet, it clears out the timesheet edit request instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the timesheet edit request; a search such as Reads All Edit Timesheet Requests placed just before can find it.

Updates an Edit Timesheet Request

Action

In Zapier“Updates an edit timesheet request by specifying the fields required to update the shift.”

Update a timesheet edit request that already exists in Factorial.

When to use it

For a field-service company with technicians on the road, it brings the timesheet edit request up to date when the information changes in another tool.

Watch out

The step needs the ID of the timesheet edit request; a search such as Reads All Edit Timesheet Requests placed just before can find it.

Creates an Edit Timesheet Request

Action

In Zapier“Creates an edit timesheet request by specifying the type of the request and the fields required to create or update the shift.”

Create a timesheet edit request in Factorial from data another step brings in.

When to use it

For a warehouse running early and late crews, it saves someone from typing the timesheet edit request into Factorial by hand.

Watch out

Two fields are required here, including employee_id and request_type; a run that leaves one empty fails, and a failed action costs no task.

Approves an Overtime Request

Action

In Zapier“Approves an Overtime request”

Approve an overtime request in Factorial without opening it yourself.

When to use it

At a coffee chain where baristas clock in on a tablet, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the overtime request; a search such as Reads All Overtime Requests placed just before can find it.

Deletes an Overtime Request

Action

In Zapier“Deletes an Overtime request”

Delete an overtime request from Factorial.

When to use it

For a field-service company with technicians on the road, it clears out the overtime request instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the overtime request; a search such as Reads All Overtime Requests placed just before can find it.

Updates an Overtime Request

Action

In Zapier“Updates an Overtime request”

Update an overtime request that already exists in Factorial.

When to use it

For a warehouse running early and late crews, it brings the overtime request up to date when the information changes in another tool.

Watch out

The step needs the ID of the overtime request; a search such as Reads All Overtime Requests placed just before can find it.

Creates an Overtime Request

Action

In Zapier“Creates an Overtime request”

Create an overtime request in Factorial from data another step brings in.

When to use it

At a coffee chain where baristas clock in on a tablet, it saves someone from typing the overtime request into Factorial by hand.

Watch out

Three fields are required here, including date and employee_id; a run that leaves one empty fails, and a failed action costs no task.

Rejects an Overtime Request

Action

In Zapier“Rejects an Overtime request”

Turn down an overtime request and record the reason for it.

When to use it

For a field-service company with technicians on the road, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the overtime request; a search such as Reads All Overtime Requests placed just before can find it.

Autofills a Shift

Action

In Zapier“Autofills a Shift”

Fill in shifts automatically for a list of employees over a date range.

When to use it

For a warehouse running early and late crews, it takes this chore off someone's list for good.

Watch out

Three fields are required here, including employee_ids and start_on; a run that leaves one empty fails, and a failed action costs no task.

Break Ends a Shift

Action

In Zapier“Given that attendance breaks are enabled, this endpoint ends a break in an open shift.”

End the break currently running in an open shift.

When to use it

At a coffee chain where baristas clock in on a tablet, it does this for you the moment the chosen trigger fires.

Watch out

Attendance breaks must be enabled for the employee, or the step has nothing to end.

Break Starts a Shift

Action

In Zapier“Given that attendance breaks are enabled, this endpoint starts a break in an open shift.”

Start a break inside a shift that is still open.

When to use it

For a field-service company with technicians on the road, it takes this chore off someone's list for good.

Watch out

Attendance breaks must be enabled before this step can open one.

Clocks in a Shift

Action

In Zapier“Records the start of a shift by setting the current time as the clock-in. The shift remains open and will not have a clock-out time until explicitly updated. If you need to clock out directly, consider using or subscribing to the clock-out endpoint”

Clock an employee in, using the current time as the start of the shift.

When to use it

For a warehouse running early and late crews, it does this for you the moment the chosen trigger fires.

Watch out

The shift stays open with no clock-out until something closes it, such as Clocks Out a Shift.

Clocks Out a Shift

Action

In Zapier“Completes an open shift by setting the current time as the clock-out. This action only applies to shifts that were previously started using clock_in. If you need to clock in directly, consider using or subscribing to the clock-in endpoint”

Close an open shift by clocking out at the current time.

When to use it

At a coffee chain where baristas clock in on a tablet, it takes this chore off someone's list for good.

Watch out

It only closes shifts that were opened by a clock-in in the first place.

Deletes a Shift

Action

In Zapier“Deletes a Shift”

Delete an attendance shift from Factorial.

When to use it

For a field-service company with technicians on the road, it removes the attendance shift once another tool says it is no longer needed.

Watch out

The step needs the ID of the attendance shift; a search such as Reads All Shifts placed just before can find it.

Updates a Shift

Action

In Zapier“Updates a Shift”

Change the details of an attendance shift in Factorial from the Zap.

When to use it

For a warehouse running early and late crews, it keeps the attendance shift in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the attendance shift; a search such as Reads All Shifts placed just before can find it.

Creates a Shift

Action

In Zapier“Creates a complete shift by specifying both the clock-in and clock-out times. If you need to clock in directly, consider using or subscribing to the clock-in endpoint”

Add an attendance shift to Factorial without opening the app.

When to use it

At a coffee chain where baristas clock in on a tablet, it creates the attendance shift from what the trigger just brought in, with no double entry.

Watch out

This one records a complete shift, start and end together; to clock someone in right now, Clocks in a Shift is the right step.

Clock In/Out a Shift

Action

In Zapier“Use this endpoint to toggle shift (it will clock in or out)”

Toggle an employee's clock: the step records a clock-in or a clock-out depending on where the shift stands.

When to use it

For a field-service company with technicians on the road, it takes this chore off someone's list for good.

Watch out

Two fields are required here, including employee_id and clock_time; a run that leaves one empty fails, and a failed action costs no task.

Updates a Bookkeepers Management Incidence

Action

In Zapier“Updates an Incidence”

Update a bookkeeping incidence that already exists in Factorial.

When to use it

For a finance lead who closes payroll with an outside accountant, it brings the bookkeeping incidence up to date when the information changes in another tool.

Watch out

The step needs the ID of the bookkeeping incidence; a search such as Reads All Bookkeepers Management Incidences placed just before can find it.

Deletes a Compensation

Action

In Zapier“Deletes a Compensation”

Delete a compensation from Factorial.

When to use it

At a company where contract changes go to the CFO for sign-off, it clears out the compensation instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the compensation; a search such as Reads All Compensations placed just before can find it.

Updates a Compensation

Action

In Zapier“Updates a Compensation”

Update a compensation that already exists in Factorial.

When to use it

For an HR team running a compensation review, it brings the compensation up to date when the information changes in another tool.

Watch out

contracts_taxonomy_id is required here; a run that leaves it empty fails, and a failed action costs no task.

Creates a Compensation

Action

In Zapier“Creates a Compensation”

Create a compensation in Factorial from data another step brings in.

When to use it

For a people-ops lead handling raises and contract renewals, it saves someone from typing the compensation into Factorial by hand.

Watch out

Two fields are required here, including contract_version_id and contracts_taxonomy_id; a run that leaves one empty fails, and a failed action costs no task.

Deletes a Contract Version

Action

In Zapier“Deletes a Contract version”

Delete a contract version from Factorial.

When to use it

At a company where contract changes go to the CFO for sign-off, it removes the contract version once another tool says it is no longer needed.

Watch out

The step needs the ID of the contract version; a search such as Reads All Contract Versions placed just before can find it.

Updates a Contract Version

Action

In Zapier“Updates a Contract version”

Update a contract version that already exists in Factorial.

When to use it

For an HR team running a compensation review, it keeps the contract version in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the contract version; a search such as Reads All Contract Versions placed just before can find it.

Creates a Contract Version

Action

In Zapier“Creates a Contract version”

Create a contract version in Factorial from data another step brings in.

When to use it

For a people-ops lead handling raises and contract renewals, it creates the contract version from what the trigger just brought in, with no double entry.

Watch out

Three fields are required here, including employee_id and effective_on; a run that leaves one empty fails, and a failed action costs no task.

Deletes a Field

Action

In Zapier“Deletes a Field”

Delete a custom field from Factorial.

When to use it

At a company that stores visa or equipment details on employee profiles, it clears out the custom field instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the custom field; a search such as Reads All Fields placed just before can find it.

Creates a Field

Action

In Zapier“Creates a Field”

Create a custom field in Factorial from data another step brings in.

When to use it

For a team that built its own records inside Factorial, it creates the custom field from what the trigger just brought in, with no double entry.

Watch out

Two fields are required here, including company_id and field_type; a run that leaves one empty fails, and a failed action costs no task.

Creates a Custom Field Option

Action

In Zapier“Creates an Option”

Add a custom field option to Factorial without opening the app.

When to use it

For an HR admin who tracks data Factorial has no standard field for, it saves someone from typing the custom field option into Factorial by hand.

Watch out

Two fields are required here, including label and field_id; a run that leaves one empty fails, and a failed action costs no task.

Updates a Custom Resource Field

Action

In Zapier“Creates an schema custom field”

Add a field to a custom resource schema, with its type and whether it is required, editable and visible.

When to use it

At a company that stores visa or equipment details on employee profiles, it does this for you the moment the chosen trigger fires.

Watch out

Six fields are required here, including schema_id and company_id; a run that leaves one empty fails, and a failed action costs no task.

Updates a Value

Action

In Zapier“Updates a Value”

Update a custom field value that already exists in Factorial.

When to use it

For a team that built its own records inside Factorial, it keeps the custom field value in Factorial aligned with what another tool says.

Watch out

Every field is optional here, so run one test with real values before you publish.

Creates a Value

Action

In Zapier“Creates a Value”

Custom field value creation, done by the Zap instead of by hand.

When to use it

For an HR admin who tracks data Factorial has no standard field for, it creates the custom field value from what the trigger just brought in, with no double entry.

Watch out

Four fields are required here, including field_id and valuable_type; a run that leaves one empty fails, and a failed action costs no task.

Creates a Schema

Action

In Zapier“Creates a Schema”

Custom resource schema creation, done by the Zap instead of by hand.

When to use it

At a company that stores visa or equipment details on employee profiles, it saves someone from typing the custom resource schema into Factorial by hand.

Watch out

Three fields are required here, including name and company_id; a run that leaves one empty fails, and a failed action costs no task.

Creates a Value

Action

In Zapier“Creates a Value”

Custom resource value creation, done by the Zap instead of by hand.

When to use it

For a team that built its own records inside Factorial, it creates the custom resource value from what the trigger just brought in, with no double entry.

Watch out

Four fields are required here, including schema_id and employee_id; a run that leaves one empty fails, and a failed action costs no task.

Deletes a Document

Action

In Zapier“Deletes a Document”

Delete a document from Factorial.

When to use it

For an HR team chasing signed policies, it clears out the document instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the document; a search such as Reads All Documents placed just before can find it.

Updates a Document

Action

In Zapier“Updates a Document”

Update a document that already exists in Factorial.

When to use it

At a company that keeps payslips and contracts in one place, it brings the document up to date when the information changes in another tool.

Watch out

The step needs the ID of the document; a search such as Reads All Documents placed just before can find it.

Move to Trash Bins a Document

Action

In Zapier“This endpoint moves the documents to the trash bin, after 30 days they will be deleted from the system.”

Send one or several documents to Factorial's trash bin.

When to use it

For an office manager filing onboarding paperwork, it takes this chore off someone's list for good.

Watch out

Documents left in the trash bin are deleted from Factorial after 30 days.

Creates a Document

Action

In Zapier“Creates a Document”

Create a document in Factorial from data another step brings in.

When to use it

For an HR team chasing signed policies, it creates the document from what the trigger just brought in, with no double entry.

Watch out

Eight fields are required here, including public and space; a run that leaves one empty fails, and a failed action costs no task.

Restore From Trash Bins a Document

Action

In Zapier“This endpoint restores the documents from the trash bin, remember that a document in the trash bin will be deleted from the system after 30 days.”

Bring documents back out of the trash bin before they are erased.

When to use it

At a company that keeps payslips and contracts in one place, it takes this chore off someone's list for good.

Watch out

Past 30 days in the trash bin, there is nothing left to restore.

Bulk Creates a Download URL

Action

In Zapier“This endpoint generate temporal urls for a list of documents. The urls let you download the documents.”

Generate temporary download links for a list of documents.

When to use it

For an office manager filing onboarding paperwork, it does this for you the moment the chosen trigger fires.

Watch out

The links are temporary, so send them on rather than storing them for later.

Updates a Folder

Action

In Zapier“Update a folder.”

Update a folder that already exists in Factorial.

When to use it

For an HR team chasing signed policies, it keeps the folder in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the folder; a search such as Reads All Folders placed just before can find it.

Creates a Folder

Action

In Zapier“Create a folder.”

Create a folder in Factorial from data another step brings in.

When to use it

At a company that keeps payslips and contracts in one place, it creates the folder from what the trigger just brought in, with no double entry.

Watch out

Three fields are required here, including company_id and name; a run that leaves one empty fails, and a failed action costs no task.

Create With Contracts an Employee

Action

In Zapier“Create an employee with a contract”

Create an employee and their contract in a single step.

When to use it

For an HR team that keeps a directory in sync with other tools, it takes this chore off someone's list for good.

Watch out

Four fields are required here, including company_id and first_name; a run that leaves one empty fails, and a failed action costs no task.

Updates an Employee

Action

In Zapier“Updates an Employee”

Update an employee that already exists in Factorial.

When to use it

For a fast-hiring startup onboarding new joiners, it brings the employee up to date when the information changes in another tool.

Watch out

The step needs the ID of the employee; a search such as Reads All Employees placed just before can find it.

Invites an Employee

Action

In Zapier“Send an email invitation to an unconfirmed employee to join Factorial”

Email an invitation to an employee who has not confirmed their Factorial account yet.

When to use it

At a company where IT provisions laptops for each hire, it takes this chore off someone's list for good.

Watch out

The invitation only goes to an employee whose account is still unconfirmed.

Terminates an Employee

Action

In Zapier“Terminates an Employee”

Record an employee's termination, with the date it takes effect.

When to use it

For an HR team that keeps a directory in sync with other tools, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the employee; a search such as Reads All Employees placed just before can find it.

Unterminates an Employee

Action

In Zapier“Unterminates an Employee”

Cancel an employee's termination.

When to use it

For a fast-hiring startup onboarding new joiners, it takes this chore off someone's list for good.

Watch out

The step needs the ID of the employee; a search such as Reads All Employees placed just before can find it.

Creates an Account

Action

In Zapier“Create a ledger account for the company legal_entity. To avoid duplicates use the external_id field to set the ID of the ledger account in the external system.”

Create a ledger account in Factorial from data another step brings in.

When to use it

At a company that books payroll into its general ledger, it creates the ledger account from what the trigger just brought in, with no double entry.

Watch out

Fill the external_id field with the account's ID in your other system, which is how Factorial avoids duplicates.

Bulk Create Updates a Cost Center Membership

Action

In Zapier“What does it do? Performs an update of cost center memberships for an employee. The action creates new memberships starting from today, terminating any pre-existing memberships for the employee. This ensures a history of cost center memberships is preserved. ###### What does the `memberships` array look like? An array of objects with these properties: - `cost_center_id` - `percentage`: A float between 0 and 1 representing the percentage that the employee is assigned to the cost center. For multiple assignments, the sum of percentages must equal 1.0. For example, for an employee assigned to cost center 1 during 30% of their time and cost center 2 during 70% of their time, the request parameters would look like: `memberships[][cost_center_id]=1&memberships[][percentage]=0.3&memberships[][cost_center_id]=2&memberships[][percentage]=0.7`”

Reset an employee's cost center split: the new memberships start today and the previous ones are closed.

When to use it

For a controller who tracks headcount cost per cost center, it takes this chore off someone's list for good.

Watch out

Factorial keeps the history of the previous memberships, so the old split does not vanish.

Edits a Cost Center

Action

In Zapier“Edits a Cost center”

Edit a cost center already set up in Factorial.

When to use it

For a CFO splitting salary costs by department, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the cost center; a search such as Reads All Cost Centers placed just before can find it.

Deletes a Cost Center

Action

In Zapier“Deletes a Cost center”

Delete a cost center from Factorial.

When to use it

At a company that books payroll into its general ledger, it clears out the cost center instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the cost center; a search such as Reads All Cost Centers placed just before can find it.

Creates a Cost Center

Action

In Zapier“Creates a Cost center”

Create a cost center in Factorial from data another step brings in.

When to use it

For a controller who tracks headcount cost per cost center, it creates the cost center from what the trigger just brought in, with no double entry.

Watch out

Two fields are required here, including name and company_id; a run that leaves one empty fails, and a failed action costs no task.

Deletes a Location

Action

In Zapier“Deletes a Location”

Delete a location from Factorial.

When to use it

For a retailer opening new stores, it clears out the location instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the location; a search such as Reads All Locations placed just before can find it.

Updates a Location

Action

In Zapier“Updates a Location”

Update a location that already exists in Factorial.

When to use it

At a company with offices in several cities, it brings the location up to date when the information changes in another tool.

Watch out

The step needs the ID of the location; a search such as Reads All Locations placed just before can find it.

Creates a Location

Action

In Zapier“Creates a Location”

Create a location in Factorial from data another step brings in.

When to use it

For an operations lead mapping teams to work areas, it saves someone from typing the location into Factorial by hand.

Watch out

Four fields are required here, including name and country; a run that leaves one empty fails, and a failed action costs no task.

Archives a Work Area

Action

In Zapier“Archives a Work area”

Archive a work area that is no longer in use.

When to use it

For a retailer opening new stores, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the work area; a search such as Reads All Work Areas placed just before can find it.

Updates a Work Area

Action

In Zapier“Updates a Work area”

Update a work area that already exists in Factorial.

When to use it

At a company with offices in several cities, it keeps the work area in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the work area; a search such as Reads All Work Areas placed just before can find it.

Creates a Work Area

Action

In Zapier“Creates a Work area”

Create a work area in Factorial from data another step brings in.

When to use it

For an operations lead mapping teams to work areas, it creates the work area from what the trigger just brought in, with no double entry.

Watch out

Two fields are required here, including name and location_id; a run that leaves one empty fails, and a failed action costs no task.

Unarchives a Work Area

Action

In Zapier“Unarchives a Work area”

Bring an archived work area back into use.

When to use it

For a retailer opening new stores, it takes this chore off someone's list for good.

Watch out

The step needs the ID of the work area; a search such as Reads All Work Areas placed just before can find it.

Deletes an Identifier

Action

In Zapier“Reads Payroll employee identifier codes, current countries supported are Portugal, Italy and Germany”

Delete a payroll identifier from Factorial.

When to use it

At a US subsidiary that sends data to a payroll bureau, it removes the payroll identifier once another tool says it is no longer needed.

Watch out

These identifiers only cover Portugal, Italy and Germany for now.

Updates an Identifier

Action

In Zapier“Reads Payroll employee identifier codes, current countries supported are Portugal, Italy and Germany”

Update a payroll identifier that already exists in Factorial.

When to use it

For a controller reconciling payroll inputs line by line, it keeps the payroll identifier in Factorial aligned with what another tool says.

Watch out

These identifiers only cover Portugal, Italy and Germany for now.

Creates an Identifier

Action

In Zapier“Reads Payroll employee identifier codes, current countries supported are Portugal, Italy and Germany”

Create a payroll identifier in Factorial from data another step brings in.

When to use it

For a finance lead who closes payroll with an outside accountant, it creates the payroll identifier from what the trigger just brought in, with no double entry.

Watch out

These identifiers only cover Portugal, Italy and Germany for now.

Updates a Family Situation

Action

In Zapier“Update a family situation.”

Update a family situation that already exists in Factorial.

When to use it

At a US subsidiary that sends data to a payroll bureau, it keeps the family situation in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the family situation; a search such as Reads All Family Situations placed just before can find it.

Creates a Family Situation

Action

In Zapier“Create a family situation.”

Create a family situation in Factorial from data another step brings in.

When to use it

For a controller reconciling payroll inputs line by line, it creates the family situation from what the trigger just brought in, with no double entry.

Watch out

employee_id is required here; a run that leaves it empty fails, and a failed action costs no task.

Deletes a Code

Action

In Zapier“Deletes a Code”

Remove a payroll integration code from Factorial without opening the app.

When to use it

For a finance lead who closes payroll with an outside accountant, it clears out the payroll integration code instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the payroll integration code; a search such as Reads All Codes placed just before can find it.

Updates a Code

Action

In Zapier“Updates a Code”

Payroll integration code details, rewritten in Factorial by the Zap.

When to use it

At a US subsidiary that sends data to a payroll bureau, it brings the payroll integration code up to date when the information changes in another tool.

Watch out

The step needs the ID of the payroll integration code; a search such as Reads All Codes placed just before can find it.

Creates a Code

Action

In Zapier“Creates a Code”

Add a payroll integration code to Factorial without opening the app.

When to use it

For a controller reconciling payroll inputs line by line, it saves someone from typing the payroll integration code into Factorial by hand.

Watch out

Four fields are required here, including code and codeable_id; a run that leaves one empty fails, and a failed action costs no task.

Change Statuses a Policy Period

Action

In Zapier“Change statuses a Policy period”

Change the status of a payroll policy period for a list of employees, and choose whether to notify them.

When to use it

For a finance lead who closes payroll with an outside accountant, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the policy period; map it from the trigger or an earlier step.

Deletes a Supplement

Action

In Zapier“Deletes a Supplement”

Payroll supplement removal, handled by the Zap.

When to use it

At a US subsidiary that sends data to a payroll bureau, it clears out the payroll supplement instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the payroll supplement; a search such as Reads All Supplements placed just before can find it.

Updates a Supplement

Action

In Zapier“Updates a Supplement”

Payroll supplement details, rewritten in Factorial by the Zap.

When to use it

For a controller reconciling payroll inputs line by line, it brings the payroll supplement up to date when the information changes in another tool.

Watch out

The step needs the ID of the payroll supplement; a search such as Reads All Supplements placed just before can find it.

Creates a Supplement

Action

In Zapier“Creates a Supplement”

Payroll supplement creation, done by the Zap instead of by hand.

When to use it

For a finance lead who closes payroll with an outside accountant, it saves someone from typing the payroll supplement into Factorial by hand.

Watch out

Four fields are required here, including amount_in_cents and employee_id; a run that leaves one empty fails, and a failed action costs no task.

Bulk Initiates an Agreement

Action

In Zapier“Initiate the action plan for all your direct reports in a review process. If you are acting as a company, the action plan from all employees in the review process will be initiated.”

Start the action plans of every direct report in a review process at once.

When to use it

At a scale-up rolling out its first structured review cycle, it does this for you the moment the chosen trigger fires.

Watch out

Acting as the company rather than as a manager, it starts the action plans of every employee in the process.

Initiates an Agreement

Action

In Zapier“Initiate the action plan for a review process target ID in a review process.”

Kick off the action plan of a single participant in a review process.

When to use it

For managers who want reviews to lead to action plans, it takes this chore off someone's list for good.

Watch out

Two fields are required here, including process_id and target_id; a run that leaves one empty fails, and a failed action costs no task.

Sets a Company Employee Score Scale

Action

In Zapier“Set the predefined employee score scale for the company.”

Pick which predefined score scale the company uses to rate employees in reviews.

When to use it

For a people team running performance reviews, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the company score scale; a search such as Reads All Company Employee Score Scales placed just before can find it.

Replace Reviewers a Review Evaluation

Action

In Zapier“Define a new reviewer for the evaluation that will only be able to leave feedback about the employee. This can only be done if the process is active, the evaluation is not published and the evaluation type is not "self".”

Hand an evaluation over to a new reviewer, who can only leave feedback on the employee.

When to use it

At a scale-up rolling out its first structured review cycle, it takes this chore off someone's list for good.

Watch out

It only works on an active process, on an evaluation not yet published, and never on a self-review.

Bulk Creates a Review Owner

Action

In Zapier“Add multiple owners to a review process.”

Add several owners to a review process at once.

When to use it

For managers who want reviews to lead to action plans, it does this for you the moment the chosen trigger fires.

Watch out

Two fields are required here, including review_process_id and owner_access_ids; a run that leaves one empty fails, and a failed action costs no task.

Deletes a Review Owner

Action

In Zapier“Remove an owner from a review process. The review process must have at least one owner.”

Delete a review owner from Factorial.

When to use it

For a people team running performance reviews, it clears out the review owner instead of leaving it to a manual clean-up.

Watch out

A review process must keep at least one owner, so the last one cannot be removed.

Duplicates a Review Process

Action

In Zapier“Duplicate an existing review process”

Start the next review process from a copy of an existing one.

When to use it

At a scale-up rolling out its first structured review cycle, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the review process; a search such as Reads All Review Processes placed just before can find it.

Action

In Zapier“Bulk creates a Project worker”

Add several employees to a project at once. Each one becomes a project worker, which is what lets their time be logged against that project later.

When to use it

Two fields are required here, including project_id and employee_ids; a run that leaves one empty fails, and a failed action costs no task.

150

Creates a Project Worker

Action

In Zapier“What does it do? This creates a new project worker. By default, the project worker will be created with the status `assigned`. ###### Who can use it? Only companies who have enabled the `projects_management` feature and users with a role in the given project.”

Project worker creation, done by the Zap instead of by hand.

When to use it

For an agency that bills clients by the hour, it saves someone from typing the project worker into Factorial by hand.

Watch out

The step needs Factorial's project management feature, and a user with the right role in the project.

Action

In Zapier“Create comments a Task”

Deletes a Task

Action

In Zapier“This endpoint deletes a task.”

Remove a task from Factorial without opening the app.

When to use it

At a company where offboarding involves IT, finance and the manager, it removes the task once another tool says it is no longer needed.

Watch out

The step needs the ID of the task; a search such as Reads All Tasks placed just before can find it.

170

Updates a Task

Action

In Zapier“This endpoint updates an existing task.”

Update a task that already exists in Factorial.

When to use it

For a people-ops lead who assigns follow-ups after each review, it keeps the task in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the task; a search such as Reads All Tasks placed just before can find it.

171

Creates a Task

Action

In Zapier“This endpoint creates a new task.”

Add a task to Factorial without opening the app.

When to use it

For an HR team running onboarding checklists, it creates the task from what the trigger just brought in, with no double entry.

Watch out

Two fields are required here, including name and status; a run that leaves one empty fails, and a failed action costs no task.

172

Deletes a Membership

Action

In Zapier“Delete the membership to remove the employee from the team.”

Delete a team membership from Factorial.

When to use it

At a company where team leads approve time off, it clears out the team membership instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the team membership; a search such as Reads All Memberships placed just before can find it.

173

Updates a Membership

Action

In Zapier“Update the membership to either make the employee a lead of the team or remove them as a lead.”

Make a team member the team lead, or take the lead role away.

When to use it

For an ops lead keeping the org chart current, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the team membership; a search such as Reads All Memberships placed just before can find it.

174

Creates a Membership

Action

In Zapier“Assign an employee to a team, meaning create a membership.”

Create a team membership in Factorial from data another step brings in.

When to use it

For a scale-up reorganising into squads, it saves someone from typing the team membership into Factorial by hand.

Watch out

Two fields are required here, including team_id and employee_id; a run that leaves one empty fails, and a failed action costs no task.

175

Deletes a Team

Action

In Zapier“Delete a team”

Remove a team from Factorial without opening the app.

When to use it

At a company where team leads approve time off, it removes the team once another tool says it is no longer needed.

Watch out

The step needs the ID of the team; a search such as Reads All Teams placed just before can find it.

176

Updates a Team

Action

In Zapier“Update a team”

Update a team that already exists in Factorial.

When to use it

For an ops lead keeping the org chart current, it keeps the team in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the team; a search such as Reads All Teams placed just before can find it.

177

Creates a Team

Action

In Zapier“Create a team with a given name”

Add a team to Factorial without opening the app.

When to use it

For a scale-up reorganising into squads, it creates the team from what the trigger just brought in, with no double entry.

Watch out

name is required here; a run that leaves it empty fails, and a failed action costs no task.

178

Deletes an Allowance Incidence

Action

In Zapier“Deletes an allowance incidence”

Delete an allowance adjustment from Factorial.

When to use it

At a company where approved leave must reach the shared calendar, it clears out the allowance adjustment instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the allowance adjustment; a search such as Reads All Allowance Incidences placed just before can find it.

179

Updates an Allowance Incidence

Action

In Zapier“Updates an allowance incidence”

Update an allowance adjustment that already exists in Factorial.

When to use it

For an HR team auditing holiday balances before year-end, it brings the allowance adjustment up to date when the information changes in another tool.

Watch out

The step needs the ID of the allowance adjustment; a search such as Reads All Allowance Incidences placed just before can find it.

180

Creates an Allowance Incidence

Action

In Zapier“Creates an allowance incidence, also known as an Allowance Adjustment in the Employee Time off Page. They are hours or days added or subtracted from the time off allowance”

Create an allowance adjustment in Factorial from data another step brings in.

When to use it

For a team lead covering absences on a busy rota, it saves someone from typing the allowance adjustment into Factorial by hand.

Watch out

Five fields are required here, including employee_id and timeoff_allowance_id; a run that leaves one empty fails, and a failed action costs no task.

181

Delete With Alt Allowances an Allowance

Action

In Zapier“Deletes an allowance and migrate the existing incidences in the alternative allowance”

Delete a time off allowance and move its existing adjustments to another allowance.

When to use it

At a company where approved leave must reach the shared calendar, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the time off allowance; a search such as Reads All Allowances placed just before can find it.

182

Deletes an Allowance

Action

In Zapier“Deletes an allowance”

Remove a time off allowance from Factorial without opening the app.

When to use it

For an HR team auditing holiday balances before year-end, it clears out the time off allowance instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the time off allowance; a search such as Reads All Allowances placed just before can find it.

183

Updates an Allowance

Action

In Zapier“Updates an existing Time Off Allowance”

Update a time off allowance that already exists in Factorial.

When to use it

For a team lead covering absences on a busy rota, it brings the time off allowance up to date when the information changes in another tool.

Watch out

The step needs the ID of the time off allowance; a search such as Reads All Allowances placed just before can find it.

184

Creates an Allowance

Action

In Zapier“Creates a new Time off allowance”

Create a time off allowance in Factorial from data another step brings in.

When to use it

At a company where approved leave must reach the shared calendar, it saves someone from typing the time off allowance into Factorial by hand.

Watch out

Many fields are required here, including accrued_units_availability and allowance_type; a run that leaves one empty fails, and a failed action costs no task.

185

Deletes a Blocked Period

Action

In Zapier“Deletes a blocked period”

Delete a blocked period from Factorial.

When to use it

For an HR team auditing holiday balances before year-end, it removes the blocked period once another tool says it is no longer needed.

Watch out

The step needs the ID of the blocked period; a search such as Reads All Blocked Periods placed just before can find it.

186

Updates a Blocked Period

Action

In Zapier“Updates a blocked period”

Update a blocked period that already exists in Factorial.

When to use it

For a team lead covering absences on a busy rota, it keeps the blocked period in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the blocked period; a search such as Reads All Blocked Periods placed just before can find it.

187

Creates a Blocked Period

Action

In Zapier“Creates a blocked period is add a range of dates during which employees cannot submit time off requests. This allows to better plan your team's work throughout the year and ensure that time off requests are in line with the company's needs”

Create a blocked period in Factorial from data another step brings in.

When to use it

At a company where approved leave must reach the shared calendar, it creates the blocked period from what the trigger just brought in, with no double entry.

Watch out

Three fields are required here, including company_id and name; a run that leaves one empty fails, and a failed action costs no task.

188

Approve All Leaves

Action

In Zapier“Allows authorized users to approve employee time-off requests by directly approving the leave”

Approve a time off request directly on the leave itself.

When to use it

For an HR team auditing holiday balances before year-end, it takes this chore off someone's list for good.

Watch out

It approves the leave itself rather than walking through an approval flow; Approves a Leave is the step that follows the flow.

189

Approves a Leave

Action

In Zapier“Allows authorized users to approve employee time-off requests by approving the corresponding approval flow if it exists”

Through the leave's approval flow, when it has one, this step approves a time off request.

When to use it

For a team lead covering absences on a busy rota, it does this for you the moment the chosen trigger fires.

Watch out

Only users with the right to approve can use it, and with no approval flow there is nothing to walk through.

190

Deletes a Leave

Action

In Zapier“Deletes a Leave”

Delete a leave from Factorial.

When to use it

At a company where approved leave must reach the shared calendar, it clears out the leave instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the leave; a search such as Reads All Leaves placed just before can find it.

191

Updates a Leave

Action

In Zapier“Updates a Leave”

Update a leave that already exists in Factorial.

When to use it

For an HR team auditing holiday balances before year-end, it brings the leave up to date when the information changes in another tool.

Watch out

The step needs the ID of the leave; a search such as Reads All Leaves placed just before can find it.

192

Creates a Leave

Action

In Zapier“Creates a Leave”

Create a leave in Factorial from data another step brings in.

When to use it

For a team lead covering absences on a busy rota, it saves someone from typing the leave into Factorial by hand.

Watch out

Two fields are required here, including employee_id and start_on; a run that leaves one empty fails, and a failed action costs no task.

193

Rejects a Leave

Action

In Zapier“Allows authorized users to reject employee time-off requests”

Reject a time off request from an employee.

When to use it

At a company where approved leave must reach the shared calendar, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the leave; a search such as Reads All Leaves placed just before can find it.

194

Updates a Leave Type

Action

In Zapier“Updates a Leave type”

Leave type details, rewritten in Factorial by the Zap.

When to use it

For an HR team auditing holiday balances before year-end, it keeps the leave type in Factorial aligned with what another tool says.

Watch out

Every field is optional here, so run one test with real values before you publish.

195

Creates a Leave Type

Action

In Zapier“Creates a Leave type”

Add a leave type to Factorial without opening the app.

When to use it

For a team lead covering absences on a busy rota, it creates the leave type from what the trigger just brought in, with no double entry.

Watch out

Eight fields are required here, including accrues and approval_required; a run that leaves one empty fails, and a failed action costs no task.

196

Deletes a Policy

Action

In Zapier“Deletes a Policy”

Time off policy removal, handled by the Zap.

When to use it

At a company where approved leave must reach the shared calendar, it clears out the time off policy instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the time off policy; a search such as Reads All Policies placed just before can find it.

197

Updates a Policy

Action

In Zapier“Updates a Policy”

Edit a time off policy you already have in Factorial.

When to use it

For an HR team auditing holiday balances before year-end, it brings the time off policy up to date when the information changes in another tool.

Watch out

The step needs the ID of the time off policy; a search such as Reads All Policies placed just before can find it.

198

Creates a Policy

Action

In Zapier“Creates a Policy”

Add a time off policy to Factorial without opening the app.

When to use it

For a team lead covering absences on a busy rota, it saves someone from typing the time off policy into Factorial by hand.

Watch out

name is required here; a run that leaves it empty fails, and a failed action costs no task.

199

Bulk Creates a Planning Version

Action

In Zapier“Bulk creates a Planning version”

Create a planning version for several employees at once.

When to use it

At a care provider scheduling staff across sites, it does this for you the moment the chosen trigger fires.

Watch out

Three fields are required here, including effective_at and planning_tool; a run that leaves one empty fails, and a failed action costs no task.

200

Deletes a Planning Version

Action

In Zapier“Deletes a Planning version”

Delete a planning version from Factorial.

When to use it

For a retail manager building the next rota, it clears out the planning version instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the planning version; a search such as Reads All Planning Versions placed just before can find it.

201

Updates a Planning Version

Action

In Zapier“Updates a Planning version”

Update a planning version that already exists in Factorial.

When to use it

For a restaurant group planning weekend rotas, it brings the planning version up to date when the information changes in another tool.

Watch out

The step needs the ID of the planning version; a search such as Reads All Planning Versions placed just before can find it.

202

Creates a Planning Version

Action

In Zapier“Creates a Planning version”

Add a planning version to Factorial without opening the app.

When to use it

At a care provider scheduling staff across sites, it saves someone from typing the planning version into Factorial by hand.

Watch out

Three fields are required here, including effective_at and planning_tool; a run that leaves one empty fails, and a failed action costs no task.

203

Updates a Break Configuration

Action

In Zapier“Updates a Break configuration”

Update a break type that already exists in Factorial.

When to use it

For an operations lead handling shift patterns, it brings the break type up to date when the information changes in another tool.

Watch out

The step needs the ID of the break type; a search such as Reads All Break Configurations placed just before can find it.

204

Creates a Break Configuration

Action

In Zapier“Creates a Break configuration”

Create a break type in Factorial from data another step brings in.

When to use it

For an HR team managing summer hours, it saves someone from typing the break type into Factorial by hand.

Watch out

Two fields are required here, including name and paid; a run that leaves one empty fails, and a failed action costs no task.

205

Deletes a Category

Action

In Zapier“Deletes a Category”

Delete a training category from Factorial.

When to use it

At a company that tracks mandatory safety training, it removes the training category once another tool says it is no longer needed.

Watch out

The step needs the ID of the training category; a search such as Reads All Categories placed just before can find it.

206

Creates a Category

Action

In Zapier“Creates a Category”

Create a training category in Factorial from data another step brings in.

When to use it

For a team lead enrolling new hires in onboarding sessions, it saves someone from typing the training category into Factorial by hand.

Watch out

Two fields are required here, including name and company_id; a run that leaves one empty fails, and a failed action costs no task.

207

Bulk Creates a Session Access Membership

Action

In Zapier“Bulk creates a Session access membership”

Give several people access to a training session, with or without a notification.

When to use it

For an L&D manager running compliance courses, it does this for you the moment the chosen trigger fires.

Watch out

Two fields are required here, including session_id and notify; a run that leaves one empty fails, and a failed action costs no task.

208

Bulk Destroys a Session Access Membership

Action

In Zapier“Bulk destroys a Session access membership”

Revoke session access for several people at once.

When to use it

At a company that tracks mandatory safety training, it takes this chore off someone's list for good.

Watch out

Two fields are required here, including ids and notify; a run that leaves one empty fails, and a failed action costs no task.

209

Bulk Updates a Session Attendance

Action

In Zapier“Bulk updates a Session attendance”

Mark attendance for several session participants in one go.

When to use it

For a team lead enrolling new hires in onboarding sessions, it does this for you the moment the chosen trigger fires.

Watch out

Two fields are required here, including ids and status; a run that leaves one empty fails, and a failed action costs no task.

210

Deletes a Session

Action

In Zapier“Deletes a Session”

Remove a training session from Factorial without opening the app.

When to use it

For an L&D manager running compliance courses, it clears out the training session instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the training session; a search such as Reads All Sessions placed just before can find it.

211

Updates a Session

Action

In Zapier“Updates a Session”

Update a training session that already exists in Factorial.

When to use it

At a company that tracks mandatory safety training, it brings the training session up to date when the information changes in another tool.

Watch out

The step needs the ID of the training session; a search such as Reads All Sessions placed just before can find it.

212

Creates a Session

Action

In Zapier“Creates a Session”

Add a training session to Factorial without opening the app.

When to use it

For a team lead enrolling new hires in onboarding sessions, it saves someone from typing the training session into Factorial by hand.

Watch out

Two fields are required here, including name and training_id; a run that leaves one empty fails, and a failed action costs no task.

213

Bulk Creates a Training Membership

Action

In Zapier“Bulk creates a Training membership”

Enrol several people in a training.

When to use it

For an L&D manager running compliance courses, it does this for you the moment the chosen trigger fires.

Watch out

training_id is required here; a run that leaves it empty fails, and a failed action costs no task.

214

Bulk Destroys a Training Membership

Action

In Zapier“Bulk destroys a Training membership”

Remove several enrolments from a training.

When to use it

At a company that tracks mandatory safety training, it takes this chore off someone's list for good.

Watch out

ids is required here; a run that leaves it empty fails, and a failed action costs no task.

215

Updates a Training Membership

Action

In Zapier“Update a training membership”

Training enrolment details, rewritten in Factorial by the Zap.

When to use it

For a team lead enrolling new hires in onboarding sessions, it brings the training enrolment up to date when the information changes in another tool.

Watch out

The step needs the ID of the training enrolment; a search such as Reads All Training Memberships placed just before can find it.

216

Bulk Deletes a Training

Action

In Zapier“Bulk deletes a Training”

Delete several trainings in one go.

When to use it

For an L&D manager running compliance courses, it takes this chore off someone's list for good.

Watch out

ids is required here; a run that leaves it empty fails, and a failed action costs no task.

217

Bulk Update Catalogs a Training

Action

In Zapier“Bulk update catalogs a Training”

Update the catalog of several trainings at once.

When to use it

At a company that tracks mandatory safety training, it does this for you the moment the chosen trigger fires.

Watch out

Two fields are required here, including ids and catalog; a run that leaves one empty fails, and a failed action costs no task.

218

Deletes a Training

Action

In Zapier“Deletes a Training”

Training removal, handled by the Zap.

When to use it

For a team lead enrolling new hires in onboarding sessions, it clears out the training instead of leaving it to a manual clean-up.

Watch out

The step needs the ID of the training; a search such as Reads All Trainings placed just before can find it.

219

Updates a Training

Action

In Zapier“Updates a Training”

Training details, rewritten in Factorial by the Zap.

When to use it

For an L&D manager running compliance courses, it brings the training up to date when the information changes in another tool.

Watch out

The step needs the ID of the training; a search such as Reads All Trainings placed just before can find it.

220

Creates a Training

Action

In Zapier“Creates a Training”

Training creation, done by the Zap instead of by hand.

When to use it

At a company that tracks mandatory safety training, it saves someone from typing the training into Factorial by hand.

Watch out

Four fields are required here, including name and description; a run that leaves one empty fails, and a failed action costs no task.

221

Update Statuses a Training

Action

In Zapier“Update statuses a Training”

Change a training's status and choose whether to notify people.

When to use it

For a team lead enrolling new hires in onboarding sessions, it does this for you the moment the chosen trigger fires.

Watch out

The step needs the ID of the training; a search such as Reads All Trainings placed just before can find it.

222

Bulk Cuds a Day Configuration

Action

In Zapier“Bulk cuds a Day configuration”

Handle the day configurations of an overlap period in one batch: create, update and delete together.

When to use it

For an HR team managing summer hours, it takes this chore off someone's list for good.

Watch out

overlap_period_id is required here; a run that leaves it empty fails, and a failed action costs no task.

223

Deletes an Overlap Period

Action

In Zapier“Deletes an Overlap period”

Delete an overlap period from Factorial.

When to use it

At a company with different schedules per site, it removes the overlap period once another tool says it is no longer needed.

Watch out

The step needs the ID of the overlap period; a search such as Reads All Overlap Periods placed just before can find it.

224

Updates an Overlap Period

Action

In Zapier“Updates an Overlap period”

Update an overlap period that already exists in Factorial.

When to use it

For an operations lead handling shift patterns, it keeps the overlap period in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the overlap period; a search such as Reads All Overlap Periods placed just before can find it.

225

Creates an Overlap Period

Action

In Zapier“Creates an Overlap period”

Create an overlap period in Factorial from data another step brings in.

When to use it

For an HR team managing summer hours, it creates the overlap period from what the trigger just brought in, with no double entry.

Watch out

Three fields are required here, including author and schedule_id; a run that leaves one empty fails, and a failed action costs no task.

226

Updates a Schedule

Action

In Zapier“Updates a Schedule”

Work schedule details, rewritten in Factorial by the Zap.

When to use it

At a company with different schedules per site, it keeps the work schedule in Factorial aligned with what another tool says.

Watch out

The step needs the ID of the work schedule; a search such as Reads All Schedules placed just before can find it.

227

Creates a Schedule

Action

In Zapier“Creates a Schedule”

Add a work schedule to Factorial without opening the app.

When to use it

For an operations lead handling shift patterns, it creates the work schedule from what the trigger just brought in, with no double entry.

Watch out

Two fields are required here, including name and schedule_type; a run that leaves one empty fails, and a failed action costs no task.

228

Toggle Archives a Schedule

Action

In Zapier“Toggle archives a Schedule”

Send a work schedule to the archive, or bring an archived one back.

When to use it

For an HR team managing summer hours, it takes this chore off someone's list for good.

Review evaluation lookup by ID, for when an earlier step already knows which one. The record it finds feeds the steps after it.

When to use it

For a people team running performance reviews, it reads the details of the review evaluation before a later step acts on it.

Watch out

It needs the ID of the review evaluation: map it from an earlier step, or start from Reads All Review Evaluations when you only know other details.

127

Reads All Review Owners

In Zapier“Retrieves the review owners of review processes (each process has at least one owner). The owners can edit the review process and access its results.”

All review owners on your Factorial account come back with this search. What it finds is handed to the next steps of the Zap.

When to use it

At a scale-up rolling out its first structured review cycle, it pulls the review owners so a later step can pick or compare them.

Watch out

Every review process has at least one owner, and owners can edit the process and see its results.

128

Reads All Review Processes

In Zapier“Reads all Review processes”

All review processes on your Factorial account come back with this search. Later steps pick from that result instead of asking you.

When to use it

For managers who want reviews to lead to action plans, it gives the next step the whole list of review processes to work from.

Watch out

When nothing matches, the Zap stops there by default; switch on Successful if no search results are found? to let it carry on.

129

Reads a Single Review Process

In Zapier“Reads a single Review process”

Review process lookup by ID, for when an earlier step already knows which one. The record it finds feeds the steps after it.

When to use it

For a people team running performance reviews, it fetches the review process whose ID an earlier step already holds.

Watch out

It needs the ID of the review process: map it from an earlier step, or start from Reads All Review Processes when you only know other details.

130

Reads All Review Process Estimated Targets

In Zapier“Reads all Review process estimated targets”

All estimated review participants on your Factorial account come back with this search. What it finds is handed to the next steps of the Zap.

When to use it

At a scale-up rolling out its first structured review cycle, it gives the next step the whole list of estimated review participants to work from.

Watch out

When nothing matches, the Zap stops there by default; switch on Successful if no search results are found? to let it carry on.

131

Reads All Review Process Targets

In Zapier“Retrieves the participants of active review processes.”

All review participants on your Factorial account come back with this search. Later steps pick from that result instead of asking you.

When to use it

For managers who want reviews to lead to action plans, it pulls the review participants so a later step can pick or compare them.

Watch out

When several items come back, the default keeps only the first; change If multiple search results are found? to pass them all on.

132

Reads a Single Review Process Target

In Zapier“Retrieves the participants of active review processes.”

Review participant lookup by ID, for when an earlier step already knows which one. The record it finds feeds the steps after it.

When to use it

For a people team running performance reviews, it reads the details of the review participant before a later step acts on it.

Watch out

It needs the ID of the review participant: map it from an earlier step, or start from Reads All Review Process Targets when you only know other details.

133

Reads All Review Questionnaire by Strategies

In Zapier“Retrieves the questionnaires by reviewer strategy for review processes.”

All review questionnaires on your Factorial account come back with this search. What it finds is handed to the next steps of the Zap.

When to use it

At a scale-up rolling out its first structured review cycle, it pulls the review questionnaires so a later step can pick or compare them.

Watch out

When several items come back, the default keeps only the first; change If multiple search results are found? to pass them all on.

134

Reads a Single Review Questionnaire by Strategy

In Zapier“Retrieves the questionnaires by reviewer strategy for review processes.”

Review questionnaire lookup by ID, for when an earlier step already knows which one. Later steps can then read its details without a manual lookup.

When to use it

For managers who want reviews to lead to action plans, it reads the details of the review questionnaire before a later step acts on it.

Watch out

It needs the ID of the review questionnaire: map it from an earlier step, or start from Reads All Review Questionnaire by Strategies when you only know other details.

135

Reads All Review Visibility Settings

In Zapier“Retrieves the visibility settings of review processes.”

All review visibility settings on your Factorial account come back with this search. The steps that follow can then use what comes back.

When to use it

For a people team running performance reviews, it pulls the review visibility settings so a later step can pick or compare them.

Watch out

When several items come back, the default keeps only the first; change If multiple search results are found? to pass them all on.

136

Reads All Target Managers

In Zapier“Retrieves the participants' managers of a review process.”

All participants' managers on your Factorial account come back with this search. What it finds is handed to the next steps of the Zap.

When to use it

At a scale-up rolling out its first structured review cycle, it gives the next step the whole list of participants' managers to work from.

Watch out

When nothing matches, the Zap stops there by default; switch on Successful if no search results are found? to let it carry on.

137

Reads a Single Target Manager

In Zapier“Retrieves the participants' managers of a review process.”

One specific participant's manager, found by its ID, is what this search returns. Later steps can then read its details without a manual lookup.

When to use it

For managers who want reviews to lead to action plans, it fetches the participant's manager whose ID an earlier step already holds.

Watch out

It needs the ID of the participant's manager: map it from an earlier step, or start from Reads All Target Managers when you only know other details.

138

Reads All Comments

In Zapier“Reads all Comments”

All community comments on your Factorial account come back with this search. The steps that follow can then use what comes back.

When to use it

For an internal comms lead running company announcements, it gives the next step the whole list of community comments to work from.

Watch out

When nothing matches, the Zap stops there by default; switch on Successful if no search results are found? to let it carry on.

139

Reads a Single Comment

In Zapier“Reads a single Comment”

One specific community comment, found by its ID, is what this search returns. What comes back is ready to map into the next step.

When to use it

At a distributed company where the intranet is the water cooler, it fetches the community comment whose ID an earlier step already holds.

Watch out

It needs the ID of the community comment: map it from an earlier step, or start from Reads All Comments when you only know other details.

140

Reads All Groups

In Zapier“> ###### What does it do? > These endpoints will allow you to retrieve groups > ###### What can you do with groups? > Increase visibility and communication within the company by creating events and announcements. You can create groups for different departments, teams, or projects. > ###### Who can use it? > For having this funcionality available, you need to have Communities V2 feature enabled.”

All community groups on your Factorial account come back with this search. Later steps pick from that result instead of asking you.

When to use it

For an HR team that posts benefits news to employees, it gives the next step the whole list of community groups to work from.

Watch out

Community groups and posts require the Communities V2 feature on the Factorial side.

141

Reads a Single Group

Community group lookup by ID, for when an earlier step already knows which one. The record it finds feeds the steps after it.

When to use it

For an internal comms lead running company announcements, it fetches the community group whose ID an earlier step already holds.

Watch out

Community groups and posts require the Communities V2 feature on the Factorial side.

142

Reads All Posts

In Zapier“What does it do? These endpoints allow you to retrieve posts of a community ###### What can you do with groups? Increase visibility and communication within the company by creating interaction and community within your company. ###### Who can use it? For having this funcionality available, you need to have Communities V2 feature available”

All community posts on your Factorial account come back with this search. What it finds is handed to the next steps of the Zap.

When to use it

At a distributed company where the intranet is the water cooler, it gives the next step the whole list of community posts to work from.

Watch out

Community groups and posts require the Communities V2 feature on the Factorial side.

143

One specific flexible time record comment, found by its ID, is what this search returns. What comes back is ready to map into the next step.

When to use it

At a consultancy tracking time against client projects, it reads the details of the flexible time record comment before a later step acts on it.

Watch out

The step only works if the company has the flexible time tracking feature for projects switched on.

One specific project, found by its ID, is what this search returns. Later steps can then read its details without a manual lookup.

When to use it

For a studio where producers watch project budgets, it reads the details of the project before a later step acts on it.

Watch out

The step needs Factorial's project management feature switched on, and a user with the matching rights on projects.

153

Reads All Project Tasks

In Zapier“Lists project tasks based on user permissions. Filter by: ids[], project_ids[], subproject_ids[], completed, overdue, search, due_status (no_due/due_today/over_due/due_in_future), client_ids[]. Access depends on project role and company-wide permissions. Requires projects_management feature.”

All project tasks on your Factorial account come back with this search. The steps that follow can then use what comes back.

When to use it

For an agency that bills clients by the hour, it pulls the project tasks so a later step can pick or compare them.

Watch out

The step needs Factorial's project management feature switched on, and a user with the matching rights on projects.

154

Reads a Single Project Task

In Zapier“Retrieves a single project task. Access based on permissions: company-wide view/create access or project role (editor/owner). Requires projects_management feature and project read permissions.”

Project task lookup by ID, for when an earlier step already knows which one. What comes back is ready to map into the next step.

When to use it

At a consultancy tracking time against client projects, it reads the details of the project task before a later step acts on it.

Watch out

The step needs Factorial's project management feature switched on, and a user with the matching rights on projects.

155

Reads All Project Workers

In Zapier“What does it do? This endpoint reads and retrieves a list of project workers. You can utilize URL parameters to filter the results. ###### Is it related to other entities? A project_worker is always related to a project and a employee. Only a `project worker` is able to add time to a project using the `time_record` entity. ###### Who can use it? Only companies who have enabled the `projects_management` feature and users with the permission to read project workers.”

All project workers on your Factorial account come back with this search. Later steps pick from that result instead of asking you.

When to use it

For a studio where producers watch project budgets, it pulls the project workers so a later step can pick or compare them.

Watch out

The step needs Factorial's project management feature switched on, and a user with the matching rights on projects.

156

Reads a Single Project Worker

Project worker lookup by ID, for when an earlier step already knows which one. The record it finds feeds the steps after it.

When to use it

For an agency that bills clients by the hour, it reads the details of the project worker before a later step acts on it.

Watch out

The step needs Factorial's project management feature switched on, and a user with the matching rights on projects.

157

Reads All Subprojects

In Zapier“What does it do? This reads all subprojects created ###### What params does it accept? - `ids`: retrieve only the subprojects that matches the ids passed in the request.\n - `include_inputed_minutes`: if `true` we will perform the minutes calculations and will be return the total `inputed_minutes`. If the param is not passed in the request, its default value is `FALSE` so it will return `inputed_minutes: 0` and no minutes calculations will be performed. - `updated_after`: this parameter is needed to filter subprojects created or updated after a date. ###### Is it related to other entities? A subproject is always related to a project, so you can use the query params to list only the subprojects that are related to a specific project. ###### Who can use it? Only companies who have enabled the `projects_with_subprojects` feature and users with the permission of read subprojects.”

All subprojects on your Factorial account come back with this search. What it finds is handed to the next steps of the Zap.

When to use it

At a consultancy tracking time against client projects, it pulls the subprojects so a later step can pick or compare them.

Watch out

Subprojects need their own feature switched on in Factorial, plus a role in the parent project.

158

In Zapier“Reads a single Schedule”

Work schedule lookup by ID, for when an earlier step already knows which one. Later steps can then read its details without a manual lookup.

When to use it

For an operations lead handling shift patterns, it reads the details of the work schedule before a later step acts on it.

Watch out

It needs the ID of the work schedule: map it from an earlier step, or start from Reads All Schedules when you only know other details.

The three settings every search exposes

Successful if no search results are found?
Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
Create X if it doesn't exist yet?
This box turns a search into a find-or-create. No Factorial search offers it, so every search here only reads.
If multiple search results are found?
Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.

When it breaks

When a Factorial Zap breaks

Zapier lists no limit or error specific to Factorial, so the traps below are the general ones.

They matter on Factorial, where several triggers react to bulk changes, such as Bulk Deletes Tasks. For a Zap that stopped for another reason, start from our Zapier troubleshooting page.

Nothing from before the Zap
A Zap only reacts to what happens after you publish it. Applications, leaves or employees already in Factorial are never picked up; moving that backlog is a separate job.
A Zap that sets itself off
If the action writes into what the trigger watches, say Creates a Task on a Zap started by Creates a Task, it loops and eats through your task count fast.
Bulk changes held back
A trigger that suddenly sends a huge batch, after a bulk import or a migration, can be held back by Zapier's flood protection.
A search that finds nothing
By default, a search with no result stops the Zap there and skips the steps that depended on it, unless you switch on the setting that lets it carry on.

Need help

Need help automating Factorial with Zapier?

A person reads every message.

FAQ

Factorial and Zapier: your questions

01Is the Factorial Zapier integration free?

Yes, as long as the Zap stays simple. Factorial is not a premium app, so it runs on Zapier's free plan. That plan gives you 100 tasks a month and Zaps of two steps only: one trigger and one action. As soon as you add a second action, a filter or a search step, the Zap becomes multi-step and needs a paid plan. No price is quoted here on purpose, because Zapier's pricing grid changes often; check it on zapier.com before you pick a plan.

02How many tasks does a Factorial Zap use?

One task per action that completes successfully, and nothing else. The trigger never costs a task, however many events Factorial sends, and an action that fails is not counted against your plan. A Zap with three actions uses three tasks each time it runs all the way through. The trap is a Zap that writes into what its own trigger watches: it sets itself off again and again, and the task count drops fast.

03Do Factorial triggers fire in real time?

Yes. All 111 Factorial triggers are instant: Factorial tells Zapier the moment the event happens, so the Zap starts right away. The polling interval of the plans, 15 minutes on the free plan and down to 1 minute on Team or Enterprise, does not apply to them. That makes Factorial a good fit for a free plan, as long as the Zap stays at two steps. In the editor, a Zap built on an instant trigger shows a lightning bolt next to it.

04What does it take to connect Factorial to Zapier?

A Factorial account, and read or write access to anything you do not own but want the Zap to touch. In Zapier, open Apps, click + Add connection, search for Factorial, click Add connection, sign in to Factorial in the tab that opens and grant access. The connection is then reused by every Factorial step of every Zap. Before building, also note your company identifier somewhere handy: every trigger asks for it.

05Which field catches people out on Factorial triggers?

The company identifier. Every one of the 111 triggers asks for it, and it is required, so the setup stays incomplete until it is filled in. Many actions also require an ID, for instance the ID of the leave, employee or task to change. The clean way to get one is a search step placed right before the action, such as Reads All Employees, which hands the ID to the next step. Remember that a search step makes the Zap multi-step, so paid.

06What if the Factorial operation you need is not there?

Check the full list first: with 545 operations, many HR objects have a create, update, delete and read step. If yours is missing, two routes remain. Combine a search and an action to rebuild the gesture in two steps, which means a paid plan. Or look at another automation tool covering Factorial. Our team can also tell you quickly whether a workaround exists before you start building. A search such as Reads All Employees is often the first half of that pair.

07Zapier, Make or n8n for Factorial?

It depends on three criteria rather than on a ranking. First, coverage: here Zapier offers 545 Factorial operations, so check that the one you need exists on the tool you compare. Second, how usage is counted: Zapier bills each successful action as a task, so estimate your own volume before you compare. Third, what you already run: if your other HR flows already live on one of the three, staying there saves rebuilding them.

Plan	Checks for new data every
Free	15 min
Professional	2 min
Team	1 min
Enterprise	1 min

Open the Apps page

Pick Factorial

Sign in and grant access

Build: pick the trigger

Set and test the trigger

Add the filter

Add the action

Test, then publish