Jotform submission → its own Google Drive folder with every upload filed inside
Each application gets a Drive folder, the uploads inside it, and a row in the index sheet.
Each Jotform submission becomes its own Google Drive folder. Every uploaded file is saved inside under its original name, and a row in an index sheet links to the folder. The folder is named from the date, the applicant and the submission ID. Reviewers open Drive, not Jotform, and the documents sit where the rest of the team's files already live.
How it works
- Jf
Trigger
New form submission (Jotform webhook)
Jotform
- if
Step 1
Name the folder from the submission
Builds the folder name from the submission date, the name field you choose and Jotform's submission ID, so two applicants with the same name never collide.
- Dr
Step 2
Find or create the submission folder
Searches the parent folder for a folder with that exact name and creates one only if none exists, so a retried run reuses the same folder. Works on My Drive or a shared drive.
- Jf
Step 3
Download every uploaded file
Requests each file URL in the submission with your Jotform API key and keeps the original filename and MIME type. A submission with no uploads still gets a folder.
- Dr
Step 4
Upload the files into the folder
Writes each file into the submission folder as a binary upload, one file per Drive request, and returns the Drive file IDs.
- GS
Step 5
Add a row to the index sheet
Appends submission ID, form name, applicant, submitted time, file count and the folder link to a sheet the review team already watches.
What changes once it runs
- Every submission has a Drive folder within a minute of arriving, uploads included.
- Folder names carry the date, the applicant's name and the submission ID, so nothing collides.
- Files keep their original names and types. A PDF uploaded as a PDF is a PDF in Drive.
- Reviewers work from one index sheet with a link per submission.
- A submission with no attachments still gets a folder and a row, so the index is complete.
What you get
- n8n workflow export with the Jotform trigger and both Google connections wired
- Written guide to the Jotform API key, the Google OAuth consent screen and the parent folder
- Index-sheet template with the six columns the workflow writes
- A recorded walkthrough of the first run
- 30 days of email support for setup questions
Before you start
- Jotform account (the free plan works) with the form built and an API key created under Settings
- A Google account with edit rights to the parent folder, on My Drive or a shared drive
- One Google Sheet for the index; the template with the six columns is included
- n8n reachable from the internet so Jotform's webhook can deliver the submission
Built for
Questions before you buy
- Can it file to SharePoint or OneDrive instead of Google Drive?
- Yes. n8n has a Microsoft OneDrive node with the same create-folder and upload operations, and the guide includes the swap. The index sheet then moves to Excel Online or stays in Google Sheets, your choice.
- What happens if a download from Jotform fails?
- That submission's execution stops with the error attached and waits in n8n's executions list. Retry it once Jotform is reachable. Because the folder step searches by name first, the retry files into the folder already created rather than making a second one.
- Which name field goes into the folder name?
- You pick it in one expression at the top of the workflow; the default is the form's Full Name field. Forms without a name field can use the email address or the submission ID alone.
- Why n8n only, and not Make or Zapier?
- Jotform's file URLs need your API key to download, and that authenticated fetch is one node in n8n. Make and Zapier can do it with extra per-file handling. We have not packaged or tested those builds, so we do not list them.
- Are there limits on file size or API calls?
- Two apply. Jotform's free plan allows 1,000 API calls a day, and each uploaded file costs one call. File size is set by your Jotform plan and the upload field's own setting. On the n8n side the file passes through memory; for self-hosted instances that will receive large video files the guide names the setting to raise. PDFs, images and Word documents need no change.
Nearby on the shelf
Whole catalog- ShGSMade to order
Shopify product created or updated → one row per variant in Google Sheets
Your product sheet matches the Shopify store, one row per variant, minutes after an edit.
Data sync & backups$49 - GSDrGDDSMade to order
Google Sheets row → Google Docs contract → PDF → DocuSign envelope
One new row in a sheet becomes a filled contract, a PDF and a DocuSign envelope.
Documents & e-signature$199 - HMcMade to order
HubSpot contact created or changed → Mailchimp audience member kept in step
Marketing sends to the list HubSpot holds, and unsubscribes never get re-added.
Data sync & backups$99
