Let only qualifying applications reach the hiring manager
A Filter step checks location and hours first, so only qualifying applications create a candidate record and reach the hiring manager.
New Submission on your Careers application form
Add a Zapier Filter so only applicants who meet the criteria continue, then create a candidate record and email the hiring manager
One-directional. A submission triggers the action — nothing is written back into your form.
Most roles collect more applications than the person hiring can read in a week. Half of them are outside the commute radius or wrong for the level advertised, and the hiring manager still opens each one to find that out.
A Filter step sits between the form and everything downstream. Applications that fail the location or hours test stop there: no record, no email, nothing added to the tracker. Recruiters turn this on for high-volume roles where the first screen is the same two questions every time.
Setting it up
- 1
Publish the careers form with Position Applied For as a choice list rather than free text. One Zap per role becomes unmanageable once you are hiring for five.
- 2
In Zapier, add formformform's New Submission trigger, select the careers form, and pull in a test application that would pass your criteria.
- 3
Add a Filter as the second step, before any action. Everything after it runs only when the filter passes.
- 4
Set the first condition on City, State. Contains your metro area is more forgiving than an exact match, which fails on abbreviations and spelling.
- 5
Add a second condition on Employment Type, joined with AND, so someone wanting part-time hours on a full-time requisition also stops here.
- 6
After the filter, add your applicant tracker action to create the candidate record, mapping Position Applied For to the open requisition.
- 7
Add the email step last, addressed to the hiring manager, with the candidate's name in the subject and the skills answer in the body.
- 8
Send one application that should pass and one that should not, then read the Zap history. A filtered run shows as stopped, which is the result you want.
What maps where
Using the Job Application Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Zapier |
|---|---|
| City, State | First filter condition — a wrong location stops the run before anything is created |
| Employment Type | Second filter condition, matched against the hours the requisition actually offers |
| Full Name | Candidate name on the tracker record and the subject line of the manager's email |
| Email Address | Candidate email on the record, and the reply-to on the notification |
| Position Applied For | The requisition the candidate record is filed against |
| Relevant Skills | Body of the hiring manager's email, so the first read happens in the inbox |
Variations worth knowing
A filtered run leaves nothing outside Zapier's history. If you need the full applicant pool for reporting, add a spreadsheet step before the Filter that logs every application, and let the Filter guard only the tracker and the email.
When several roles share the form, add a third condition on Position Applied For and duplicate the Zap for each open role. Each copy then filters to its own requisition and emails its own hiring manager, with no routing logic in the middle.
If something isn't arriving
The conditions are too narrow, or joined with AND where you meant OR. Open a stopped run in Zapier's history — it shows the value the filter tested — and loosen whichever condition is rejecting everyone, usually the location text.
A blank answer passes a does-not-contain condition, because there is nothing to contain. Make the questions you filter on required in the form, or add an exists condition ahead of the real test.
Frequently asked questions
Is filtering an application the same as rejecting it?
No. The filter only decides whether the rest of the Zap runs. The submission is still in formformform with every answer intact, so you can search the responses later and pull out anyone the criteria turned out to be too strict for.
Can the hiring manager's decision update the application?
No. Nothing travels back from Zapier into the form. The decision belongs in your tracker, where the candidate record lives, and the form response stays as the read-only account of what the applicant actually sent.
Should I filter on education or experience?
Filter on what a recruiter would check without reading the application, which is usually location or the hours on offer. Experience answers are free text and vary too much for a reliable match, so they read better in the manager's email than in a condition.
Related automations
- Log every feedback score, then follow up a day later
Formatter cleans the rating into a number, the row lands in your analysis sheet, and a Delay sends the follow-up email a day later.
- Put each RSVP on the calendar and on the reminder list
Guests who say yes get a calendar invite and a place on the reminder list from the same Zap, with no spreadsheet export in between.
- Send one demo request to your CRM, sheet and Slack
A single demo request creates a CRM contact, adds a row to the reporting sheet and posts to the sales channel in one multi-step Zap.
- Split urgent support requests into their own queue
A Path reads the priority answer and raises an escalated help desk ticket for urgent submissions, a standard one for everything else.
- Turn each order into an invoice and a confirmation email
Each order submission drafts an invoice in your billing app and sends the buyer a confirmation, so fulfilment and accounts stay level.
- Confirm event sign-ups and log the attendee
A registration becomes a calendar entry, a confirmation email and an attendee row, all from one scenario run.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free