JOIN Zapier integrationAutomate JOIN with Zapier.
The JOIN Zapier integration gives you 3 triggers, 2 actions and 2 searches to move applicants and job ads out of your recruiting tool. All three triggers are instant, it works on the free plan, and this page shows what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the JOIN Zapier integration actually does for a hiring team
The JOIN Zapier integration links your JOIN recruiting account to the other tools your team already uses. A Zap (an automation you build once on Zapier: one starting event, then the steps that follow) watches JOIN for new applicants or job status changes, then acts elsewhere, or writes back into JOIN for you.
Three results come up again and again. First, a hiring manager who hears about every new candidate without opening JOIN: Application Created starts the Zap, and a message lands in chat or a row lands in a sheet. Second, applicants collected somewhere else (a careers form, a referral sheet, an event list) that end up in the right job: Create Application files them, as long as the Zap knows the job's ID. Third, a job board that stays in sync with reality: Job Published and Job Unpublished tell your other tools when an ad goes live or comes down, and Update Job Status can flip an ad online, offline or archived from another app.
Now the part the app page skips. Zapier does not edit or delete an application in JOIN, does not create a job ad, and does not move a candidate between stages: the integration only offers the seven operations listed below. It also reacts only to what happens after the Zap is switched on, so last month's applicants stay where they are. If your process needs more than that, our Zapier agency can look at the case with you.
The same app also has a JOIN Make integration page, if you want to weigh the other platform before you build.
Zapier vocabulary in one minute
Seven words cover everything on this page. Each one is used exactly like this from here on.
- Zap
- Your automation on Zapier: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for it to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
- Task
- What Zapier bills you for: one action that your Zap completes successfully. Your plan's allowance is a count of these.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets the condition you set, and stops it quietly otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can reuse what it found.
What a JOIN Zap really costs
JOIN is not a paid-only app on Zapier, so it runs on the free plan.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2 steps per Zap
- JOIN triggers3 instant, 0 polling
The trigger never costs a task, and neither does Zapier waiting for events. Every action that succeeds counts once; a failed one does not count. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search or a second action and it becomes a multi-step Zap, which needs a paid plan. The interval grid below concerns polling triggers only; all JOIN triggers are instant, so it never slows them down.
Connect your JOIN account in three steps
- 01
Open your Zapier apps
Go to the Apps page of your Zapier account and click + Add connection. A connection is your JOIN account linked to Zapier once, then reused by every step that touches JOIN.
- 02
Pick JOIN
Type JOIN in the search box of the dialog, select it, then click Add connection. A new tab opens on the JOIN side. You need an existing JOIN account here; Zapier does not create one for you.
- 03
Sign in and grant access
Log in to JOIN in that tab and allow Zapier to reach the account. Anything you do not own yourself (a colleague's job, a shared pipeline) also needs read or write access on your side before a Zap can touch it.
Your first Zap: ping the team on every new applicant
GoalEach new application on a chosen job posts a short message in the hiring channel.
- 01
Create the Zap
In Zapier, start a new Zap and pick JOIN as the app that starts it. Choose Application Created as the event, then select the JOIN connection you added earlier.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent applications from your account, so you map fields on a real candidate rather than an empty placeholder.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field to check, the rule and the value. Keep in mind a filter turns this into a multi-step Zap, which needs a paid plan.
- 04
Add the message
Add the action step in your chat tool and map the candidate's name and the job from the trigger into the message text, so the team sees who applied and for what.
- 05
Test, then publish
Run each step once and read what came back. When the message looks right, click Publish to switch the Zap on. It only reacts to applications that arrive from then on.
JOIN triggers on Zapier
3 events start a Zap when something happens in JOIN, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
Application Created
Instant triggerIn Zapier“Triggers when a new application is created for a published job.”
Starts your Zap as soon as a candidate applies to one of your published job ads, and hands over that application so the next steps can use the candidate's details. This is the trigger most hiring teams build on first, because it turns every incoming applicant into something your other tools can react to.
Job Published
Instant triggerIn Zapier“Triggers when a new or existing job's status becomes online.”
Fires whenever a job ad goes online in JOIN, whether you just wrote it or you are bringing back an older one. The Zap receives the job so it can announce it, log it, or open a matching folder elsewhere. Think of it as the starting gun for everything that should happen when a role opens.
Job Unpublished
Instant triggerIn Zapier“Triggers when a job's status is changed to offline or archived.”
Reacts when an ad leaves the market, either switched offline or archived. The Zap gets the job that was taken down, which is handy for closing the loop in other tools instead of chasing stale listings by hand. It is the mirror of Job Published, and the two often live side by side.
JOIN actions on Zapier
JOIN gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Application
ActionIn Zapier“Creates a new application and assigns it to a specific job.”
Adds a candidate to a given job in JOIN, built from data another app collected. Four fields are mandatory: the candidate's email, first name, last name and the Job ID.
Update Job Status
ActionIn Zapier“Updates the job status to one of the following values: ONLINE, OFFLINE, or ARCHIVED.”
Switches a job ad to ONLINE, OFFLINE or ARCHIVED from outside JOIN. You give it the Job ID and the new status, and nothing else is needed.
JOIN searches on Zapier
2 search steps look for data that already exists in JOIN, so a later step can use it.
Both searches look up jobs by title, which is the easiest way to get a Job ID that no earlier step carried. You find them at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not a clean single match.
Get Jobs
SearchIn Zapier“Search for jobs by title”
Looks up jobs in your JOIN account by their title and hands what it found to the next steps. It is the step that feeds Create Application or Update Job Status when you only know the role's name.
Get Online Jobs
SearchIn Zapier“Search for online jobs by title”
Same lookup by title, limited to jobs currently live. That keeps closed or archived roles out of the answer, which matters when a candidate should only land on an open position.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap carries on without a result.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. Neither JOIN search offers it, so a missing job is never created by the Zap.
- If multiple search results are found?Several jobs match the title: keep the first one (the default), stop the Zap, or pass all of them along together.
When a JOIN Zap breaks
Zapier attaches no help article and no documented rate limit to JOIN.
The failures you will meet come from how Zapier works in general. Here are the cases worth knowing before you publish anything; our Zapier troubleshooting page goes further when one of them bites.
Old applicants never show up
A Zap only reacts to what happens after you switch it on. Candidates and jobs that already existed are ignored, and moving that backlog is a separate job.The Zap keeps setting itself off
Update Job Status inside a Zap started by Job Published or Job Unpublished writes where the trigger watches. It fires again and again and burns through your tasks.A bulk import gets held back
If a trigger suddenly sends a huge batch, after a migration or a mass import of jobs, Zapier's flood protection can hold it back.A search stops the Zap
Get Jobs or Get Online Jobs finds no title match and, with default settings, every step after it is skipped. Switch the setting on if empty results are normal.
Need help automating JOIN with Zapier?
A person reads every message.
