Resources · Make integration

JOIN Make integrationAutomate JOIN with Make.

Can Make run the busywork of your JOIN hiring pipeline without code? The JOIN Make integration gives you 17 modules: 4 scheduled triggers, 10 actions and 3 searches. This guide helps recruiters and ops leads connect JOIN and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the JOIN Make integration do for your hiring?

The JOIN Make integration links your JOIN recruiting account to Make, a visual tool where you chain modules (single bricks: a trigger, an action or a search) into a scenario, the automation that runs for you. New applications, jobs and candidate notes then travel to the other apps your team uses, and nobody writes a line of code.

Give every applicant a first note. Watch New Applications picks up each fresh application, and Create a Candidate Note pins a short summary on the profile, so the hiring manager opens JOIN and finds context already there.

Announce new openings where people read. Watch New Job Events spots a newly published job, and Get a Job pulls its details into a team message or a tracking sheet in another app.

Close roles the moment the decision is made. When a hire is recorded in another tool, Update a Job Status changes the job in JOIN, and List Applications gathers what came in for a final review.

Know the limits before you start: the Make documentation for JOIN is flagged as limited, so it gives few details on fields. When a listed module falls short, Make an API Call reaches the rest of the JOIN API with the same connection. If you are also weighing n8n, the n8n vs Make comparison lays out the criteria. The Make training covers scenario design step by step, and Make troubleshooting helps when a run stops with an error.

Connect

How do you connect your JOIN account to Make?

  1. 01

    Add a JOIN module

    In your scenario, click the + and type JOIN in the search. Pick any module, Watch New Applications for instance, then click Create a connection. A connection is your JOIN account linked to Make once; every JOIN module reuses it afterwards.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the hiring team account. The step is optional, yet it saves confusion as soon as you link a second JOIN account and have to pick the right one in a module.

  3. 03

    Authorize Make and save

    Make then asks for access: either you approve it on the JOIN page that opens, or you paste the key JOIN gives you, depending on what the window shows. Click Save. The module can now read your account and offer its content in menus.

First scenario

Your first scenario: a note on every new application

GoalWhen a new application lands in JOIN, Make adds an internal note to that candidate's profile.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. Click the + in the middle of the editor, search for JOIN and choose Watch New Applications as the first module.

  2. 02

    Connect and set the trigger

    Select your JOIN connection, or click Create a connection if this is your first JOIN module. Fill in the module fields; once connected, Make lists what it can read from JOIN, so you pick from menus.

  3. 03

    Add the note

    Click the + on the right of the trigger and add Create a Candidate Note. Map data from the application bundle, the single item the trigger hands over, into the note so the text names the job the candidate applied to.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time; read the bundles each module received, then open the candidate in JOIN and check that the note is there and reads well.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: every 15 minutes by default, never shorter than 15 minutes on the Free plan. Switch the scenario on. Each run spends operations, the module executions Make counts on your plan.

Triggers

What starts a JOIN scenario

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

JOIN1Watch New Applications

Watch New Applications

Scheduled trigger

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

Every fresh application in JOIN becomes a bundle your scenario can act on: a message to the hiring manager, a row in a sheet, a note on the profile. Most recruiting automations start here, because the application is the moment a candidate enters your pipeline.

How it fires
scheduled. Make checks JOIN on the scenario's schedule, every 15 minutes by default, and runs the following modules for what it finds.
When to use it
when each new applicant should trigger the same follow-up, whatever job they applied to.
Watch out
a popular job can bring several applications in one check, and each of them runs the next modules and counts operations.
JOIN2Watch New Candidate Notes

Watch New Candidate Notes

Scheduled trigger

In Make“Triggers when a new note is added to specific candidate.”

Feedback written on a candidate reaches the people who need it without them opening JOIN. The module follows the notes of one specific candidate and hands each new note to the rest of the scenario.

How it fires
scheduled. Make checks JOIN on the scenario's schedule and picks up the notes added to that candidate.
When to use it
for a finalist several interviewers are assessing, when the hiring manager wants every new remark sent to a chat or an email as soon as the scenario runs.
Watch out
it watches a specific candidate, not your whole pipeline, so it suits a short list better than broad volume.
JOIN3Watch New Job Events

