Resources · Make integration

TalentHR Make integrationAutomate TalentHR with Make.

What if new hires, time off answers and job posts moved on their own? The TalentHR Make integration gives you 25 modules, including 9 instant triggers. This page shows HR and ops teams how to link the account and build a first scenario.

Try the TalentHR integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TalentHR Make integration do for you?

The TalentHR Make integration links your TalentHR account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, updates or searches something. TalentHR events start the scenario, and other modules write back to your HR records.

Recruiting that feeds other tools. Watch New ATS Application fires the moment a candidate applies, so the details can land in your team chat or a tracking sheet. Watch Job Published in ATS and Watch Unpublished Job From ATS keep a careers page or a job board list in step with what is actually open.

A hire recorded once. When an offer is signed elsewhere, Create (Hire) an Employee adds the person to TalentHR, and Upload an Employee's Document drops the signed file into their private folder. Watch New Employee can then start the rest of the onboarding in other apps.

Time off without chasing. Watch Time Off Request reacts to each new request, Get Summary of Who's Out Today and Tomorrow shows the overlap, and Respond to a Time Off Request sends the answer back.

The module list has no delete action and no trigger on departments or locations. Make an API Call reaches the rest of the TalentHR API with the same connection. If you are still weighing tools, read the Make review and the n8n vs Make comparison, and check Make pricing before you count operations.

Connect

How do you connect TalentHR to Make?

  1. 01

    Generate your TalentHR API key

    You need an active TalentHR account. In TalentHR, open Settings, pick Domain settings, go to the API tab and click Generate new. Copy the key shown on screen and keep it at hand.

  2. 02

    Add a TalentHR module in Make

    In your scenario, add any TalentHR module and click Create a connection. The connection is your TalentHR account linked to Make once, then reused by every TalentHR module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. Make can now read and write your TalentHR data, and the fields of the module fill with lists it pulled from your account.

First scenario

Your first scenario: hire someone and file their contract

GoalWhen a signed offer arrives from another app, Make creates the employee in TalentHR and uploads the contract to their folder.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where signed offers arrive (a form or a signature tool) and its trigger, the module that starts everything.

  2. 02

    Add Create (Hire) an Employee

    Click the + on the right of the first module, search TalentHR and choose Create (Hire) an Employee. Create the connection with your API key, then map the name and details coming from the offer.

  3. 03

    Attach the signed contract

    Add Upload an Employee's Document after it. Map the employee created by the previous module and the file from the first app. A PDF, a DOCX or a JPG all fit the list of accepted formats.

  4. 04

    Test with Run once

    Click Run once and send one real offer through. Open each module to read the bundle it received, a bundle being one item passed along, here one new hire. Check the person and the file in TalentHR.

  5. 05

    Switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default, unless its trigger is instant) and turn the scenario on. Every signed offer now becomes a TalentHR employee with the contract filed.

Triggers

What can start a TalentHR scenario?

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

TalentHR1Watch Deleted Employee

Watch Deleted Employee

Instant trigger

In Make“Triggers when an employee is deleted.”

Removing someone from TalentHR can close the loop everywhere else: this trigger hands Make the deleted employee so other tools stop treating that person as active.

How it fires
instant, TalentHR calls Make through a webhook as soon as the record is deleted, no waiting for a schedule.
When to use it
to revoke access in a shared drive or remove a teammate from a chat workspace when HR deletes their profile.
Watch out
treat this bundle as the last copy of the profile you get in Make, and map what other tools need from it before the scenario ends.
TalentHR2Watch Job Published in ATS

Watch Job Published in ATS

Instant trigger

In Make“Triggers when an ATS job position is published.”

Each opening you publish in the TalentHR applicant tracking system reaches Make at once, so the job can be announced wherever candidates look.

How it fires
instant, TalentHR alerts Make by webhook the moment the position goes live.
When to use it
to post the new role in a team channel, add it to a careers spreadsheet or tell recruiters that sourcing can start.
Watch out
pair it with Watch Unpublished Job From ATS, otherwise a closed role stays listed in the other tools long after TalentHR hid it.
TalentHR3Watch New ATS Application

