Add job applicants to a hiring pipeline

Each application becomes a Candidates record with role, start date and stage, ready to drag through a kanban view.

When this happens

New form submission

Do this

Create a record in the Candidates table of an applicant-tracking base

One-directional. A submission triggers the action — nothing is written back into your form.

Applications arrive in bursts and go stale fast. Sending each one straight into the Candidates table of an applicant-tracking base means the recruiter opens Airtable rather than a mailbox, and every candidate already carries the role they applied for.

Small hiring teams use this when a single role is being advertised across several channels at once. A Stage single-select turns the table into a kanban view, so a candidate moves from Applied to Screening without anyone retyping a name, and the source answer shows which channel is actually producing applicants.

Setting it up

1
Publish one careers form covering every open role, with Position Applied For as a select listing each vacancy by its exact title.
2
Add a File Upload field for the CV, and keep a short URL question beside it for a portfolio or a shared folder of work samples — the ceiling is 2 MB per file, which a PDF CV clears easily and a design portfolio does not.
3
In your hiring base, give the Candidates table a Stage single-select starting at Applied, plus a Role single-select whose options match the Position Applied For choices exactly.
4
In Zapier, set formformform as the trigger app, pick New Submission, choose the careers form, and load a sample application.
5
Add the Airtable Create Record action and point it at the hiring base and the Candidates table.
6
Map Full Name to the primary field, Email Address and Phone Number to their columns, and Position Applied For to the Role single-select.
7
Type Applied into the Stage field in the Zap so every candidate enters the board in the same lane, and leave the Recruiter collaborator field empty.
8
Map Work Experience and Cover Letter into long text columns and the portfolio link into a URL column. The CV upload comes through as a reference to the stored file rather than the file itself, so give it a plain text column and open the CV from the response in formformform. Run a test application, then switch the Zap on once the card shows up in the Applied lane.

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	Airtable
Full Name	Primary field of the Candidates table
Email Address	Email column
Position Applied For	Role single-select
Available Start Date	Available From date column
How Did You Hear About This Position?	Source single-select
Cover Letter	Cover Letter long text column

Variations worth knowing

Link candidates to the vacancy they applied for

Keep an Openings table holding the role, hiring manager and closing date, and change Role on Candidates to a link-to-record field pointing at it. Applications then roll up per vacancy, so you can see that one opening has forty candidates and another has three without counting rows yourself.

Give each role its own board

One Candidates table with views filtered by Role beats a table per vacancy. The Zap stays as it is, the kanban stacks by Stage, and a view per opening gives each hiring manager a board of their own. Closing a role means archiving a view rather than migrating records between tables.

If something isn't arriving

Available Start Date arrives as text and cannot be sorted.

An Airtable date column rejects an unparseable string and stores nothing, while a text column keeps whatever was typed. Add a Zapier Formatter step set to Date / Time to convert the answer before it reaches Airtable, and choose a date question on the form rather than a free-text one.

Cover letters appear truncated in the grid.

Grid view shows one line of a long text field by default; the full text is usually there. Expand a record to check before assuming data was lost. If the text really is cut, the column is single line text and needs changing to Long text.

Frequently asked questions

Can applicants attach a CV to the form?

Yes. Add a File Upload field to the careers form and the CV is uploaded from the applicant's browser and stored with their response, where only you can open it. Two things shape how you use it: the limit is 2 MB per file, which a PDF CV clears easily, and what reaches Zapier is a reference to the stored file rather than the file itself, so the Candidates record points back to the response rather than carrying the CV as an Airtable attachment. Keep a URL question beside the upload for anything larger — a portfolio site, a full-resolution reel, a shared folder of work samples — and map that answer to a URL column in Candidates so it opens straight from the record.

What if someone applies for two different roles?

Each submission creates its own Candidates record, so you get one row per application rather than one per person. That keeps the stages independent. If you want a single view of the person, link both rows to a shared People table on email address.

Does moving a candidate to Rejected send them anything?

Not by itself, and nothing is written back to the form. Set up an Airtable automation on the Stage column if you want a rejection email, and keep the wording there — the Zap in this recipe only ever runs from form to base.

Related automations

Capture demo requests as leads in a CRM base
Every demo request becomes a Leads record with name, company, work email and source, ready for an owner and a status.
Collect event RSVPs as attendee records
Each RSVP becomes an Attendees record with guest count and dietary notes, stamped with the event date.
Log every support request as a new ticket record
Each help desk submission opens a Tickets record with priority, description and requester email, its status already set to New.
Store product feedback with a rating for triage
Every response lands in a Feedback record with the rating, the product and the verbatim comment, ready to group by theme.
Turn pre-orders into linked records in an inventory base
Every pre-order writes an Orders record with quantity and customer details, linked to the matching product row.
Add every inbound enquiry to your Notion leads database
Every business enquiry lands in your Notion Leads database as a page tagged New, with the company and inquiry type already filled in.

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