Watch New Job Events

Scheduled trigger

In Make“Triggers when a new job is published.”

A newly published job in JOIN turns into a bundle you can share: title and details go to a team channel, a careers tracker or a referral campaign. Nobody has to remember to spread the word.

How it fires
scheduled. Make checks JOIN on the scenario's schedule and passes on the newly published jobs it finds.
When to use it
when publishing a role should always be followed by the same announcement or the same setup in another tool.
Watch out
the module name speaks of events while its description speaks of a published job; publish a test job and click Run once to see exactly what the bundle holds.
JOIN4Watch New Job Updates

Watch New Job Updates

Scheduled trigger

In Make“Triggers when an existing job is updated.”

Changes to an existing job flow out to every copy of it, so a sheet, a site or a report never shows an outdated title or description. The scenario reacts to edits rather than to new jobs.

How it fires
scheduled. Make checks JOIN on the scenario's schedule and picks up the jobs that were updated.
When to use it
when job details live in JOIN and other tools should mirror them without anyone retyping.
Watch out
if the same scenario then runs Update a Job on that job, its own edit can count as a new update on the next check; keep that change in a separate scenario.
Modules

What the JOIN modules can do

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

JOIN1

Create a Candidate Note

Action

In Make“Adds a new internal note to a candidate’s profile.”

Leave a written trace on a candidate's profile without opening JOIN, right where your recruiters already look. It fits screening remarks, feedback collected in a form or a reminder coming from another tool.

When to use it
right after Watch New Applications, to pin a first summary of the application for the hiring manager.
Watch out
the note is internal to JOIN, so keep any message meant for the applicant in a tool that actually reaches them.
JOIN2

Create a Job

Action

In Make“Creates a new job posting in your JOIN account.”

Open a new job posting in JOIN from the place where the role gets approved, such as a request form or a planning sheet. Your recruiters stop copying the same text from one tool to another.

When to use it
when hiring requests are validated outside JOIN and each approval should become a job in your account.
Watch out
every run creates a new job, so test with Run once on a dummy role before you switch the scenario on.
JOIN3

Create an Application

Action

In Make“Creates a new application in a specific job.”

Bring candidates who applied through another channel into the right job in JOIN, so the whole pipeline sits in one place. Referrals from a form or contacts met at an event can enter JOIN this way.

When to use it
when applications reach you outside JOIN and must be attached to a specific job.
Watch out
the application belongs to a specific job, so place Get a Job or List Jobs before it when your source does not carry that job.
JOIN4

Delete a Candidate Note

Action

In Make“Removes an internal note from a candidate’s profile.”

Tidy a profile by removing a note that should not be there, for instance a remark an earlier scenario posted on the wrong candidate. The profile stays readable for the next interviewer.

When to use it
as a correction step, once List Candidate Notes has found the exact note to remove.
Watch out
a deletion cannot be taken back from Make, so run your first tests on a test candidate you created for that purpose.
JOIN5

Get a Job

Action

In Make“Retrieves detailed information about a specific job by its ID.”

Turn a bare job ID into the full job record, with its details ready for the next modules. A short reference becomes a title and a description you can place in a message or a sheet.

When to use it
after a trigger or an application, when the next step needs the job's details and not just its reference.
Watch out
it reads one job by its ID; to browse several jobs or choose among them, List Jobs is the module to take.
JOIN6

Get an Application

Action

In Make“Retrieves detailed information about a specific application by its ID.”

Pull everything JOIN holds on one application from its ID, so the modules that follow work with one complete record. Handy when the scenario starts in another app that only knows the reference.

When to use it
when another tool sends you an application ID, for example after a decision logged outside JOIN.
Watch out
the module needs an exact ID; map it from a previous module rather than typing it by hand.
JOIN7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the JOIN API from your scenario, with the connection you already have, when the dedicated modules do not cover what you need. It is the escape hatch of the integration.

When to use it
for a request JOIN supports in its API that has no ready-made module in Make.
Watch out
you write the request yourself, so this module suits people who already know the endpoint they want to call, not a first scenario.
JOIN8

Update a Candidate Note

