Resources · Make integration

Recruitee Make integrationAutomate Recruitee with Make.

Your hiring pipeline can update itself while you interview. The Recruitee Make integration gives you 22 modules: 3 triggers, 15 actions and 4 searches on candidates, offers, notes and tags. This guide shows recruiters and ops leads how to link the account and build a first scenario.

Try the Recruitee integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Recruitee Make integration do for your hiring?

The Recruitee Make integration links your Recruitee account to Make, a visual tool where you chain apps together without code. Make can spot new, disqualified or requalified candidates, then create, read, update or delete candidates, offers, notes and tags for you, so the admin side of hiring runs on its own.

Every applicant from outside lands in Recruitee. A referral form or a sourcing sheet feeds Create a Candidate, and Create a Note records where the person came from. Nobody retypes a profile again.

Rejections leave a trace elsewhere. Watch Disqualified Candidates picks up each disqualified person, so a talent-pool spreadsheet or a follow-up email tool can keep them in view for the next opening. Watch Requalified Candidates does the reverse when someone comes back into play.

Offers stay tidy. List Offers and Update an Offer let a hiring manager adjust open offers from a single sheet instead of clicking through each one.

Two honest limits. The three triggers are all scheduled, so Make checks Recruitee on the scenario's schedule rather than getting pinged the moment something changes. And when a listed module does not cover your case, Make an API Call reaches the rest of the Recruitee API with the same connection. Apps like Recruitee often have an n8n node too; the n8n vs Make comparison lays out the differences, the Make review covers the tool itself, and Make pricing explains how operations are counted.

Connect

How do you connect Recruitee to Make?

  1. 01

    Grab your token and company ID

    In Recruitee, open Settings, choose Personal API Tokens and click New token. Copy the token shown on screen. Then go to Company settings and copy the Company ID from that section. You need both.

  2. 02

    Add a Recruitee module in Make

    Inside your scenario (the automation you build in Make), add any Recruitee module and click Create a connection. A connection is your Recruitee account linked to Make once, then reused by every Recruitee module. Naming it in Connection name is optional but handy.

  3. 03

    Paste the credentials and save

    Paste the API token and the Company ID you copied, or follow the prompts Make displays, then save. From now on, the module lists the Recruitee data it can read, and every new module picks the same connection from a dropdown.

First scenario

Build your first Recruitee scenario in Make

GoalWhen a new candidate appears in Recruitee, Make adds a note to that profile with the screening checklist your team agreed on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Recruitee and pick Watch Candidates, the module that starts the whole chain.

  2. 02

    Link your account

    Click Create a connection, paste your API token and Company ID, and save. The trigger now reads your Recruitee account through that connection.

  3. 03

    Add the note

    Click the + on the right of the trigger and choose Create a Note. Map the candidate coming out of Watch Candidates, then type the checklist text your recruiters should see.

  4. 04

    Test with Run once

    Add a test candidate in Recruitee, then click Run once. Open each module's output to read the bundle it received (one bundle is one item, here one candidate) and check the note on the profile.

  5. 05

    Schedule and switch on

    On the first module, set the schedule. A new scenario runs every 15 minutes by default, and the Free plan cannot go lower. Switch the scenario on and let it work.

Triggers

What starts a Recruitee scenario?

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

Recruitee1Watch Candidates

Watch Candidates

Scheduled trigger

In Make“Triggers when a new candidate is created.”

Watch Candidates hands your scenario every candidate newly created in Recruitee each time your scenario checks the account, so no applicant slips past the welcome steps you set up. Each one arrives as its own bundle, ready to feed the next module.

How it fires
scheduled. Make checks Recruitee on the scenario's schedule (every 15 minutes by default, 1 minute at best on paid plans), so a fresh applicant shows up at the next check.
When to use it
any welcome step you want to happen for every applicant, like a screening note or a line in a hiring sheet.
Watch out
each candidate picked up costs operations in every module after it, so a busy offer grows your usage fast.
Recruitee2Watch Disqualified Candidates

Watch Disqualified Candidates

Scheduled trigger

In Make“Triggers when a candidate has been disqualified.”

Rejected applicants are not lost here: this trigger catches each candidate who gets disqualified in Recruitee and passes them to the rest of the scenario. That makes it the natural start for anything that should happen after a no.

How it fires
scheduled. Make checks Recruitee on the scenario's schedule, so the disqualification reaches Make at the next check, not the second a recruiter clicks.
When to use it
feeding a silver-medalist list in a spreadsheet, or tagging people you would contact again for another role.
Watch out
keep any rejection email step in a separate, reviewed flow, since a mistaken disqualification would go out too.
Recruitee3Watch Requalified Candidates

Watch Requalified Candidates

Scheduled trigger

