Resources · Make integration

Factorial Make integrationAutomate Factorial with Make.

Can Make keep Factorial in sync with the rest of your HR stack? The Factorial Make integration gives you 29 modules, including 8 triggers, for employees, leaves and attendance. This page shows HR and ops teams how to link the account and build a first scenario.

Try the Factorial integration on Make See the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Factorial Make integration do for your HR team?

The Factorial Make integration links your Factorial account to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or searches something. It lets hires, leaves and clock-ins in Factorial start work in your other apps, with no code.

Onboarding that starts itself. Watch Employee Created fires the moment HR adds someone in Factorial. Follow it with Get an Employee to pull the full record, then pass it to your IT or payroll tools so accounts are ready before the first day.

Leave requests that land where managers look. Watch Leaves picks up each new leave on the scenario's schedule. Pair it with Search Leave Types to label the absence, and a store manager sees it in the shared planning sheet without opening Factorial.

Clean exits. Watch Employee Terminated reacts when the termination form is submitted, so a scenario can close access elsewhere. If someone is rehired, Watch Employee Unterminated or the Unterminate an Employee module handles the return.

The listed modules cover employees, leaves, leave types and attendance; for documents and folders they only search. Anything else goes through Make an API Call, which reuses the same connection. Make's documentation for this app is AI-generated from Factorial's docs, so check important details with Factorial. If you also compare tools, the n8n vs Make page lays out the criteria, and Make training helps if Make is new to you.

Connect

How do you connect Factorial to Make?

01
Add a Factorial module
In your scenario, add any Factorial module and click Create a connection. A connection is your Factorial account linked to Make once, then reused by every Factorial module. For an instant module, click Create a webhook first, then Create a connection.
02
Generate your API key
In Factorial, open Settings, then API access or API keys, and click Generate API key. Copy the key shown on screen. You need an active Factorial account, and an OAuth2 application also works instead of a key.
03
Name and save the connection
Back in Make, type a label in Connection name if you like (it is optional), then paste the key or follow the on-screen instructions. Once saved, the connection appears in every Factorial module you add later.

First scenario

Your first scenario: add new hires to Factorial automatically

GoalWhen a new hire is recorded in another app, Make creates the employee in Factorial.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. This first module is the app where the hire is recorded, such as your form tool or CRM.
02
Set the starting module
Search that app by name, pick the module that watches for new entries and connect your account. Each entry it returns is a bundle: one item passed to the next module, here one new hire.
03
Add Create an Employee
Click the + on the right of the first module, search Factorial and choose Create an Employee. Pick your Factorial connection, then map the hire's details from the first module into the fields Make shows.
04
Test with Run once
Click Run once and add a test hire in the source app. Make runs the scenario one time and shows the bundles each module received, so you can check the employee in Factorial before going live.
05
Schedule and switch it on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation, the unit Make counts on your plan.

Triggers

Which Factorial events can start a scenario?

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

Factorial1Watch Attendance Clock In

Watch Attendance Clock In

Instant trigger

In Make“Triggers when a user clocks in and starts the timer.”

Starts your scenario when someone clocks in and their timer begins in Factorial, so the start of a shift becomes an event other apps can act on.

How it fires

instant, meaning Factorial calls Make through a webhook as soon as the clock-in happens. That is the lightning badge on the module.

When to use it

a shop or warehouse where the floor lead wants a message the moment each person on the rota arrives.

Watch out

click Create a webhook before Create a connection, or the trigger will never receive the event.

Factorial2Watch Attendance Clock Out

Watch Attendance Clock Out

Instant trigger

In Make“Triggers when the user clocks out and stops the timer.”

Sends each clock-out to Make as it happens, when the person stops their timer, so you can close the day's record in another tool without exporting anything.

How it fires

instant; Factorial notifies Make through a webhook right after the clock-out.

When to use it

logging end-of-shift times into a timesheet sheet that a client or project manager reviews.

Watch out

each module watches only one of the two events, so tracking both clock-in and clock-out takes two scenarios, one per trigger.

Factorial3Watch Employee Created

Watch Employee Created

Instant trigger

In Make“Triggers when an employee has been created.”

