Resources · Make integration

Hirely Make integrationAutomate Hirely with Make.

Can a new Hirely applicant set off the rest of your hiring process on its own? The Hirely Make integration gives you 30 modules: 13 triggers and 17 actions. This guide shows recruiters and ops leads how to link the account and build a first working scenario.

Try the Hirely integration on MakeSee the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hirely Make integration do for your hiring?

The Hirely Make integration links your Hirely account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches Hirely or acts in it. Make notices what changes in your recruiting pipeline and passes each item, called a bundle, to the next step without anyone copying data by hand.

Every applicant gets a follow-up. Watch Applications picks up each new candidacy, and Create a Task gives the recruiter a to-do in Hirely right away. Add Create a Comment to leave context on the file for the hiring manager.

Job ads stay in sync with your other tools. When a role is approved elsewhere, Create a Job Offer drafts it in Hirely and Publish a Job Offer puts it live. Watch Archived Job Offers then tells the rest of your stack when the position closes.

Hiring decisions travel beyond Hirely. Watch Hired Applicants and Watch Rejected Applicants catch the outcome of each process, so an onboarding checklist or a polite closing message can start from the same event.

A few limits are worth knowing. Judging by their names, all 13 triggers are scheduled: Make polls Hirely instead of hearing from it instantly. The Make documentation for Hirely also warns that its content is AI-generated and may contain mistakes, so test each module on a sample record first. If a scenario misbehaves, the Make troubleshooting guide covers the usual suspects, and the Make pricing page explains how operations add up.

Weighing another automation tool? The n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect your Hirely account to Make?

  1. 01

    Create an API key in Hirely

    In Hirely, click your profile picture in the top right, open Benutzerkonto, then Entwickler-Einstellungen in the left menu. Click + API-Schlüssel erstellen, give the key a name and copy it straight away.

  2. 02

    Add a Hirely module to a scenario

    In Make, open a scenario, click the +, search for Hirely and pick any module. Click Create a connection. The connection is your Hirely account linked to Make once and reused by every Hirely module.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, which helps when several Hirely accounts coexist. Paste the API key you copied and confirm. Make can now read and write in your Hirely workspace.

First scenario

Your first scenario: a task for every new Hirely application

GoalWhen a new application lands in Hirely, Make creates a follow-up task for the recruiter in Hirely.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Hirely and choose Watch Applications as the first module.

  2. 02

    Link your account

    Click Create a connection and paste your Hirely API key. Once the connection works, Make can list what it reads in Hirely, so there is nothing to type from memory.

  3. 03

    Add the task

    Click the + on the right of the trigger and add Hirely Create a Task. Map the candidate name from the previous module into the task so the recruiter knows who to call.

  4. 04

    Test with Run once

    Submit a test application in Hirely, then click Run once. Open the bubbles above each module to read the bundles it received and check that the task shows up in Hirely.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and paid plans go down to 1 minute. Pick your interval and turn the scenario on.

Triggers

Hirely triggers: what can start a scenario

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

Hirely1Watch Applications

Watch Applications

triggerIn the docs only

This trigger hands every new candidacy to your scenario, one bundle per applicant, so nobody has to refresh the Hirely inbox to spot fresh profiles.

How it fires
scheduled. Make checks Hirely on the scenario's schedule, every 15 minutes unless you change it.
When to use it
when an application should open a task, notify a hiring manager in chat or add a row to a reporting sheet.
Watch out
each applicant fetched counts as an operation, so a busy job ad uses more of your plan than a quiet one.
Hirely2Watch Archived Job Offers

Watch Archived Job Offers

triggerIn the docs only

Closing a position becomes a signal the rest of your tools can act on: this trigger returns job offers that have moved to the archive in Hirely.

How it fires
scheduled. Make asks Hirely for newly archived offers each time the scenario runs.
When to use it
when a closed role should also disappear from an internal job board, or when the team channel should hear that hiring for it is over.
Watch out
pair it with Archive a Job Offer in another scenario only if that scenario does not also listen here, or the two will feed each other.
Hirely3Watch Campaigns

Watch Campaigns

triggerIn the docs only

With this module, a new recruiting campaign in Hirely can kick off everything that usually surrounds it, from a budget line to a kickoff note for the team.

How it fires
scheduled. Make polls Hirely for campaigns at the interval set on the first module.
When to use it
when marketing or finance must know that a campaign exists, for example to log it in a tracking sheet as soon as it appears.
Watch out
nothing documented says what a campaign bundle contains, so run it once and read the bundle before mapping anything downstream.
Hirely4Watch Customers

Watch Customers

triggerIn the docs only

For agencies that recruit on behalf of clients, this trigger sends each new customer record from Hirely into your scenario so the account exists everywhere it should.

How it fires
scheduled. On every run of the scenario, Make looks in Hirely for customers it has not seen yet.
When to use it
when a new client in Hirely should also land in your CRM or your invoicing tool without a second entry.
Watch out
if another scenario uses Create a Customer from that same CRM, check that the two flows cannot send the same client back and forth.
Hirely5Watch Domains

Watch Domains

triggerIn the docs only

This one keeps an eye on the domains recorded in your Hirely account and passes each new one along, handy when career pages live on several addresses.

How it fires
scheduled. Make queries Hirely for domains following the scenario's own timing.
When to use it
when the web or IT team wants a heads-up that a domain was added, so they can check the setup on their side.
Watch out
domains change rarely, so a scenario built on this trigger will often run and find nothing, which still uses a check each time.
Hirely6Watch Hired Applicants

Watch Hired Applicants

triggerIn the docs only

The moment of hire is where onboarding starts, and this trigger delivers each newly hired applicant to your scenario as its own bundle.

How it fires
scheduled. Make looks for fresh hires in Hirely at the pace of the scenario, not the second the decision is made.
When to use it
when a signed candidate should get an onboarding checklist, an account request to IT or a welcome message from the team.
Watch out
the delay between the hire and the next check is normal for a scheduled trigger, so do not expect the welcome to go out instantly.
Hirely7Watch Job Offers

Watch Job Offers

triggerIn the docs only

Every job offer created in Hirely, published or not, can reach your scenario through this trigger, which gives you a single place to react to new openings.

How it fires
scheduled. Make checks Hirely for new offers each time the clock on the first module ticks.
When to use it
when a new role should be announced to the team or copied into a headcount tracker before it goes public.
Watch out
only live ads matter to you? Watch Published Job Offers is the closer fit and avoids reacting to drafts.
Hirely8Watch Linked Customers

Watch Linked Customers

triggerIn the docs only

Where Watch Customers catches new client records, this trigger focuses on customers that have been linked inside Hirely, a useful distinction for agencies juggling several accounts.

How it fires
scheduled. Make polls Hirely for linked customers on the scenario's timing.
When to use it
when the link itself is the event that matters, such as giving a client access to a shared folder once the relationship is set up.
Watch out
the Make documentation for Hirely gives no description of this module, so test it with Run once to see exactly what a bundle contains.
Hirely9Watch Locations

Watch Locations

triggerIn the docs only

Opening a new office or site in Hirely can update the rest of your company data too: this trigger reports each location added to the account.

How it fires
scheduled. Make asks Hirely for new locations whenever the scenario runs.
When to use it
when a new site should appear in the list your HR team keeps elsewhere, or when facilities needs to know about it.
Watch out
if you also create locations from Make with Create a Location, keep that scenario separate from this one to avoid duplicates.
Hirely10Watch Published Job Offers

Watch Published Job Offers

triggerIn the docs only

Only offers that actually go live come through here, which makes it the right starting point for anything candidates will see.

How it fires
scheduled. Make checks Hirely for newly published offers at the interval of the scenario.
When to use it
when a published ad should be shared on the company social accounts, posted in an employee referral channel or logged for reporting.
Watch out
a scenario that publishes with Publish a Job Offer and listens here at the same time will pick up its own work, so split them.
Hirely11Watch Rejected Applicants

Watch Rejected Applicants

triggerIn the docs only

A clean close for every candidate who was turned down: this trigger returns each applicant marked as rejected in Hirely.

How it fires
scheduled. Make collects the latest rejections from Hirely on the scenario's schedule.
When to use it
when a rejection should add the person to a talent pool for later roles, or update the numbers in a hiring dashboard.
Watch out
if Reject an Application runs in another scenario, rejected people reach this trigger too, so make sure nothing sends them a second message.
Hirely12Watch Tasks

Watch Tasks

triggerIn the docs only

Tasks created in Hirely, whether by a recruiter or by Make, show up here as bundles, which lets you mirror them into the tool your team actually checks.

How it fires
scheduled. Make looks for new tasks in Hirely at each scheduled run.
When to use it
when hiring to-dos should also appear in a project board or a shared calendar outside Hirely.
Watch out
never end this scenario with Create a Task or Update a Task on the same records, or each run will create work for the next one.
Hirely13Watch Users

Watch Users

triggerIn the docs only

This trigger tracks the people who have access to your Hirely account and returns each new user, so seat changes do not go unnoticed.

How it fires
scheduled. Make checks Hirely for new users on the rhythm of the scenario.
When to use it
when an admin wants a log of who joined the workspace, or when a new hiring manager should get a short guide by email.
Watch out
Invite an User adds people from Make; if both sit in one flow, the invitation will come back here as a new user.
Modules

Hirely actions: what Make can do in your account

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

Hirely1

Archive a Job Offer

ActionIn the docs only

Role filled or cancelled? Take it off the board from Make, without opening Hirely, and the ad stops collecting candidates.

When to use it
when a signed offer in your HR tool means the position is closed and the listing should follow.
Watch out
run it once on a test offer first, since archiving a live ad by mistake cuts off incoming applications.
Hirely2

Create a Comment

ActionIn the docs only

Leave a note inside Hirely automatically, so the context gathered elsewhere sits next to the candidate file where recruiters read it.

When to use it
when a phone screen summary, a test score from another tool or a referral note should be attached to an application.
Watch out
map only what the team needs to read; a comment full of raw data is harder to scan than no comment.
Hirely3

Create a Customer

ActionIn the docs only

Add a client to Hirely straight from the tool where the deal was won, which saves agencies from typing the same company twice.

When to use it
when a contract signed in your CRM should give the recruiting team a customer record ready for its first job offer.
Watch out
each run adds a record, so filter out clients that already exist in Hirely before this step.
Hirely4

Create a Customer Group

ActionIn the docs only

Group related clients in Hirely from a scenario, a quick way to keep large accounts or regional divisions together.

When to use it
when a new parent company appears in your CRM and its subsidiaries should be gathered under one group before you add them.
Watch out
create the group before the customers that belong to it, and keep the order of modules in the scenario to match.
Hirely5

Create a Job Offer

ActionIn the docs only

Draft a new opening in Hirely from an approved request, so the hiring manager's form becomes a job offer without copy and paste.

When to use it
when a headcount approval in a form or a spreadsheet should produce the offer that recruiters then polish.
Watch out
creating is not publishing; add Publish a Job Offer later in the flow if the ad must go live too.
Hirely6

Create a Location

ActionIn the docs only

Record a new site in Hirely from Make, so offers for that office can point to the right place from day one.

When to use it
when your company directory gains a new office and job offers there are about to open.
Watch out
check the spelling of the site against what already exists in Hirely, since near duplicates make filtering offers harder.
Hirely7

Create a Task

ActionIn the docs only

Put a clear to-do in front of a recruiter inside Hirely, triggered by whatever event needs a human follow-up.

When to use it
when a new application, a missing document or a date set in a calendar tool should become a task that someone owns.
Watch out
a task per bundle adds up fast, so filter the flow so that only events that need a person reach this module.
Hirely8

Create an Application

ActionIn the docs only

Bring candidates who applied outside Hirely into the same pipeline, so a form, a job fair list or a referral all end up in one place.

When to use it
when a careers form on another site or a referral sheet collects profiles that recruiters should screen in Hirely.
Watch out
test with Run once and a fake candidate before going live, then remove that test file from the pipeline.
Hirely9

Hire a Candidate

ActionIn the docs only

Mark someone as hired in Hirely when the final step happens in another tool, so the pipeline reflects the real decision.

When to use it
when the signature of an employment contract in an e-signature tool is the moment that really closes the process.
Watch out
this changes a candidate's status; if Watch Hired Applicants starts other scenarios, they will fire from this action too.
Hirely10

Invite an User

ActionIn the docs only

Give a colleague access to Hirely from Make, which keeps workspace seats in step with your team directory.

When to use it
when a new hiring manager is added to your HR system and should be able to review candidates without waiting for an admin.
Watch out
every run sends an invitation, so filter out people who already have access before this step.
Hirely11

