Resources · Zapier integration

Hirely Zapier integrationAutomate Hirely with Zapier.

The Hirely Zapier integration gives you 11 triggers and 11 actions, with no search step. Ten of the triggers are instant, so new applications, hires and published job offers reach your Zap the moment they happen, even on the free plan.

See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Hirely Zapier integration actually does for a hiring team

The Hirely Zapier integration lets Hirely start automations and receive instructions from them. Something happens in Hirely (an application lands, a candidate is hired, a job offer goes live), and Zapier runs the steps you chose next. It also works the other way: Zapier can create job offers, applications, tasks or users inside Hirely for you.

Three outcomes are worth building first. First, a to-do for every hire: Applicant Hired feeds Create Task, so onboarding never depends on someone remembering. Second, a job board that runs itself: New Job Offer can hand over to Publish Job Offer, and Archive Job Offer closes a position when you decide it is filled. Third, a tidy team list: Invite User and Remove User keep access in line with who actually works on recruiting.

Now the limits. The integration has no search step, so a Zap cannot look up an applicant, an offer or a user that already exists in Hirely; it only works with what the trigger hands over or what you type. Several operations (campaigns and customers) are reserved to agencies. And every single step asks for a Company-ID, so a Zap always works inside one company at a time.

If you want the same app in another tool, the Hirely Make integration page is the counterpart on Make.

Vocabulary

Zapier vocabulary, in plain words

Seven words come back on every line of this page. Here is what each one means for a Hirely user.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event that starts the Zap, like a new application in Hirely. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that creates, updates or removes something for you, in Hirely or elsewhere.
Task
The unit Zapier bills. One action completed successfully counts as one task, and your plan is a monthly count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks Hirely for new items at a fixed interval and keeps only what it has not seen yet.
Instant trigger
A trigger Hirely reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it otherwise.
Connection
Your Hirely account linked to Zapier once, then reused by every step that talks to Hirely.
Cost

What a Hirely Zap really costs

Zapier bills actions, never triggers. Watching Hirely for new applications costs nothing, however often it happens.

  • Tasks per month, free plan100
  • Steps per Zap, free plan2 (one trigger, one action)
  • Cost of a trigger0 tasks
  • Premium appNo

Each action that works counts as one task. An action that fails is not counted. A Zap with three actions uses three tasks per run, so the bill follows the number of steps, not the number of Zaps. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. Add a second action or a filter and the Zap becomes a multi-step Zap (anything beyond one trigger and one action), which needs a paid plan. Hirely is not a premium app, so it works on the free plan.

Connect

Connect your Hirely account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Before you start, make sure you have a Hirely account, plus access to any company you do not own but want the Zap to touch.

  2. 02

    Find Hirely and add it

    Type Hirely in the search box of the dialog, pick it from the results, then click Add connection. Zapier opens a new tab where Hirely asks you to sign in.

  3. 03

    Sign in and grant access

    Log in with your Hirely credentials and accept the access request. From then on, every Hirely step in every Zap reuses this connection, so you do it once per account.

First Zap

Your first Zap: every published offer switched on for Google Jobs, with a promotion to-do

GoalWhen a job offer goes live in Hirely, turn on its Google Jobs listing and create a task so the team shares the opening on its own channels.

  1. 01

    Build: pick the trigger

    Create a new Zap, choose Hirely as the app and Job Offer Published as the event. Select your Hirely connection and set the Company-ID of the company you recruit for.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent published offers of the account, so you map the next steps on a real offer rather than an empty sample.

  3. 03

    Switch on Google Jobs

    Add an action, pick Hirely and Update Job Offer. Fill the Company-ID again, map the offer's ID from the test item into JobOffer-ID, and turn on Publish On Google Jobs.

  4. 04

    Add the promotion task

    Add Create Task and build the Title from the test result, for example "Share:" followed by the offer's name. With two actions this Zap is multi-step, so it needs a paid plan.

  5. 05

    Test, then Publish

    Test each action once and open Hirely to check the offer's setting and the new task. When both look right, click Publish to switch the Zap on.

Triggers

Hirely triggers on Zapier