Action

In Make“Edits an existing note on a candidate’s profile.”

Correct or complete a note already on a candidate's profile instead of stacking a second one next to it. The history stays short and easy to read for the whole team.

When to use it
when a later step, such as a scored test, adds information to a note your scenario wrote earlier.
Watch out
you must point to the note to edit; List Candidate Notes finds it on the profile first.
JOIN9

Update a Job

Action

In Make“Updates details of an existing job (e.g., job title, description, office, etc.).”

Keep a JOIN job in line with your source of truth when its title, description or office changes in another tool. Recruiters no longer edit the same posting twice.

When to use it
when job details are maintained in a sheet or an HR tool and JOIN must follow those changes.
Watch out
this module edits a real, existing job, so a wrong mapping lands on a live posting; test it on a dummy job with Run once.
JOIN10

Update a Job Status

Action

In Make“Changes the status of a job.”

Change the status of a job straight from a scenario, so a role closes or reopens as soon as the decision is recorded elsewhere. Candidates stop applying to a filled position.

When to use it
when a signed offer or a budget approval lives in another tool and JOIN must reflect it.
Watch out
it touches the status only; to change the title or the description, Update a Job is the module you need.
JOIN11

List Applications

Search

In Make“Lists all applications submitted across your jobs.”

Gather the applications submitted across all your jobs in a single pass, then send each one to a report, a sheet or a review list. Useful for a full picture instead of one application at a time.

When to use it
for a pipeline review or a first import of existing applications into another tool.
Watch out
a search returns zero, one or many bundles, and each bundle runs the next modules and counts operations.
JOIN12

List Candidate Notes

Search

In Make“Lists all notes added to a specific candidate profile.”

Read every note on one candidate's profile to prepare an interview brief or to find the note you want to change. The notes come out one bundle each.

When to use it
before Update a Candidate Note or Delete a Candidate Note, or to send all feedback to a manager before a final call.
Watch out
a candidate with no notes returns zero bundles, and the modules after this one then have nothing to process.
JOIN13

List Jobs

Search

In Make“Lists all jobs in your account.”

Get every job in your account, one bundle per job, to feed an overview of open roles or a check across your postings. It is the module that lets a scenario pick the right job.

When to use it
when a later step, such as Create an Application or Update a Job Status, must first find the matching job.
Watch out
the modules placed after it run once per job, so an account with many roles spends operations fast.
Need help

Need help automating JOIN with Make?

A person reads every message.

FAQ

JOIN and Make: common questions

01Is the JOIN Make integration free?
Yes. JOIN is a standard app in Make, so it works on the Free plan. That plan allows 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) remove the cap on active scenarios, allow shorter intervals and count usage in credits, meaning operations, each month. Your JOIN subscription is a separate matter that this page does not cover.
02What does it take to connect JOIN to Make?
A JOIN account and a Make account. The Make documentation for JOIN lists no other prerequisite and no dedicated connection steps, so the generic path applies. Add any JOIN module, click Create a connection, optionally give it a name, then either authorize Make on the JOIN page or paste the key JOIN provides, and click Save. The connection is then reused by all 17 JOIN modules, so this setup happens once per account.
03Do JOIN triggers fire the moment something happens in JOIN?
No. All 4 JOIN triggers are scheduled: Make checks JOIN on the scenario's schedule instead of receiving a signal from the app. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans allow shorter gaps. None of the JOIN modules is an instant trigger, so for faster reactions the lever is the schedule you set on the first module.
04What if the JOIN module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the JOIN API from your scenario with the same connection, so it covers what the dedicated modules leave out. Keep in mind that the Make documentation for JOIN is flagged as limited, which means few details on fields and behaviors. Test each new step with Run once and read the bundles it returns before you switch the scenario on, so surprises show up during testing.
05Make or n8n for JOIN: which one fits?
It depends on your criteria rather than on a winner. This page covers Make: 17 JOIN modules, 4 scheduled triggers, and the Free plan to start. Many apps also have an n8n node, so check whether JOIN has one and whether it covers the same triggers and actions you need. Then compare on what matters for your team, such as the modules available and the tool people already know. Neither option is ranked here.