In Make“Triggers when a candidate has been requalified.”

Second chances deserve their own signal. Watch Requalified Candidates reacts when a previously disqualified candidate is brought back into the process, and sends that person through your scenario.

How it fires
scheduled. Make checks Recruitee on the scenario's schedule, so it catches the change on its next pass.
When to use it
undoing what the disqualification flow did, for example removing someone from a talent-pool sheet or leaving a note that explains the comeback.
Watch out
pair it with the disqualified trigger in mind; if both scenarios write to the same place, make sure the second one really reverses the first.
Modules

What else can Make do in Recruitee?

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

Recruitee1

Create a Candidate

Action

In Make“Creates a candidate.”

Profiles from other tools become real Recruitee candidates without a single copy and paste. Map the details from a form, a sheet or an email parser, and the candidate appears in your account.

When to use it
referrals collected through a separate form, or leads from a job fair spreadsheet.
Watch out
run a List Candidates check first if the same person might already exist.
Recruitee2

Create an Offer

Action

In Make“Creates an offer.”

Opening a role can start outside Recruitee. This module creates a new offer from data Make already holds, such as an approved request in a project tool or a row in a headcount plan.

When to use it
when a hiring request gets approved elsewhere and the recruiter should find the offer already waiting.
Watch out
review the offer in Recruitee before publishing it anywhere.
Recruitee3

Create a Note

Action

In Make“Creates a note.”

Context sticks to the right person when Make writes it as a note. You pick the candidate, compose the text from earlier modules, and the note lands on the profile for the whole team to read.

When to use it
logging where a candidate came from, a test score from another tool, or a reminder tied to a trigger.
Watch out
keep the note short; a wall of mapped data is hard to read on a profile.
Recruitee4

Create a Tag

Action

In Make“Creates a candidate tag.”

Tags are how recruiters slice a crowded pipeline, and this module adds a new candidate tag to Recruitee straight from a scenario. It is useful when your labels come from another system.

When to use it
a new sourcing channel or campaign should exist as a tag before candidates start flowing in.
Watch out
check List Tags first, so the scenario does not create near-duplicates with different spellings.
Recruitee5

Delete a Candidate

Action

In Make“Deletes a candidate.”

Removing a candidate record becomes a scenario step, which helps when a data request or a clean-up rule arrives from another tool. The chosen candidate disappears from Recruitee.

When to use it
honoring a deletion request logged in a form or a ticketing tool.
Watch out
treat the deletion as final. Add a filter so only the intended candidate reaches this module, and test on a dummy profile.
Recruitee6

Delete an Offer

Action

In Make“Deletes an offer.”

Stale offers clutter the account. Delete an Offer removes one offer you target from a scenario, typically after it has been flagged as obsolete in a planning sheet or another tool.

When to use it
a role cancelled in your headcount plan should vanish from Recruitee too.
Watch out
treat it as permanent and think about the candidates attached to that offer before you automate it.
Recruitee7

Delete a Note

Action

In Make“Deletes a note.”

Automated notes sometimes need to go. This module wipes a specific note, which keeps profiles readable when a scenario wrote something that is no longer true.

When to use it
cleaning up placeholder notes left by an earlier test, or reversing a note when a candidate is requalified.
Watch out
target the note precisely, ideally from List Notes, or you might erase a human comment.
Recruitee8

Delete a Tag

Action

In Make“Deletes a candidate tag.”

A tag list grows messy over time. Delete a Tag removes a candidate tag you no longer use, so filters in Recruitee stay short and meaningful for the whole team.

When to use it
a campaign is over and its tag should leave the list.
Watch out
make sure no active search or saved filter still depends on that tag before you let a scenario remove it.
Recruitee9

Get a Candidate

Action

In Make“Gets a candidate.”

Triggers pass along what they saw; this module fetches one candidate's full record when a later step needs more. You point it at a candidate mapped from a previous module and get that profile as a single bundle.

When to use it
before sending data to another app that needs details the trigger bundle lacks.
Watch out
it reads one person; for many, use List Candidates.
Recruitee10

Get an Offer

Action

In Make“Gets an offer.”

Knowing which role a candidate targets often matters downstream. Get an Offer reads one offer from Recruitee and hands its details to the next module in your scenario.

When to use it
enriching a message to a hiring manager with the offer behind the application.
Watch out
it returns a single offer, so map the offer from an earlier step rather than searching for it here.
Recruitee11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

The listed modules do not cover everything Recruitee can do. Make an API Call lets you call any endpoint of the Recruitee API from your scenario, with the same connection you already set up.

When to use it
an action exists in the Recruitee API but has no ready-made module in Make.
Watch out
you write the request yourself, so keep the Recruitee API documentation open next to it.
Recruitee12

Update a Candidate

Action