11 events start a Zap when something happens in Hirely, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Applicant Hired

Instant trigger

In Zapier“Triggers when an applicant was marked as "hired"”

Starts your Zap as soon as someone on the team marks a candidate as hired. It is the cleanest signal Hirely gives for the end of a recruiting process, because it fires on a decision, not on a draft.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a startup's hiring manager wants an onboarding task and a welcome checklist created the minute an offer is accepted.
Watch out
the trigger is tied to one Company-ID, so a second company needs its own Zap.
2

Applicant Rejected

Instant trigger

In Zapier“Triggers when an applicants application gets rejected”

Fires when an application gets rejected in Hirely. Use it for whatever has to happen after a no: closing a loop, logging the outcome, or freeing a slot in someone's schedule.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a recruiter who wants a follow-up task to send a personal note to every finalist who did not get the job.
Watch out
it reacts to each rejection one by one, so a bulk cleanup of old applications can start many runs at once and eat tasks quickly.
3

Job Offer Archived

Instant trigger

In Zapier“Triggers when a job-offer's status is set to "archived"”

Runs when a job offer's status switches to archived. That makes it the natural place to wrap up a position: tell the team, clean up related tasks, or record that the role is closed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an operations lead wants a task reminding them to update the headcount plan each time a role is taken off the career page.
Watch out
if another Zap archives offers with Archive Job Offer, this trigger fires on those too, which is fine unless the two Zaps feed each other.
4

Job Offer Published

Instant trigger

In Zapier“Triggers when a job-offer's status is set to "published"”

Fires when a job offer moves to published, which is the moment candidates can actually see it. It is a different event from creation, which New Job Offer covers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketing team that wants a task to promote every new opening on its own channels, only once the offer is live.
Watch out
a Zap on this trigger that also runs Publish Job Offer can loop, so keep those two apart.
5

New Application

Instant trigger

In Zapier“Triggers when a new application is created.”

Starts the Zap whenever a new application is created in Hirely, the moment a candidate lands in your pipeline.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a small agency team that wants a review task assigned for every candidate, so nobody sits unread in the pipeline.
Watch out
a Zap that also runs Create Application in the same company sets itself off again; keep imports in a separate Zap.
6

New Campaign

Instant trigger

In Zapier“Triggers when a new campaign is created. (Only for agencies)”

Agency accounts get this one when a new campaign is created. Hirely reserves this one to agencies, so on a regular company account it has nothing to report.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a recruitment agency that opens a campaign per client brief and wants a kickoff task created for the account manager straight away.
Watch out
set the Company-ID of the agency itself, not the client's, or the trigger watches the wrong place.
7

New Customer

Instant trigger

In Zapier“Triggers when a new customer is created. (For Agencies only)”

Reacts when an agency creates a new customer in Hirely. Like the campaign trigger, it only exists for agency accounts, where customers are the companies you recruit for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency that wants every new client to get a setup task, so the account is ready before the first job offer.
Watch out
the trigger also asks whether to include existing companies that link to your agency as customers; that answer is required and changes what counts as new.
8

New Customer Linked

Instant trigger

In Zapier“Triggers when an existing company links to your agency as a customer. (For Agencies only)”

Covers the moment a company that already has its own Hirely account links to your agency as a customer. It covers the case the previous trigger misses: the client did not start from your side.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency partner who wants to know the day an existing Hirely user signs up with them, to plan a first call.
Watch out
it is for agencies only, and the Company-ID you set must be the agency's.
9

New Job Offer

Instant trigger

In Zapier“Triggers when a new job offer is created.”

Catches each job offer at creation, before anyone has published it. Pair it with an action when you want a review or an approval to happen at the draft stage.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a head of people who wants a check task on every new draft, so wording and location are validated before the offer goes out.
Watch out
a Zap on this trigger that runs Create Job Offer in the same company would feed itself without end.
10

New Task

Polling trigger

In Zapier“Triggers when a new task is created”

Picks up every new task created in Hirely. It is the only trigger of the app that works by checking on a timer, so it behaves differently from the ten others.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a team lead who wants new recruiting tasks copied into the tool where the rest of the team plans its week.
Watch out
a Zap that answers this trigger with Create Task in the same company will spin in a loop and burn tasks.
11

