Ninehire Zapier integrationAutomate Ninehire with Zapier.
The Ninehire Zapier integration gives you 1 trigger, 1 action and 0 searches. One trigger watches for new applicants, one action adds or updates an applicant. Small, but enough to move candidates in and out of your hiring pipeline. Here is how each works and what it costs.
Verified Trustpilot reviews · AI, automation & growth agency
What the Ninehire Zapier integration does for your hiring
Ninehire is a collaborative recruiting tool where a team manages its open positions and the people who apply. Connected to Zapier, it can tell your other apps about each new applicant, and it can receive applicants that come from somewhere else, without anyone retyping them.
A shared view of new applicants. Add Applicant picks up each applicant added to a recruitment you chose, so a spreadsheet, a chat channel or a board outside Ninehire stays in step with the pipeline.
Applicants that arrive on their own. Upsert Applicant in Ninehire takes a person collected by another app and puts them into a recruitment. If someone with that email is already in it, the action updates their additional questions instead of creating a second record.
One place for every source. Put the two together across separate Zaps and Ninehire becomes the place where applicants land, while the rest of your tools hear about them.
What Zapier does not do here: there is no search step, so a Zap cannot look up an applicant before acting, and there is no action to move, reject or delete one. Those stay in Ninehire. The only trigger checks on a timer rather than instantly.
If you are new to building Zaps, see our Zapier training page.
Zapier words in one minute
Seven terms are enough to follow the rest of this page, even if you have never opened Zapier.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new applicant in Ninehire.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like adding an applicant.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the ones it has not seen.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. Ninehire has none: its only trigger is a polling one.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
What a Ninehire Zap costs you
Ninehire is not a premium app, so it runs on Zapier's free plan. The trigger never costs a task, and the checks Zapier makes for new applicants are free too, however often they happen.
- Trigger and checksFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Filter or second actionMulti-step Zap, paid plan
Each action that succeeds counts as one task; one that fails does not. The free plan gives you 100 tasks a month and Zaps of two steps, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks for new applicants on each plan. On paid plans you can change that interval, and run a check by hand from the editor.
Connect your Ninehire account to Zapier
- 01
Open the connection dialog
In Zapier, open the Apps page of your account and click + Add connection. A connection is your Ninehire account linked once, then reused by every step that uses Ninehire.
- 02
Find Ninehire
Search for Ninehire in the dialog, select it and click Add connection. You need an account on Ninehire, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 03
Sign in and grant access
A tab opens on Ninehire. Sign in there and grant Zapier access to the account. The connection then serves the trigger and the action in any of your Zaps.
Your first Ninehire Zap: tell the team about the right applicants
GoalWhen a new applicant lands in a Ninehire recruitment and meets your condition, a message goes out in your team chat.
- 01
Create the Zap and set the trigger
Start a new Zap, pick Ninehire and
Add Applicant, choose your connection, then the Company and the ongoing Recruitment to watch. - 02
Test the trigger
Run the test. Zapier brings back the three most recent applicants of that recruitment, so you build the next steps on a real one. Read which details come back.
- 03
Add a filter
Add a Filter step and set its three boxes: the field to look at, the rule, the value, picked from what the test returned. A filter needs a paid plan.
- 04
Add the message
Choose your chat tool and its send-message action. Drop the applicant details you saw at test into the text, then test the step once and check the message.
- 05
Publish
Click Publish to switch the Zap on. Zapier then checks for new applicants at your plan's interval. Applicants added before publishing are not sent.
The Ninehire trigger in Zapier
1 event starts a Zap when something happens in Ninehire. Zapier checks for them at the interval your plan allows.
Add Applicant
Polling triggerIn Zapier“Triggers when a new applicant added”
Starts your Zap each time a new applicant is added to the recruitment you picked. You choose a Company, then one Recruitment, and the Zap only watches that one.
The Ninehire action in Zapier
Ninehire gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Upsert Applicant in Ninehire
ActionIn Zapier“Find applicants with your recruitment ID and email, and if there are applicants, proceed with additional question updates, and if there are no applicants, register a new one.”
Adds a person to a Ninehire recruitment, or updates them if they are already there. It looks for an applicant with the same recruitment and email; if it finds one, it updates the additional questions, otherwise it registers a new applicant.
When a Ninehire Zap breaks
Zapier attaches no help article to Ninehire, so the cases below are the general limits of any Zap, applied to this app.
Go through them before you publish. If one of them shows up, open our Zapier troubleshooting guide.
Earlier applicants are not picked up
A Zap only reacts to what happens after you switch it on. Applicants already in the recruitment are not sent, and moving them is a separate job.A Zap that keeps setting itself off
A Zap that writes into the place its own trigger watches can start itself again and again and burn tasks. Keep what the trigger watches apart from what the action writes.A big batch after an import
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.The same applicant, only once
Zapier keeps track of what it has already seen on a polling trigger, so the same applicant does not start the Zap twice.
Need help automating Ninehire with Zapier?
A person reads every message.