Watch New ATS Application

Instant trigger

In Make“Triggers when a new job application is submitted.”

Every candidate who applies becomes a bundle in Make, so a hiring manager hears about applicants without logging into TalentHR.

How it fires
instant, the application triggers a webhook call to Make right after it is submitted.
When to use it
to ping the hiring manager in chat, log the candidate in a shared tracking sheet or send an acknowledgment from your email tool.
Watch out
a popular role sends one run per application, and each module that runs counts as an operation on your Make plan, so keep the chain short.
TalentHR4Watch New Employee

Watch New Employee

Instant trigger

In Make“Triggers when an employee is created in the system.”

A new record in TalentHR becomes the starting signal for onboarding: this trigger passes the fresh employee to Make as soon as HR saves the profile.

How it fires
instant, TalentHR notifies Make through a webhook when the employee is created.
When to use it
to open accounts in other tools, add the person to a welcome checklist or alert IT that a laptop is needed.
Watch out
if a scenario of yours also uses Create (Hire) an Employee, this trigger will most likely fire on those hires too; make sure the two scenarios do not feed each other.
TalentHR5Watch Time Off Request

Watch Time Off Request

Instant trigger

In Make“Triggers when an employee requests time off.”

Managers stop discovering leave requests late: each request filed in TalentHR arrives in Make at once, ready to route.

How it fires
instant, TalentHR warns Make by webhook as soon as an employee asks for time off.
When to use it
to message the approving manager, or to chain Get Summary of Who's Out Today and Tomorrow and show who else is away before anyone answers.
Watch out
this trigger sees the request, not the decision; the approval and the refusal have their own triggers.
TalentHR6Watch Time Off Request Approved

Watch Time Off Request Approved

Instant trigger

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

An approved absence can update the tools your team actually looks at: this trigger reports each approval the second it happens in TalentHR.

How it fires
instant, TalentHR pushes the approval to Make via webhook right away.
When to use it
to block the dates in a shared calendar, post an out-of-office note in the team channel or tell payroll about the leave.
Watch out
it only fires on approvals; a request that is later rejected needs Watch Time Off Request Rejected if other tools already hold the dates.
TalentHR7Watch Time Off Request Rejected

Watch Time Off Request Rejected

Instant trigger

In Make“Triggers when a time off request is rejected.”

The employee learns the outcome where they work: each refused leave request reaches Make, so the answer can travel beyond TalentHR.

How it fires
instant, a webhook from TalentHR tells Make as soon as the request is turned down.
When to use it
to send a direct message to the employee, or to remove tentative dates someone had already placed in a planning sheet.
Watch out
a rejection can feel abrupt in an automated message; send it to the manager first if a conversation should come before the notice.
TalentHR8Watch Unpublished Job From ATS

Watch Unpublished Job From ATS

Instant trigger

In Make“Triggers when a ATS job position is unpublished.”

Closed roles disappear from your other channels too: when you pull a job from the TalentHR applicant tracking system, Make gets the position right away.

How it fires
instant, TalentHR calls Make through a webhook as soon as the job is unpublished.
When to use it
to mark the role as filled in a careers sheet, archive its channel post or tell recruiters to stop sourcing.
Watch out
it reacts only to unpublishing, so a role that stays open but changes content will not reach Make through this trigger.
TalentHR9Watch Updated Employee

Watch Updated Employee

Instant trigger

In Make“Triggers when an employee is updated in TalentHR.”

Changes to a profile spread without copy and paste: whenever HR edits an employee in TalentHR, Make receives the updated record.

How it fires
instant, TalentHR notifies Make via webhook each time the employee is saved with changes.
When to use it
to keep a directory, an org chart sheet or a payroll tool aligned after a promotion or a new job title.
Watch out
never end this scenario with Update an Employee on the same person, or each update fires the trigger again and the scenario loops.
Modules