New User

Instant trigger

In Zapier“Triggers when a new user is added to the company”

Kicks in when a user is added to the company in Hirely. Useful for anything that should follow a new seat: a welcome, a training reminder, an access check in another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an IT admin who wants a task to walk every new hiring manager through the recruiting process on day one.
Watch out
the Company-ID is required here too, so the Zap only sees new users of that one company.
Actions

Hirely actions on Zapier

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

1

Archive Job Offer

Action

In Zapier“Archives a currently published job offer”

Archives a job offer that is currently published, which takes it off the market. You give it the Company-ID and the Job Offer ID.

When to use it
taking a role off the career page when the hiring request is closed in another tool that holds the offer's ID.
Watch out
it only applies to a published offer, so a draft has nothing to archive.
2

Create Application

Action

In Zapier“Creates a new application.”

Adds an application to a job offer, with first name, surname and e-mail. Two options decide whether the team gets notified and whether Hirely's automatic process actions (emails, status changes) run.

When to use it
bringing referrals collected through a form into the right opening.
Watch out
leave automatic actions on only if candidates should get Hirely's usual emails.
3

Create Customer

Action

In Zapier“Creates a new customer (for registered agencies only)”

Creates a customer for a registered agency, with a name and a full address. Each address field has a length cap: 100 characters for the street, 10 for the postal code, 50 for city and state, 2 for the country code.

When to use it
an agency that signs clients in its CRM and wants them in Hirely without retyping.
Watch out
company accounts cannot use it.
4

Create Job Offer

Action

In Zapier“Creates a job offer for the company”

Creates a job offer for the company, with the public name candidates and job boards will see. It needs a Location-ID, so the location has to exist first.

When to use it
a staffing team that drafts offers from an approved hiring request in another tool.
Watch out
making it public is a separate step, Publish Job Offer.
5

Create Location

Action

In Zapier“Creates a new company location.”

Adds a company location, with an internal name, street, postal code, city, state and a 2-digit country code. All of these are required.

When to use it
a company opening a new office that wants job offers attached to it from the start.
Watch out
a full country name instead of the code will not pass.
6

Create Task

Action

In Zapier“Creates a new Task for your account”

Creates a task in Hirely tied to a company, with a title as the only other required field. It is the simplest action of the app, and a safe first step to test a new Zap.

When to use it
turning any signal (a hire, a new draft, a rejection) into a to-do the team sees in Hirely.
Watch out
never pair it with the New Task trigger on the same company.
7

Invite User

Action

In Zapier“Invites a user to your company”

Sends an invitation to join your company in Hirely, from just an e-mail address and the Company-ID.

When to use it
giving every new hiring manager access as soon as they appear in your HR tool.
Watch out
the step sends an invitation; nothing in the integration tells you whether the person accepted it.
8

Publish Job Offer

Action

In Zapier“Publishes a job offer.”

Takes an existing job offer and makes it public, from its Job Offer ID. It is the step that turns a draft into something candidates can apply to.

When to use it
publishing approved drafts without someone opening Hirely to click the button.
Watch out
the ID must come from an earlier step or be typed; there is no search to find it.
9

Remove User

Action

In Zapier“Removes an user from the company”

Removes a user from the company in Hirely, from their User-ID. This is the offboarding counterpart of Invite User.

When to use it
cutting recruiting access the day someone leaves, driven by your HR system.
Watch out
you need the User-ID itself; an e-mail address will not do, and there is no search step to convert one into the other.
10

Update Company

Action

In Zapier“Updates the details of a company”

Edits the details of a company in Hirely. Only the Company-ID is required; everything else is what you choose to change.

When to use it
keeping the company profile in Hirely aligned with the master record held in another system.
Watch out
test it on a real company first and check the result in Hirely before you publish.
11

Update Job Offer

Action

In Zapier“Updates an existing job offer”

Changes an existing job offer. Beyond the usual details, it exposes three switches: formal or informal tone for generated text, publishing on Google Jobs, and publishing on the career page.

