Log new applicants in your Notion hiring pipeline
Each application arrives in your Notion candidates database as an Applied card, with the role and available start date already on it.
New submission on your "Apply now" form
Create a page in your Candidates database with the applicant's name, the role applied for, their available start date, and a Stage of "Applied"
One-directional. A submission triggers the action — nothing is written back into your form.
Hiring in Notion works when every applicant is a page from the start. This flow creates that page as the application is submitted, tagged Applied and dropped into the first column of the pipeline, so the review queue is the database rather than someone's inbox.
Recruiters and hiring managers running a small process without an applicant tracking system use it. One database per role, or one with a Role select and a view per stage, and the whole shortlist can be moved along by dragging cards.
Setting it up
- 1
Publish the application form with Position Applied For as a select listing only the roles you are hiring for right now. Free text here turns into a messy Role property later.
- 2
In Notion, build the Candidates database with a Name title, a Role select matching those positions, a Stage select that starts at Applied, and a date property for the start date.
- 3
In Zapier, pick formformform, choose the New Submission trigger, and select the application form. Submit a test application so the sample data includes a real date.
- 4
Add Notion's "Create Database Item" action and choose the Candidates database.
- 5
Map Full Name to the title and Position Applied For to the Role select, then set Stage to "Applied" as a fixed value nobody has to think about.
- 6
Map Available Start Date into the date property and check the format Zapier is sending. If the page shows an empty date, reformat the value first with a Zapier Formatter step.
- 7
Put Cover Letter into the page body so a reviewer reads the whole application inside the candidate page instead of squinting at a property.
- 8
Turn the Zap on and confirm the card lands in the Applied view of the board rather than an unsorted default view.
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 | Notion |
|---|---|
| Full Name | Name title of the candidate page |
| Email Address | Email property |
| Position Applied For | Role select |
| Employment Type | Employment Type select |
| Available Start Date | Start date property |
| Cover Letter | Page body of the candidate page |
Variations worth knowing
Add a Zapier filter on Position Applied For and give each role its own Create Database Item step. Hiring managers then open one database and see only their own shortlist, without anyone building a filtered view for every vacancy.
Once Available Start Date is a real date property rather than text, a Notion view can sort by it. A role that needs cover in three weeks surfaces the people who can actually start in three weeks, ahead of the rest of the pile.
If something isn't arriving
Notion expects an ISO-style date. Insert a Zapier Formatter step between the trigger and the action, convert the answer to YYYY-MM-DD, and map the formatter output into Notion instead of the raw form value.
A Notion select only accepts options it already knows about. If a vacancy was added to the form but not to the Role property, the value is dropped. Add the option in Notion first, then replay the affected tasks from Zapier's history.
Frequently asked questions
Can a candidate see where they are in the pipeline?
No. The flow only creates the page, nothing is written back to the form, and applicants have no access to the database. If you want people kept informed, send an update from your mail tool as you move a card between stages.
How do we get a portfolio link onto the candidate page?
Add a URL question to the application form for a portfolio or LinkedIn address, then map it to a URL property in Notion. Reviewers open it from the candidate page, in the same place as the rest of the application.
Does someone who applies for two roles create two candidate pages?
Yes. Every submission creates its own page, which is usually what you want, since the two applications are separate. Group the database by email address if you want repeat applicants to sit next to each other during review.
Related automations
- 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 your Notion guest list from event RSVPs
Every registration adds a guest to your Notion attendees database, with ticket type, party size and dietary notes attached.
- File survey feedback in your Notion research database
Each survey response becomes a tagged entry in your Notion research database, ready to group by theme during planning.
- Queue new orders in your Notion operations database
Each order request opens as a To do card in your Notion Orders database, with the product and quantity ready to pick.
- Turn problem reports into open tickets in Notion
Each problem report opens as a ticket in your Notion support board, already carrying a priority and the steps to reproduce.
- 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.
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