Google Drive folder templates, cloned clean every time
You copy a “template” folder in Google Drive… and suddenly you’ve duplicated old files, outdated docs, and random clutter you didn’t want in the new project. Now you’re deleting things, second-guessing what to keep, and hoping you didn’t miss anything important.
This kind of Drive folder cloning problem hits marketing managers launching campaigns, agency owners spinning up client workspaces, and ops folks trying to keep internal projects consistent. You want the same structure every time. Just the folders. Clean.
This workflow clones a Google Drive folder structure without copying files, and it skips folders that already exist. You’ll see how it works, what you need, and where teams usually trip up.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Drive folder templates, cloned clean every time
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Get_Folders_SOURCE", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "EDIT_THIS_NODE", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Create Folder", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Check if folder exists"]
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If exists", pos: "b", h: 48 }
n7@{ icon: "mdi:cog", form: "rounded", label: "Get_Folders_DESTINATION", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Destination Names", pos: "b", h: 48 }
n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge_Folder_Context"]
n6 --> n4
n4 --> n2
n3 --> n7
n3 --> n9
n2 --> n5
n1 --> n2
n9 --> n8
n8 --> n1
n5 --> n6
n7 --> n9
n0 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n6 decision
class n5 code
classDef customIcon fill:none,stroke:none
class n5,n9 customIcon
The Problem: Folder templates that copy the wrong stuff
Google Drive makes it easy to duplicate folders. Too easy, honestly. When you copy a “Client Template” or “Campaign Template,” Drive happily pulls along everything inside, including last quarter’s assets, old briefs, and files someone forgot to remove. Then you spend your first hour “starting” a project doing housekeeping. The bigger issue is consistency: if every new folder starts with a slightly different cleanup, your team’s structure drifts, people can’t find things, and handoffs get messy.
The friction compounds. Here’s where it usually breaks down.
- Copying template folders duplicates outdated files, which turns a clean kickoff into a cleanup job.
- Small differences in folder naming stack up, so reports and assets end up scattered.
- Manual setup takes about 15–30 minutes per client or campaign, and it’s easy to miss one required folder.
- People reuse “whatever worked last time,” so your template quietly stops being the template.
The Solution: Clone only the folder structure (not the files)
This n8n workflow clones the folder names from a source Google Drive folder into a destination folder, without copying any files. You set a source folder ID (your template) and a destination folder ID (where new projects should live). The workflow pulls the list of folders from the template, checks what already exists in the destination, and creates only what’s missing. That means you can safely run it more than once without creating duplicates. In practice, it gives you a “folder blueprint” you can reuse for every new client or campaign, while keeping the destination clean and current.
The workflow starts with a manual run inside n8n after you paste in the source and destination IDs. It gathers the destination folder names, then loops through the template folders and creates new ones only when needed. When it finishes, your destination matches the template structure, minus the baggage.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your client template has 25 folders (Brief, Creative, Reporting, Invoices, and so on). Manually, creating and naming those folders takes maybe 1 minute each once you include checking, fixing typos, and reordering, so you’re at about 25 minutes per client. With this workflow, you paste the source and destination IDs, hit run, and let it create what’s missing; the “human time” is closer to 2 minutes. If you onboard 10 clients in a month, that’s roughly 4 hours you don’t spend doing folder admin.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Drive as the source and destination storage.
- Google Drive API credentials to let n8n read and create folders.
- Source and destination folder IDs (copy them from the Drive folder URL).
Skill level: Beginner. You’ll paste folder IDs, connect Google Drive once, then run the workflow.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You start the run manually in n8n. This workflow is designed for “I need this folder structure now” moments, like a new client kickoff or a new internal project.
The workflow reads your inputs and gathers context. It takes the source folder ID (template) and destination folder ID, then pulls the destination’s existing folder list so it knows what’s already there.
It loops through the template folders and checks for matches. n8n processes the template folders in batches, verifies whether each folder already exists in the destination, and only then decides to create it.
New folders are created in Google Drive. When a folder is missing, the workflow creates it and continues until the destination has the same top-level structure as the template.
You can easily modify the source template to support different client types based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the workflow entry point so you can run the folder copy process on demand.
- Add or open Manual Start Trigger as the trigger node for the workflow.
- Leave the default settings as-is since this trigger runs manually with no parameters required.
- Confirm Manual Start Trigger is connected to Map Source Inputs.
Step 2: Connect Google Drive
These nodes interact with Google Drive and require valid credentials to list and create folders.
- Open Retrieve Source Folders and connect Google Drive access.
- Open Retrieve Target Folders and connect the same Google Drive access.
- Open Generate Folder and connect Google Drive access for folder creation.
Credential Required: Connect your Google Drive credentials
⚠️ Common Pitfall: None of the Google Drive nodes have credentials configured in the workflow. You must add Google Drive credentials to Retrieve Source Folders, Retrieve Target Folders, and Generate Folder before testing.
Step 3: Set Up Source-to-Target Context Mapping
These nodes prepare and merge the source and target folder context used throughout the flow.
- Open Map Source Inputs and define the fields you want to pass into the workflow (e.g., source folder ID, target parent ID).
- Confirm that Map Source Inputs outputs to both Retrieve Target Folders and Combine Folder Context in parallel.
- Open Combine Folder Context and ensure it merges the outputs from Map Source Inputs and Retrieve Target Folders.
- Open Assign Target Names and define how target folder names should be mapped or constructed from the merged context.
Tip: The parallel branch from Map Source Inputs ensures target data and context are prepared at the same time, which reduces latency before Assign Target Names runs.
Step 4: Configure Folder Retrieval, Iteration, and Creation
These nodes list source folders, iterate through items, verify existence, and create folders as needed.
- Open Retrieve Source Folders and configure it to list the source folder structure you want to copy.
- Open Iterate Folder Items and configure batch settings if you need controlled processing of large folder sets.
- Open Verify Folder Presence and implement logic to check whether a target folder already exists.
- Open Conditional Exists Check and define the condition that routes to Generate Folder when a folder is missing.
- Open Generate Folder and configure the folder creation details that use the mapped names from Assign Target Names.
Tip: The flow uses Iterate Folder Items to feed items into Verify Folder Presence, which then routes to Conditional Exists Check before creating folders.
Step 5: Test and Activate Your Workflow
Validate that the folder structure copies correctly before enabling the workflow in production.
- Click Execute Workflow to run the flow manually via Manual Start Trigger.
- Verify that Retrieve Source Folders lists the expected folders and Retrieve Target Folders returns the target structure.
- Confirm that Conditional Exists Check routes missing folders to Generate Folder and that new folders are created correctly.
- Once successful, toggle the workflow to Active for ongoing use.
⚠️ Common Pitfall: If you see empty outputs, check that Map Source Inputs includes all required IDs and names used by downstream Google Drive nodes.
Common Gotchas
- Google Drive credentials can expire or need specific permissions. If things break, check the Google Drive credential in n8n (and the connected Google account’s access to both folders) first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 20 minutes if your Google Drive connection is ready.
No coding required. You’ll mainly connect Google Drive and paste in the two folder IDs.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need Google Drive API access (usually free for normal usage).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but not with the workflow as-is. Right now it clones top-level folders only; to support nested folders you’d extend the “Retrieve Source Folders” logic to also fetch each folder’s children, then loop and create them under the right parent in “Generate Folder.” Common customizations include adding a recursion layer for subfolders, writing a simple run log to a file or Google Sheet, and adding a toggle that turns nested cloning on or off.
Usually it’s expired or mis-scoped Google credentials in n8n. Reconnect Google Drive, then confirm the same account can access both the source and destination folders (especially on Shared Drives). If it still fails, the folder ID is often the culprit, so grab it again from the Drive URL and re-paste it into the input node.
A few hundred top-level folders is fine for most setups, and batching helps it stay stable.
Often, yes. Zapier and Make can create folders, but this workflow benefits from n8n’s stronger control flow (looping, merging, and conditional checks) without turning it into an expensive multi-step scenario. Self-hosting also matters here because onboarding seasons can spike runs, and you don’t want pricing to dictate your process. The main tradeoff is setup: n8n asks for a bit more ownership up front. If you want help picking the right approach, Talk to an automation expert.
Once this is in place, new Drive workspaces start clean and stay consistent. The workflow handles the repetitive folder setup so you can get on with the actual work.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