When to use it
switching on Google Jobs for every offer once it is approved.
Watch out
the JobOffer-ID is required, and the integration offers no way to look it up.
When it breaks

When a Hirely Zap breaks

Hirely has no help article of its own on Zapier, so the failures to plan for are the general ones, applied to how this app works.

The surprises come from three places: what the Zap cannot see, what it sets off by itself, and the Company-ID it was given. When a run goes wrong, head to Zapier troubleshooting.

  • No catch-up on old records

    A Zap only reacts to what happens after you publish it. Applications, hires or offers that already existed are never picked up; moving that backlog is a separate job.

  • A Zap that triggers itself

    Writing into the place your trigger watches restarts the Zap: New Task with Create Task, or New Application with Create Application. The loop burns through your task count fast.

  • Bulk changes held back

    A sudden batch, after an import or a mass status change in Hirely, can be held by Zapier's flood protection instead of running all at once.

  • New Task never repeats an item

    On the polling trigger, Zapier remembers what it has already seen, so the same task never starts the Zap twice.

  • Agency-only steps on a company account

    New Campaign, New Customer, New Customer Linked and Create Customer are for agencies. On a regular company account they have nothing to work with.

  • The wrong Company-ID

    Every step is scoped to one Company-ID. Point it at a company the connected account cannot reach, or at the client instead of the agency, and the step fails.
Need help

Need help automating Hirely with Zapier?

A person reads every message.

FAQ

Hirely Zapier integration: frequent questions

01Is the Hirely Zapier integration free?
Yes, as far as Zapier goes. Hirely is not a premium app, so it works on Zapier's free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you want two actions, for example switching on Google Jobs and creating a task when an offer goes live, or a filter in between, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Hirely Zap use?
One per action that succeeds, nothing for the trigger. A Zap that creates a task each time a candidate applies uses one task per application. Add a second Hirely action and each application costs two. Actions that fail are not counted, and the time Zapier spends checking the New Task trigger is free too. So the number to watch is volume times the number of action steps, especially on a busy opening where New Application can fire many times a day.
03Does Hirely send data to Zapier in real time?
For ten of the eleven triggers, yes. Applicant Hired, Applicant Rejected, New Application, the job offer triggers, the agency triggers and New User are instant: Hirely tells Zapier the moment the event happens, and that holds on every plan, the free one included. The exception is New Task, which Zapier checks on a timer. On the free plan that check happens every 15 minutes; on Professional every 2 minutes, and every minute on Team and Enterprise.
04What does it take to connect Hirely to Zapier?
A Hirely account, and access to every company the Zap should touch. You add the connection from the Apps page of Zapier with + Add connection, sign in to Hirely in the tab that opens, and allow access. Then each step asks for a Company-ID. If the connected account cannot see that company, the step fails. Agency accounts should also check whether they point at the agency itself or at a client company.
05Why does the New Customer trigger never fire on some accounts?
Most likely because the account is not an agency. Hirely reserves New Customer, New Customer Linked, New Campaign and the Create Customer action to registered agencies. On a regular company account those events simply never happen, so the Zap waits with nothing to report. If you do run an agency, check that the Company-ID set in the trigger is the agency's own ID, and look at the required Include linked companies option, which changes which customers count as new.
06What if the Hirely action you need doesn't exist?
Then the Zapier integration cannot do it, and the page lists everything it can: 11 triggers and 11 actions, with no search step. That last point is the one that limits people most: a Zap cannot look up an existing applicant, job offer or user, so any ID has to come from the trigger or be typed in. When a missing step blocks a whole process, a team that builds Zaps daily, such as our Zapier agency, can help you design around it.
07Zapier, Make or n8n: which one for Hirely?
It depends on your criteria rather than on a winner. Zapier is a good fit when the eleven triggers and eleven actions on this page cover your case: ten of the triggers are instant on every plan, and connecting takes a sign-in. The gap to weigh is the missing search step, since no Zap can look up an existing offer, applicant or user. If that matters for your process, check what the Make and n8n versions of Hirely offer before choosing, and decide on that, plus the tool your team already runs.
Same platform

Other docs you might need on this stack.

Browse all integrations