Make an API Call

ActionIn the docs only

Reach any part of the Hirely API that the ready-made modules leave out, using the same connection and no extra login.

When to use it
when you need something none of the ready-made triggers or actions covers, and the Hirely API documents it.
Watch out
you write the request yourself here, so keep the Hirely API reference open and test with Run once.
Hirely12

Publish a Job Offer

ActionIn the docs only

Push an existing offer live from a scenario, which lets an approval somewhere else decide when candidates can see it.

When to use it
right after Create a Job Offer, or when a manager ticks an approval box in a shared sheet.
Watch out
once public, the ad starts collecting candidates, so place this step after any review the team requires.
Hirely13

Reject an Application

ActionIn the docs only

Close an application in Hirely from Make when the decision comes from somewhere else, such as a failed assessment in another tool.

When to use it
when a scoring tool or a knockout question in a form already tells you the profile does not fit.
Watch out
an automated rejection affects a real person, so keep a filter strict enough that no good profile slips into it.
Hirely14

Update a Company

ActionIn the docs only

Keep your company details in Hirely aligned with the source of truth elsewhere, without anyone editing the profile twice.

When to use it
when company information changes in your main HR or CRM system and Hirely should reflect it too.
Watch out
this edits your own company record, so test on a harmless change first and read the result in Hirely.
Hirely15

Update a Job Offer

ActionIn the docs only

Change an existing offer from a scenario, handy when the details of a role are maintained in a shared spreadsheet or a planning tool.

When to use it
when a manager edits a role in the source sheet and the Hirely ad should follow without a manual copy.
Watch out
do not start this scenario with Watch Job Offers on the same offers, or each update will trigger another one.
Hirely16

Update a Task

ActionIn the docs only

Edit a task in Hirely from Make, so its status stays in line with what happens in the tool where people actually do the work.

When to use it
when a card is moved to done on a project board and the matching Hirely task should reflect it.
Watch out
you need to know which task to change, so store the Hirely task reference when you first create it.
Hirely17

Update an Application

ActionIn the docs only

Enrich or correct a candidacy already in Hirely with information gathered after it arrived, keeping one file per candidate.

When to use it
when an interview scheduling tool or an assessment platform returns a result that belongs on the application.
Watch out
never place it right after Watch Applications on the same records if updates can look like new items to that trigger.
Need help

Need help automating Hirely with Make?

A person reads every message.

FAQ

Questions about Hirely and Make

01Is the Hirely Make integration free?
Yes on the Make side: Hirely is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans such as Core, Pro, Teams and Enterprise lift those limits and count usage in credits each month. Hirely itself is a separate subscription: you need an active Hirely account with an API key, and its pricing is on the Hirely website.
02What do you need to connect Hirely to Make?
An active Hirely account and an API key from it. In Hirely, open your profile picture, then Benutzerkonto and Entwickler-Einstellungen, click API-Schlüssel erstellen, name the key and copy it. In Make, add any Hirely module, click Create a connection, optionally name the connection, and paste the key. The same connection then serves every Hirely module in all your scenarios, so this setup happens only once per account. For the Hirely subscription itself, the Hirely pricing page has the details.
03Are Hirely triggers instant or scheduled in Make?
Scheduled, as far as their names tell: the Make documentation does not state the type of the 13 triggers. Make asks Hirely for new items each time the scenario runs rather than being called by Hirely the moment something happens. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans can go down to 1 minute. For hiring workflows such as follow-up tasks or onboarding, that pace usually works well, but a candidate will not get a reply in the same second they apply.
04What if a Hirely module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Hirely API with the connection you already set up, so you are not limited to the 30 listed modules. Keep in mind that the Make documentation for Hirely states that it is AI-generated and may contain mistakes, so check important details against Hirely's own documentation or ask Hirely directly. Testing each new step with Run once on a sample record is the safest habit.
05Should you use Make or n8n for Hirely?
It depends on what you need from the tool. Make gives you 30 ready-made Hirely modules, a visual editor and a Free plan to test a first scenario. Before choosing n8n, check whether it offers a Hirely node and how much of the API it covers, since that decides how much setup is left to you. Compare the two on your own criteria: modules available, how your team likes to build, and how usage is counted on each plan.
Same platform

Other docs you might need on this stack.

Browse all integrations