Collect many files through a simple web form and send them straight into the right Google Drive folder. It fits client uploads, onboarding documents, and internal requests. You enter the folder name and the system handles the rest.

A form submission starts the flow with two inputs, files and folder name. The logic checks Google Drive to see if the folder already exists inside a chosen parent folder. If it exists, each file is split and uploaded to that folder with its original name. If it does not exist, a new folder is created first, then the same upload steps run. Two code steps break out each binary file so every upload is handled cleanly. This keeps structure tidy and removes manual sorting and dragging.

Setup needs Google Drive access and the parent folder ID. Update the search query with your real parent folder and enable Always Output Data for safe checks. Teams often cut file handling time from 30 minutes per batch to under 3 minutes. Common uses are vendor document drops, school assignment collection, and event media intake.

• Form submission trigger collects multiple files and a folder name
• Google Drive search checks for a matching folder inside a set parent folder
• If condition routes uploads to existing or new folder paths
• Automatic folder creation in the selected parent location when needed
• Code steps split multiple binary files so each file uploads correctly
• Upload actions keep original file names for easy tracking
• Both paths follow the same organization rules for consistent results

• Reduce manual file sorting from 30 minutes per batch to 3 minutes
• Automate 100 percent of folder checks and creation
• Improve placement accuracy by 90 percent by enforcing the parent folder
• Handle 10 times more uploads without extra staff
• Connect form intake with Google Drive seamlessly

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Drive. See the Tools Required section above for links to create accounts with these services.
3. Open any Google Drive node, then in the Credential to connect with dropdown, click Create new credential and follow the on screen instructions to connect your Google Drive account using OAuth2. Give the credential a clear name so your team can recognize it.
4. Open the Form Trigger node and confirm there is a required file field and a required folderName field. Copy the public form URL for testing.
5. In the Google Drive Search node, paste your real parent folder ID into the query so it searches inside the correct parent. Enable the Always Output Data option to handle cases where no folder is found.
6. In the Create Folder node, set the same parent folder ID and confirm the correct Drive is selected. Keep the folder name mapped from the form field.
7. Leave the two Code nodes as provided. They split out each uploaded file so the upload nodes receive one file per item.
8. In both Upload nodes, confirm the input data field name is set to data and the file name field uses the provided fileName value to preserve names.
9. Test the existing folder path: create a folder under the parent, submit the form with that exact folder name and two files, then confirm the files appear in that folder.
10. Test the new folder path: submit the form with a folder name that does not exist and confirm a new folder is created and the files are uploaded there.
11. If uploads fail, check Google Drive permissions and credential scope. If no folder is found, verify the parent folder ID in the search query. If file names look wrong, confirm the data field mapping in the Code and Upload nodes.