Gives you a new bundle the moment an employee record is created in Factorial, which is the cleanest starting point for onboarding work across your tools.

How it fires

instant, through a webhook that Factorial calls as soon as the record exists.

When to use it

HR adds a hire and you want IT to open accounts and the manager to get a heads-up without anyone forwarding an email.

Watch out

Watch Employees does a similar job on a schedule; keep only one of them in a scenario so each hire is handled once.

Factorial4Watch Employee Invited

Watch Employee Invited

Instant trigger

In Make“Triggers when an employee has been invited.”

Reacts when an employee is invited to Factorial, and passes that invitation on to Make as a bundle you can use in other apps.

How it fires

instant; the invitation reaches Make through a webhook straight away.

When to use it

you want to follow up on invitations, for example by posting a welcome note in the team chat once the person is asked to join.

Watch out

invited and created are separate events, so pick the one that matches the step of your process you want to automate.

Factorial5Watch Employees

Watch Employees

Scheduled trigger

In Make“Triggers when a new employee has been created.”

Collects employees newly created in Factorial and hands each one to your scenario as a bundle, without needing a webhook.

How it fires

scheduled, which means Make checks Factorial on the scenario's schedule (the clock badge), every 15 minutes by default.

When to use it

a sync where a short delay does not matter, such as copying new staff into a directory spreadsheet.

Watch out

on the Free plan the shortest gap between scheduled runs is 15 minutes; if you need the event right away, use Watch Employee Created instead.

Factorial6Watch Employee Terminated

Watch Employee Terminated

Instant trigger

In Make“Triggers when terminating an employee, after submitting the form.”

Fires when someone terminates an employee in Factorial and submits the form, which lets the rest of your offboarding follow without a checklist chase.

How it fires

instant; Factorial calls Make through a webhook once the termination form is submitted.

When to use it

revoking tool access, alerting IT to collect a laptop, or archiving the person in your CRM.

Watch out

nothing reaches Make until the form is actually submitted, so a termination left half-filled does not start the scenario.

Factorial7Watch Employee Unterminated

Watch Employee Unterminated

Instant trigger

In Make“Triggers when a terminated employee gets re activated.”

Catches the reverse move: a terminated employee who is reactivated in Factorial, so a return or a mistaken exit can be undone elsewhere too.

How it fires

instant, sent by Factorial through a webhook as soon as the reactivation happens.

When to use it

a seasonal worker comes back and needs their accounts restored, or HR reverses an exit entered by mistake.

Watch out

if another scenario removed access at termination, make sure this one restores the same tools, or the two will drift apart.

Factorial8Watch Leaves

Watch Leaves

Scheduled trigger

In Make“Triggers when a new leave has been created.”

Picks up each new leave created in Factorial and sends it to your scenario, one bundle per leave, so absences can show up where the team plans its work.

How it fires

scheduled; Make checks Factorial on the scenario's schedule rather than being called by a webhook.

When to use it

copying each new leave into a shared calendar or a staffing sheet that managers already read.

Watch out

between two checks, several leaves can pile up; they arrive as separate bundles in the same run, and each one costs operations.

Modules

What can each Factorial module do?

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

Factorial1

Create a Leave

Action

In Make“Creates a leave.”

Records a leave in Factorial from another app, so absences entered elsewhere end up in the HR system without retyping.

When to use it

a manager approves time off in a form or a chat tool and you want Factorial to hold the official record.

Watch out

run Search Leave Types earlier in the scenario so you pick an existing type rather than typing one by hand.

Factorial2

Create a Leave Type

Action

In Make“Creates a leave type.”

Adds a new category of leave to Factorial, which is handy when your policy changes and the whole workforce needs the same new type.

When to use it

rolling out a new kind of absence, such as a volunteering day, across the company in one step.

Watch out

a scenario that runs again will try to create the type again, so check with Search Leave Types before creating.

Factorial3

Create an Employee

Action

In Make“Creates an employee.”

Creates a new employee record in Factorial with details mapped from an earlier module, so a hire only has to be entered once.

When to use it

a signed offer in your CRM or an onboarding form should turn into a Factorial profile without HR copying fields by hand.