What else can Make do in TalentHR?

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

TalentHR1

Create a Department

Action

In Make“Creates a 'Department' in your system.”

Adds a department to your TalentHR structure straight from a scenario, so a reorganization planned elsewhere shows up in HR without retyping.

When to use it
when a new team is approved in your planning sheet and people will soon be assigned to it.
Watch out
create the department before any Create (Hire) an Employee that needs it in the same run.
TalentHR2

Create a Division

Action

In Make“Creates a 'Division' in the system.”

Opens a new division in TalentHR, the level above departments for many companies, and gives you its reference for the next modules of the scenario.

When to use it
after an acquisition or a new business line, when the structure is decided in another tool first.
Watch out
no module deletes a division, so test with Run once before letting the scenario create them in bulk.
TalentHR3

Create a Job Title

Action

In Make“Creates a 'Job Title' in the system.”

Registers a job title in TalentHR so hires and promotions can point to it, instead of someone typing the same role by hand in several places.

When to use it
when a role approved in a hiring plan does not exist in TalentHR yet and a new employee is about to receive it.
Watch out
check the titles already in TalentHR first to avoid near-duplicates.
TalentHR4

Create a Location

Action

In Make“Creates a 'Location' in the system.”

Adds an office or site to TalentHR, so employee records can reference the right place as soon as it opens.

When to use it
when a new office is confirmed in your facilities tracker and the first people will be attached to it.
Watch out
like the other structure modules, there is no delete counterpart here; a wrong location has to be fixed with Update a Location or in TalentHR.
TalentHR5

Create (Hire) an Employee

Action

In Make“Adds a new employee (Hire) to the system.”

Records a hire in TalentHR from data you already have, such as a signed offer or an onboarding form, and returns the new employee to later modules.

When to use it
when the offer is accepted in another tool and HR should not type the profile a second time.
Watch out
it should also fire Watch New Employee, so check that no other scenario creates the same person again.
TalentHR6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the TalentHR API with the connection you already set up, for the cases the listed modules do not cover.

When to use it
when you need an action missing from this page, such as removing a record, and the TalentHR API offers it.
Watch out
you write the request yourself, so read the TalentHR API documentation and test the call with Run once.
TalentHR7

Respond to a Time Off Request

Action

In Make“Responds to an employee's time off request.”

Sends the answer to a leave request back to TalentHR, so a manager can decide from chat or a form and the record follows.

When to use it
after Watch Time Off Request and a manager's reply collected in another app, to approve or refuse without opening TalentHR.
Watch out
the answer goes to the employee's request for real, so keep a human decision in the loop.
TalentHR8

Update a Department

Action

In Make“Updates a specified 'Department' in the system.”

Changes an existing department in TalentHR so the HR structure matches what the company actually uses today.

When to use it
when a team is renamed in your planning tool and the change should reach employee records without a manual edit.
Watch out
you must point to the right department; pick it from the list Make shows once the connection exists.
TalentHR9

Update a Division

Action

In Make“Updates a specified 'Division' in the system.”

Edits a division already in TalentHR, keeping the top of your org chart accurate when business lines shift.

When to use it
after a merger of two business units decided elsewhere, to align the TalentHR label with the new name.
Watch out
an update overwrites what was there, so map only the values you really want to change and run it once on a test division.
TalentHR10

Update a Job Title

Action

In Make“Updates a specified 'Job Title' in the system.”

Renames or adjusts a job title that already exists in TalentHR, so every employee holding it reflects the new wording.

When to use it
when a salary grid or a career framework changes role names and HR wants one source to push the change.
Watch out
pick the existing title rather than creating a new one, or you end up with two versions of the same role.
TalentHR11

Update a Location

Action

In Make“Updates a specified 'Location' in the system.”

Corrects or changes an office already stored in TalentHR, so records attached to it stay right after a move.

When to use it
when a site changes address or name in your facilities tracker and HR should follow without retyping it.
Watch out
this module edits the location itself; to move one person to another office, use Update an Employee instead.
TalentHR12

