Save every job application to a hiring folder

Every application becomes a candidate file in a shared OneDrive folder, named by role and ready for the hiring panel.

When this happens

New submission on your job application form

Do this

Create a text file for the candidate in an Applications folder in OneDrive, named with the applicant and the role

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

Hiring rarely happens in one place. The role is agreed in a meeting, the applications arrive by form, and the shortlist gets drawn up by three people who each need to read the same twelve candidates. A folder in OneDrive that fills itself keeps the panel looking at one copy.

This fits small hiring teams that already live in Microsoft 365 — an office manager, a practice lead, a founder doing their own recruiting. The folder opens on a laptop or a phone, and it sits next to the offer letters rather than in a separate system nobody remembers to check.

Setting it up

1
Publish the Job Application Form template so the careers link is live, and add a File Upload question for the CV — uploads take a file up to 2 MB, which covers a normal CV comfortably. Keep a URL question beside it for the candidate whose portfolio runs past that.
2
In Zapier, start a Zap with formformform as the trigger app, choose New Submission, and select the careers form.
3
Add OneDrive as the action app, pick Create New Text File, and connect the Microsoft account whose drive the hiring panel already shares.
4
Point the destination at /Applications, or at /Applications/Engineering if you keep a folder per department and each panel should open only its own.
5
Build the file name from Position Applied For and then Full Name, so every applicant for one role sits together when the folder sorts alphabetically.
6
Order the file body the way a reviewer reads: contact details at the top, then Relevant Skills, then Work Experience, with the Cover Letter last.
7
Share the /Applications folder with the hiring panel once in OneDrive, so each new file inherits the permission instead of needing its own invite.
8
Send a test application through the live form, open the file from a phone to check the layout held, then switch the Zap on.

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	OneDrive
Position Applied For	First part of the OneDrive file name, so one role's candidates group together
Full Name	Second part of the file name, after the role
Email Address	Contact block at the top of the text file
Relevant Skills	Body of the file, high up — the line a panel skims before anything else
Work Experience	Body of the file, under its own heading
Cover Letter	Last section of the file, where the longest answer does no harm

Variations worth knowing

One folder per open role

Put a Create Folder step ahead of the file step, named from Position Applied For, then write the candidate file inside it. Worth doing when several vacancies are open at once and each panel should see only its own shortlist rather than scrolling past every other role.

Tell the panel as each file lands

Add a Microsoft Teams or Outlook step after the OneDrive action, carrying Full Name, Position Applied For and a link to the new file. The panel gets the prompt in the channel they already watch instead of remembering to check the folder.

If something isn't arriving

Two candidates with the same name produce one file, or a numbered duplicate.

Add the Zapier submission time to the end of the file name. Position Applied For stays at the front so the folder still groups by role, and the timestamp makes each file unique without making the name unreadable.

The Cover Letter arrives as one unbroken block of text.

Line breaks from long-answer fields do not always survive the step. Put a short labelled heading above each section of the body so the file stays readable when the spacing collapses, or run the field through a Formatter step first.

Frequently asked questions

Can applicants upload their CV through the form?

Yes. Add a File Upload question and the CV arrives with the application, up to 2 MB per file — enough for almost any CV, though a designer's full portfolio will not fit. The file stays in formformform, where whoever owns the form downloads it from the submission; what the Zap writes into OneDrive is the text record of everything the candidate typed. If the document itself should sit in the hiring folder for a panel that has no formformform login, keep a URL question on the form and put that link in the file body.

Can the whole hiring panel see the folder without a Zapier account?

Yes. Zapier only needs the connection on the account that owns the drive. Share /Applications in OneDrive with the panel once and every file the Zap creates afterwards inherits that access, so reviewers open it like any other shared folder.

What happens to applications already sitting in my inbox?

The Zap only fires on new submissions, so it will not backfill anything received before you switched it on. Export the earlier responses from formformform and drop them into the same folder by hand once, then let the Zap take it from there.

Related automations

Create a project folder when a client signs on
Each new engagement gets a named OneDrive folder, the standard subfolders, and the scope written in before the kickoff call.
File each bug report where support can find it
Each bug report becomes a file in a OneDrive support folder, ordered by severity and carrying the screenshot link.
File every completed waiver in one audit folder
Each completed waiver lands as a dated record in a restricted OneDrive folder, ready for the day someone asks for it.
File every contest entry for the judging panel
Each entry becomes a file in its category folder in OneDrive, so the judging panel opens a sorted set rather than an inbox.
Keep a text-file archive of every business inquiry
Every inquiry is written to a dated text file in OneDrive, giving you a searchable second copy of the response.
Append every support request to a running log
Every help desk submission appends a line to one shared Dropbox text file, so the team reads the day's requests in order.

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