Watch out

test with Run once on a dummy hire first, because every run creates a real record.

Factorial4

Delete a Leave

Action

In Make“Deletes a leave.”

Removes a leave from Factorial entirely, which keeps the absence calendar honest when a request is cancelled somewhere else.

When to use it

an employee withdraws a request in the tool where it was first filed, and Factorial should forget it too.

Watch out

a deletion cannot be undone from Make; if you only need to change dates, Update a Leave is the safer choice.

Factorial5

Get an Employee

Action

In Make“Retrieves an employee.”

Fetches one employee's full record from Factorial, giving later modules everything they need about that person in a single bundle.

When to use it

an earlier module points to one person, and the next app needs that person's complete record.

Watch out

it reads a single person; to go through a list of staff, reach for Search Employees instead.

Factorial6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends any request to the Factorial API using the connection you already set up, so you can reach data the other modules do not cover.

When to use it

you need something outside the list here, and Factorial's API offers it even though no module here does.

Watch out

you write the request yourself, so keep Factorial's API documentation open to check what it accepts.

Factorial7

Terminate an Employee

Action

In Make“Terminates an employee.”

Ends an employee's contract in Factorial from a scenario, so an exit decided in another system reaches the HR record straight away.

When to use it

offboarding starts in your ticketing or legal tool and Factorial should reflect it without a separate manual step.

Watch out

it acts on a real contract, so test it with Run once on a dummy profile before going live.

Factorial8

Unterminate an Employee

Action

In Make“Unterminates an employee.”

Reactivates a terminated employee in Factorial, bringing their profile back without creating a duplicate record.

When to use it

a rehire or a seasonal return is approved elsewhere and the old profile should simply come back to life.

Watch out

reuse the existing employee rather than calling Create an Employee, or you end up with two profiles for one person.

Factorial9

Update a Leave

Action

In Make“Updates a leave.”

Changes an existing leave in Factorial, which lets dates or details stay aligned when the request is edited in another tool.

When to use it

someone moves their holiday in the team planner and Factorial should follow the new dates.

Watch out

you need the leave's identifier, so place Search Leaves or Watch Leaves earlier in the scenario to provide it.

Factorial10

Update a Leave Type

Action

In Make“Updates a leave type.”

Edits a leave type that already exists in Factorial, keeping one category tidy instead of stacking near-duplicates.

When to use it

a policy tweak renames or adjusts an absence category and you want the change applied from the scenario that manages your rules.

Watch out

every leave filed under that type is affected, so double-check which type you picked with Search Leave Types.

Factorial11

Update an Employee

Action

In Make“Updates an employee.”

Writes changes to an employee record in Factorial, so a promotion, a move or a new phone number entered elsewhere reaches HR.

When to use it

your directory or IT tool is where people edit their details, and Factorial should stay the same.

Watch out

it writes to the live record, so try it with Run once on a test profile before switching the scenario on.

Factorial12

Get Hiring Versions for an Employee

In Make“Retrieves hiring versions for an employee.”

Returns the hiring versions stored for one employee, giving you the history of their contract terms as separate bundles.

When to use it

a report or payroll check needs to see how a person's contract changed, not just its current state.

Watch out

like any search, it can return zero, one or several bundles, so the modules after it run once per version.

Factorial13

Search Company Holidays

In Make“Retrieves a list of company holidays.”

Lists the company holidays set up in Factorial, so other apps can know which days the company is closed.

When to use it

a scheduling or delivery tool should skip closed days when it plans work or promises dates.

Watch out

each holiday arrives as its own bundle; add an aggregator (the Make tool that gathers bundles into one) if the next app expects a single list.

Factorial14

Search Documents

In Make“Searches for documents.”

Finds documents stored in Factorial and brings them into your scenario, one bundle per document.

When to use it

you want to check that a contract or a signed policy exists for a person before moving on with onboarding.

Watch out

no listed module adds documents; check Factorial's API documentation and, if it allows it, use Make an API Call.

Factorial15

Search Employees

In Make“Retrieves a list of employees. Only admins can see all the employees' information, regular users will get a restricted version of the payload as a response.”

