Save every job application as a candidate file
Every careers form submission writes a candidate file into a shared Dropbox Applicants folder, named for the role and the applicant.
New submission on your job application form
Create a text file in a Dropbox Applicants folder, named after the candidate and the role
One-directional. A submission triggers the action — nothing is written back into your form.
Recruiters lose applications in email. A shortlisting conversation starts with someone forwarding a thread, and the version in one inbox is not the version in another. Writing each application into Dropbox as it arrives gives the hiring panel one folder to open.
This suits small teams hiring for a handful of roles at once — an office manager, a founder, an HR lead of one — who want the paperwork in the same shared drive as the offer letters and the interview notes, without paying for an applicant tracking system.
Setting it up
- 1
Publish the Job Application Form template so it is live at its own link, and add a File Upload field so candidates attach the CV itself — each file can be up to 2 MB, which covers a CV comfortably. Add a URL field beside it for anything bigger: a portfolio site, a design folio, a shared folder of work samples.
- 2
In Zapier, create a Zap with formformform as the trigger app and pick the New Submission trigger.
- 3
Connect your formformform account and select the careers form as the trigger form.
- 4
Add Dropbox as the action app and choose Create Text File, then connect the Dropbox account the hiring team already shares.
- 5
Set the destination folder to /Applicants, or to /Applicants/2026 if you hire in cycles and want each year kept apart.
- 6
Build the file name from Position Applied For and then Full Name, so the folder sorts by role: 'Warehouse Supervisor — Dana Okafor.txt'.
- 7
Lay the body out in reading order — contact details first, then Work Experience, Relevant Skills and Cover Letter, each under its own heading — and put the CV field on its own line near the top, where a text action renders it as a link to the uploaded file.
- 8
Add a Dropbox Upload File step after the text file if you want the CV saved into /Applicants rather than linked from it, mapping the upload field into the step's file input and reusing the candidate and role for the file name.
- 9
Send a test application through the live form, check the file lands in /Applicants with the right name, 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 | Dropbox |
|---|---|
| Position Applied For | First half of the Dropbox file name, so applications group by role |
| Full Name | Second half of the file name |
| Email Address | Contact line at the top of the file body |
| Work Experience | Body of the text file, under an experience heading |
| Cover Letter | Body of the text file, below the experience section |
| Available Start Date | Body of the text file, next to the contact details |
Variations worth knowing
Add a Dropbox Create Folder step before the file step and name it from Position Applied For. Every application for that vacancy then lands in one place, and closing the role becomes a matter of archiving a single folder rather than picking files out of a list.
Use a Zapier filter on How Did You Hear About This Position? so referred candidates write into /Applicants/Referrals. Referral schemes usually carry a bonus, and keeping those applications apart makes the payout list straightforward to check at the end of the quarter.
If something isn't arriving
Dropbox keeps one file per path, so identical names collide. Add the submission timestamp or the Available Start Date to the file name; every application then gets its own file even when two applicants share a name.
Check the Zapier mapping rather than the form. A long-answer field passes through whole, but a formatter step with a character limit will cut it. Remove the limit, run the test again, and open the file in Dropbox to confirm the full text is there.
Frequently asked questions
Can candidates attach a CV to the form?
Yes. Add a File Upload field and applicants attach the CV as they apply, up to 2 MB per file — enough for a document, not for a design portfolio. What reaches Dropbox depends on the action you map it into: the Create Text File step writes a link to the upload alongside the rest of the application, while a Dropbox Upload File step takes the file itself and saves it into /Applicants. Keep a URL field as well for the work that will not fit in 2 MB, so a portfolio or a shared folder still travels with the application.
Does hiring progress in Dropbox flow back to the form?
No. The connection runs one way: a submission triggers an action in Dropbox. Renaming a file, moving it to a shortlist folder or deleting it changes nothing in formformform, and the original response stays in your responses view.
Will the whole hiring team see the applications?
They see whatever the Dropbox folder is shared with. The Zap writes as the connected account, so point it at a team folder rather than a personal one, and manage access in Dropbox exactly as you would for any other shared folder.
Related automations
- 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.
- Collect vendor artwork details into the event folder
Vendor registrations write a per-vendor record into the event's Dropbox folder, with booth details and a link to their artwork.
- Create a project folder when a new client onboards
A completed onboarding form creates a Dropbox folder named for the client and project, ready before the first call.
- File every property disclosure as a written record
Each completed property disclosure writes a dated text record into the Dropbox folder for that address.
- Keep a text-file archive of every contact submission
Each contact form response becomes a timestamped text file in Dropbox, giving you a plain-text backup you can search and keep.
- Archive every submission as a dated text file
Each submission becomes a dated text file in one shared Drive folder, readable by anyone with access to it.
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