Block 1 - Main Overview
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Stop manually creating folder structures for every new client or project. This workflow provides a simple form where users enter a name, and automatically duplicates your template folder structure ...
n8n-nodes-base.stickynote, n8n-nodes-base.formtrigger, n8n-nodes-base.googledrive, n8n-nodes-base.wait, n8n-nodes-base.httprequest
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Antonio Gasso.
Original n8n.io sourceStop manually creating folder structures for every new client or project. This workflow provides a simple form where users enter a name, and automatically duplicates your template folder structure in Google Drive—replacing all placeholders with the submitted name.
{{NAME}} placeholders in files and folder names{{NAME}} everywhere{{NAME}} as placeholderStep 1: Create your template folder
📁 {{NAME}} - Project Files
├── 📁 01. {{NAME}} - Documents
├── 📁 02. {{NAME}} - Assets
├── 📁 03. Deliverables
└── 📄 {{NAME}} - Brief.gdoc
Step 2: Deploy Apps Script
Me | Access: AnyoneStep 3: Configure workflow Replace these placeholders:
DESTINATION_PARENT_FOLDER_ID — Where new folders are createdYOUR_APPS_SCRIPT_URL — URL from Step 2YOUR_TEMPLATE_FOLDER_ID — Folder to duplicateStep 4: Test Activate workflow → Open form URL → Submit a name → Check Drive!
function doPost(e) {
try {
var params = e.parameter;
var templateFolderId = params.templateFolderId;
var name = params.name;
var destinationFolderId = params.destinationFolderId;
if (!templateFolderId || !name) {
return jsonResponse({
success: false,
error: 'Missing required parameters: templateFolderId and name are required'
});
}
var templateFolder = DriveApp.getFolderById(templateFolderId);
if (destinationFolderId) {
var destinationFolder = DriveApp.getFolderById(destinationFolderId);
copyContentsRecursively(templateFolder, destinationFolder, name);
return jsonResponse({
success: true,
id: destinationFolder.getId(),
url: destinationFolder.getUrl(),
name: destinationFolder.getName(),
mode: 'copied_to_existing',
timestamp: new Date().toISOString()
});
} else {
var parentFolder = templateFolder.getParents().next();
var newFolderName = replacePlaceholders(templateFolder.getName(), name);
var newFolder = parentFolder.createFolder(newFolderName);
copyContentsRecursively(templateFolder, newFolder, name);
return jsonResponse({
success: true,
id: newFolder.getId(),
url: newFolder.getUrl(),
name: newFolder.getName(),
mode: 'created_new',
timestamp: new Date().toISOString()
});
}
} catch (error) {
return jsonResponse({
success: false,
error: error.toString()
});
}
}
function replacePlaceholders(text, name) {
var result = text;
result = result.replace(/\{\{NAME\}\}/g, name);
result = result.replace(/\{\{name\}\}/g, name.toLowerCase());
result = result.replace(/\{\{Name\}\}/g, name);
return result;
}
function copyContentsRecursively(sourceFolder, destinationFolder, name) {
var files = sourceFolder.getFiles();
while (files.hasNext()) {
try {
var file = files.next();
var newFileName = replacePlaceholders(file.getName(), name);
file.makeCopy(newFileName, destinationFolder);
Utilities.sleep(150);
} catch (error) {
Logger.log('Error copying file: ' + error.toString());
}
}
var subfolders = sourceFolder.getFolders();
while (subfolders.hasNext()) {
try {
var subfolder = subfolders.next();
var newSubfolderName = replacePlaceholders(subfolder.getName(), name);
var newSubfolder = destinationFolder.createFolder(newSubfolderName);
Utilities.sleep(200);
copyContentsRecursively(subfolder, newSubfolder, name);
} catch (error) {
Logger.log('Error copying subfolder: ' + error.toString());
}
}
}
function jsonResponse(data) {
return ContentService
.createTextOutput(JSON.stringify(data))
.setMimeType(ContentService.MimeType.JSON);
}
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Template-based Google Drive folder generation with Forms and Apps Script |
|---|---|
| Complexity | intermediate |
| Nodes | 9 |
| Categories | File Management |
| Author | Antonio Gasso |
| Published | 10 Dec 2025 |
Use the JSON export at /data/workflows/11663/11663.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Stop manually creating folder structures for every new client or project. This workflow provides a simple form where users enter a name, and automatically duplicates your template folder structure ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.