Update an Employee

Action

In Make“Updates an existing Employee in the system.”

Changes an existing employee profile in TalentHR with data from another tool, keeping HR records current without manual edits.

When to use it
after Search Employee finds the right person, to apply the changes coming from an approval form.
Watch out
it should fire Watch Updated Employee; a scenario that starts from that trigger and ends here will loop.
TalentHR13

Upload an Employee's Document

Action

In Make“Uploads a document to employee's private folder in the system. Valid formats: docx,doc,odt,odp,ods,xls,xlsx,ppt,pptx,pdf,png,jpg,jpeg,svg,csv,gif,webp,tsv.”

Files a document in the employee's private TalentHR folder, so contracts and certificates stop living in email threads.

When to use it
when a signed contract, an ID scan or a training certificate arrives from a signature tool or a form.
Watch out
only listed formats pass, among them PDF, DOCX, XLSX, CSV, PNG and JPG; on the Make Free plan a file is limited to 5 MB.
TalentHR14

Employee Absence Summary

Search

In Make“Lists employees who are absent on a specific period.”

Returns the employees absent over a period you set, one bundle per person, which gives a clear picture of coverage.

When to use it
before planning an event or a launch, to post the list of people away during those dates.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per absent person, which multiplies operations.
TalentHR15

Get Summary of Who's Out Today and Tomorrow

Search

In Make“Lists employees out of the company today and tomorrow.”

Lists who is away from the company today and tomorrow, without asking you to pick dates.

When to use it
right after Watch Time Off Request, so the approving manager sees who else is off before saying yes.
Watch out
the window is fixed to those two days; for any other period, Employee Absence Summary is the module to pick.
TalentHR16

Search Employee

Search

In Make“Searches for an employee.”

Finds an employee in TalentHR and hands their record to the next modules, the usual step before any update.

When to use it
when a form or another app gives you details that identify a person and you need the matching TalentHR profile.
Watch out
a search may return no match or several; test with Run once and read the bundles before letting an update run after it.
Need help

Need help automating TalentHR with Make?

A person reads every message.

FAQ

Questions about the TalentHR Make integration

01Is the TalentHR Make integration free?
Yes, on the Make side. TalentHR is a standard app, so all 25 modules work on the Free plan. That plan allows 2 active scenarios, a scheduled run at most every 15 minutes, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift those limits and count usage in credits per month. You still need your own active TalentHR subscription, which TalentHR bills separately; check its pricing page for that part.
02What do you need to connect TalentHR to Make?
An active TalentHR account and an API key. In TalentHR, go to Settings, then Domain settings, open the API tab, click Generate new and copy the key. In Make, add a TalentHR module, click Create a connection, give it a name if you like and paste the key. With an instant trigger, Make asks you to click Create a webhook first, then Create a connection. The same connection then serves every TalentHR module in your scenarios.
03Does the TalentHR Make integration react in real time?
Yes. All 9 TalentHR triggers are instant: TalentHR calls Make through a webhook as soon as the event happens, whether that is a new application, a hire, an edited profile or a time off decision. Nothing waits for the 15 minute default schedule. The scenario runs once per event, and every module it runs counts as an operation on your plan, so a busy recruiting period or a wave of leave requests means more operations.
04What if a TalentHR module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the TalentHR API with the connection you already created, so you can cover actions the 25 listed modules skip, such as deleting a record or reaching an object that has no dedicated module. You write the request yourself from the TalentHR API documentation. If the API does not offer the action either, another app or a manual step in TalentHR will be needed.
05Should you use Make or n8n for TalentHR?
It depends on where your other automations already live. Make gives TalentHR 25 ready modules, 9 of them instant triggers, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether TalentHR has one before comparing. The fair test is simple: list the events and actions your HR process needs, see which tool covers them without custom requests, and keep the one your team already maintains.
Same platform

Other docs you might need on this stack.

Browse all integrations