Returns a list of employees from Factorial, each one as a bundle, ready to feed a report, a sync or a bulk update.

When to use it

copying the whole team into a directory, or finding everyone in one location before sending a notice.

Watch out

only admins see every employee's information; connect with a regular user and you get a restricted version.

Factorial16

Search Folders

In Make“Searches for folders.”

Looks up the folders in Factorial's document space, which helps you find where files for a team or a person are kept.

When to use it

before searching documents, to narrow things down to the folder that matters for the current employee.

Watch out

it can return several folders; add a filter after it if only one should move on to the next module.

Factorial17

Search Leaves

In Make“Retrieves a list of leaves.”

Pulls a list of leaves from Factorial so you can review absences in bulk rather than one by one.

When to use it

building a staffing overview for managers, or finding a specific leave before you update or delete it.

Watch out

unlike Watch Leaves, it does not start a scenario; it only answers when an earlier module asks.

Factorial18

Search Leave Types

In Make“Retrieves a list of leave types.”

Lists the leave types defined in Factorial, so a scenario can match a request to the right category.

When to use it

just before Create a Leave, to pick the type that fits what the employee asked for in the form.

Watch out

each type comes back as its own bundle; add a filter so only the matching one reaches the next module.

Factorial19

Search Locations

In Make“Retrieves a list of locations.”

Returns the locations set up in Factorial, such as offices or stores, each as a separate bundle you can route on.

When to use it

sending a notice only to one site, or labelling employees by office in a report.

Watch out

the modules placed after it run once per location, which adds operations as the list grows.

Factorial20

Search Shifts

In Make“Searches for shifts.”

Finds shifts recorded in Factorial, so the planned rota becomes data another app can read.

When to use it

a coverage sheet or chat channel should show who works each shift without anyone copying it.

Watch out

shifts are the plan, not what happened; for actual arrivals and departures, use the attendance triggers.

Factorial21

Search Teams

In Make“Retrieves a list of teams.”

Lists the teams defined in Factorial, useful when a scenario has to work out who belongs where.

When to use it

routing a leave or a new hire to the right team channel, or mirroring your team structure in a project tool.

Watch out

each team is a separate bundle, so the next modules run once per team and use one operation each time.

Need help

Need help automating Factorial with Make?

A person reads every message.

FAQ

Factorial and Make: common questions

01Is the Factorial Make integration free?

Yes, Factorial is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in credits, one per operation. You still need your own active Factorial account.

02What do you need to connect Factorial to Make?

You need an active Factorial account and either an API key or an OAuth2 application. To get a key, open Settings in Factorial, go to API access or API keys, click Generate API key and copy it. In Make, add a Factorial module, click Create a connection, optionally name it, and paste the key. For instant modules, click Create a webhook first, then Create a connection. The connection is saved once and reused by every Factorial module.

03Do Factorial triggers in Make fire in real time?

It depends on the trigger. Six of the eight are instant: clock-in, clock-out, employee created, employee invited, employee terminated and employee unterminated. Factorial calls Make through a webhook as soon as the event happens. The other two, Watch Employees and Watch Leaves, are scheduled: Make checks Factorial on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan. Pick an instant trigger when timing matters.

04What if a Factorial module is missing in Make?

Use Make an API Call. It sends any request to the Factorial API with the connection you already have, so you can cover endpoints that the 29 listed modules leave out, for example on documents, which the listed modules only search. Check first in Factorial's API documentation that the endpoint exists. You write the request yourself, so keep Factorial's API documentation at hand. Make also notes that its Factorial documentation is AI-generated from Factorial's docs, so confirm important details with Factorial directly.

05Should you use Make or n8n for Factorial?

It depends on the tool your team already runs. In Make, Factorial comes with 29 ready-made modules, six instant triggers and a Make an API Call module, plus a visual editor with Run once for testing. If n8n is already your automation tool, check whether it offers a Factorial node before choosing. Compare the modules each side offers for your exact process, such as leaves or attendance, rather than picking on reputation.

Add a Factorial module

Generate your API key

Name and save the connection

Create the scenario

Set the starting module

Add Create an Employee

Test with Run once

Schedule and switch it on

Need help automating Factorial with Make?