In Make“Updates a candidate.”

Profiles change after the first application. Update a Candidate edits an existing candidate with fresh data from another tool, so Recruitee holds the latest details without manual edits.

When to use it
a candidate corrects their details through a form and the change should reach Recruitee.
Watch out
only map the fields you mean to change, since empty mappings can overwrite good data.
Recruitee13

Update an Offer

Action

In Make“Updates an offer.”

Hiring plans move, and offers have to follow. This module changes an existing offer in Recruitee from a scenario, which keeps a planning sheet and the job board in step.

When to use it
a hiring manager edits a role in a shared sheet and Recruitee should reflect it.
Watch out
pair it with List Offers or Get an Offer so you update the right offer, not the first one found.
Recruitee14

Update a Note

Action

In Make“Updates a note.”

Rather than stacking a new note each time, this module rewrites an existing one. It suits notes that carry a living status, like a test result that gets refined later.

When to use it
an assessment tool sends an updated score and the note on the profile should show it.
Watch out
the old text is replaced, so copy anything worth keeping into the new version.
Recruitee15

Update a Tag

Action

In Make“Updates a company tag.”

Renaming a label everywhere at once beats editing profiles one by one. Update a Tag changes a company tag in Recruitee, and the Make directory describes it as a company tag rather than a candidate tag.

When to use it
a team renames a sourcing channel and the tag should follow.
Watch out
test it on a spare tag first to see exactly which label it changes.
Recruitee16

List Candidates

Search

In Make“Gets all candidates.”

Need to work on the whole pipeline at once? List Candidates returns your candidates, zero, one or many, each as its own bundle that the next modules process one by one.

When to use it
exporting candidates to a reporting sheet, or checking whether someone already exists before creating them.
Watch out
every returned candidate runs through the following modules, and each run is an operation on your plan.
Recruitee17

List Notes

Search

In Make“Gets all notes.”

Notes hold the story of a hiring process. List Notes pulls them out of Recruitee as separate bundles, so you can archive, analyze or clean them in another tool.

When to use it
building an audit trail in a spreadsheet, or finding automated notes you plan to delete.
Watch out
a large result multiplies operations downstream, so add a filter right after it when you only need a few.
Recruitee18

List Offers

Search

In Make“Gets all offers.”

This search brings back your Recruitee offers as a set of bundles. It is the starting point for any overview of open roles outside Recruitee, such as a hiring dashboard in a spreadsheet.

When to use it
syncing open roles to a sheet that managers already read, or picking the offer to update.
Watch out
the search can return zero results, so plan what the scenario does when nothing comes back.
Recruitee19

List Tags

Search

In Make“Gets all company tags.”

Before creating or deleting tags, it helps to see what already exists. List Tags returns all company tags as bundles you can compare, filter or copy elsewhere.

When to use it
checking for a tag before Create a Tag runs, or auditing your labels in a sheet.
Watch out
tags come back one bundle each, so use a filter to keep only the name you are looking for.
Need help

Need help automating Recruitee with Make?

A person reads every message.

FAQ

Recruitee and Make: common questions

01Is the Recruitee Make integration free?
Yes, Recruitee is a standard app in Make, so you can use it on the Free plan. That plan has real limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution 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, allow unlimited active scenarios and 40 minutes of execution, with usage counted in operations per month. You still need your own active Recruitee account.
02What do you need to connect Recruitee to Make?
An active Recruitee account, an API token and your Company ID. In Recruitee, go to Settings, then Personal API Tokens, click New token and copy it. The Company ID sits in Company settings. In Make, add any Recruitee module, click Create a connection, give it a name if you like, and paste both values. The connection is then shared by every Recruitee module in your scenarios, so you only do this once per account.
03Do Recruitee triggers in Make work in real time?
No. All three Recruitee triggers, Watch Candidates, Watch Disqualified Candidates and Watch Requalified Candidates, are scheduled. Make checks Recruitee on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. So a new or disqualified candidate reaches your scenario at the next check, and the rest of the flow runs right after.
04What if a Recruitee module is missing in Make?
Use Make an API Call. It is part of the Recruitee app in Make and lets you call any endpoint of the Recruitee API with the connection you already created. That covers actions the 22 ready-made modules do not handle. You write the request yourself, so keep the Recruitee API documentation at hand. The Make documentation for this app lists no specific limits, so test each new call with Run once before switching the scenario on.
05Should you use Make or n8n for Recruitee?
It depends on the tool your team already uses. The same app often has an n8n node as well, so check that first, and neither is ranked above the other here. On Make, you get 22 ready modules covering candidates, offers, notes and tags, three scheduled triggers, and Make an API Call for the rest. Compare how each tool fits your existing scenarios and your team's habits, and read the n8n vs Make comparison linked above before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations