Automate Google Forms File Uploads: Move and Rename in Drive

Introduction

Google Forms is a powerful way to collect data, and its file‑upload feature makes it easy for respondents to share documents, images, or spreadsheets directly from their devices. However, every uploaded file lands in a single, automatically generated folder inside the form owner’s Google Drive, which quickly becomes chaotic as responses grow. Organizing these files into dedicated folders—and even renaming them based on the information submitted in the form—can save countless hours of manual sorting and improve collaboration across teams. In this article we will explore a step‑by‑step method that uses Google Apps Script to move uploaded files to specific Drive folders, apply meaningful names derived from form answers, and automate the whole workflow so it runs seamlessly every time a new response is received.

Why the Default Upload Behavior Limits Organization

When a respondent uploads a file, Google Forms creates a hidden folder named after the form and stores every file there, regardless of the respondent’s identity or the purpose of the upload. This default setup has several drawbacks:

• Hard to locate specific files – you must search by file name or date, which is inefficient.
• No contextual naming – the original file name remains unchanged, even if it lacks relevant details.
• Permission management becomes cumbersome – all files share the same access settings, making selective sharing difficult.

By moving files to structured sub‑folders and renaming them with data from the form (e.g., “John_Doe_Invoice_2024.pdf”), you create a self‑documenting repository that scales with the volume of responses.

Setting Up the Destination Folder Structure

Before writing any code, decide how you want the files to be organized. A common approach is to create a root folder for the form and then generate sub‑folders based on a key response such as a user’s name, department, or project code. Follow these steps:

1. Open Google Drive and create a master folder (e.g., “Form Uploads – 2024”).
2. Note the folder’s ID from the URL; you will need it in the script (the string after /folders/).
3. If you prefer dynamic sub‑folders, plan the naming convention (e.g., {Department}_{Month}) and ensure the script can parse the required fields from the form response.
4. Set appropriate sharing permissions on the master folder so that collaborators can view or edit the files as needed.

Having a clear folder hierarchy in place simplifies the script logic and reduces the risk of misplaced files.

Creating an Apps Script to Move and Rename Files

The core of the solution is a Google Apps Script bound to the spreadsheet that stores the form responses. The script will:

• Identify the newly submitted row.
• Extract the file ID(s) from the “File Upload” column.
• Generate a new file name using other response columns.
• Move the file to the target folder (creating a sub‑folder if necessary).

Below is a concise example you can paste into the script editor (Extensions → Apps Script):

function onFormSubmit(e) {
  const sheet = e.range.getSheet();
  const row = e.range.getRow();
  const headers = sheet.getRange(1, 1, 1, sheet.getLastColumn()).getValues()[0];
  
  // Adjust these indices to match your form fields
  const fileCol = headers.indexOf('File Upload') + 1;
  const nameCol = headers.indexOf('Full Name') + 1;
  const deptCol = headers.indexOf('Department') + 1;
  
  const fileUrls = sheet.getRange(row, fileCol).getValue().toString().split(', ');
  const fullName = sheet.getRange(row, nameCol).getValue().replace(/\s+/g, '_');
  const department = sheet.getRange(row, deptCol).getValue().replace(/\s+/g, '_');
  
  const rootFolder = DriveApp.getFolderById('YOUR_MASTER_FOLDER_ID');
  const targetFolder = getOrCreateFolder(rootFolder, department);
  
  fileUrls.forEach(url => {
    const fileId = url.match(/[-\w]{25,}/)[0];
    const file = DriveApp.getFileById(fileId);
    const extension = file.getName().split('.').pop();
    const newName = `${fullName}_${department}.${extension}`;
    
    file.setName(newName);
    targetFolder.addFile(file);
    DriveApp.getRootFolder().removeFile(file); // Remove from the default upload folder
  });
}

function getOrCreateFolder(parent, name) {
  const folders = parent.getFoldersByName(name);
  return folders.hasNext() ? folders.next() : parent.createFolder(name);
}

Replace YOUR_MASTER_FOLDER_ID with the ID you recorded earlier. The script extracts the file ID from the URL, builds a new name (e.g., “John_Doe_Sales.pdf”), moves the file to the appropriate department folder, and removes it from the default upload location.

Automating the Process with Triggers and Testing

To ensure the script runs automatically whenever a respondent submits the form, set up an installable trigger:

1. In the Apps Script editor, click the clock icon (Triggers).
2. Select Add Trigger, choose the onFormSubmit function, set the event source to From spreadsheet, and the event type to On form submit.
3. Save the trigger; you may be prompted to authorize the script to access your Drive and Spreadsheet.

After the trigger is active, perform a few test submissions:

• Upload a small file and fill in the required fields.
• Check the master folder to confirm the file appears in the correct sub‑folder with the new name.
• Review the response sheet to ensure no extra data was added or altered.

If something goes wrong, use Logger.log() statements inside the script and view the logs via View → Logs**. Common issues include missing column headers, incorrect folder IDs, or insufficient Drive permissions.