Clone nested folder structures in Google Drive with custom naming

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Google Drive Nested Folder Structure Cloner How it works Takes any Google Drive folder structure and creates an exact copy with custom naming Perfect for agencies, consultants, or anyone who needs ...

Best for

File Management automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jagged Frontiersman.

Original n8n.io source

1.1 Workflow description

Title: Clone nested folder structures in Google Drive with custom naming
Workflow name: Clone nested folder structures in Google Drive with custom naming

Google Drive Nested Folder Structure Cloner

How it works

Takes any Google Drive folder structure and creates an exact copy with custom naming
Perfect for agencies, consultants, or anyone who needs identical folder structures for multiple projects
Creates folder hierarchy only (no files are copied)
Handles nested folders automatically with level-by-level processing

Set up steps

Get your source and destination folder IDs from Google Drive URLs
Edit the 3 variables in the CONFIG node (takes 30 seconds)
Connect your Google Drive credentials in n8n
Run the workflow and watch it create your folder structure
For deeply nested folders, run multiple times to process each level

What you'll need

Google Drive account with API access configured in n8n
Read permissions on source folder, write permissions on destination folder

Pro tips

Create a "Templates" folder in Google Drive for your reusable structures
The workflow intelligently skips folders that already exist
Each run processes the next level down for nested structures
Check the final report to see exactly what was created, skipped, or failed

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - When clicking "Test workflow"

Type / Role: n8n-nodes-base.manualTrigger - manualTrigger
Config choices: Version 1

Block 2 - ⚙️ CONFIG - Edit the 3 variables above

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 3 - 📁 Get All Folders

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 4 - 🔄 Process Folders

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 5 - 🔀 Should Create?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2

Block 6 - ✨ Create Folder

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 7 - 📊 Final Report

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 8 - README

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 9 - Config Help

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 10 - Processing Info

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 11 - Troubleshooting

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Clone nested folder structures in Google Drive with custom naming
Complexity	intermediate
Nodes	11
Categories	File Management
Author	Jagged Frontiersman
Published	23 May 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/4349/4349.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Download workflow JSON Original n8n.io source File Management workflows

Frequently asked questions

What does Clone nested folder structures in Google Drive with custom naming do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.

Jagged Frontiersman

1 workflow

Nodes

n8n-nodes-base.manualtrigger n8n-nodes-base.code n8n-nodes-base.httprequest n8n-nodes-base.if n8n-nodes-base.stickynote

Complexity

intermediate

Published 23 May 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/4349/4349.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Export WordPress data to a CSV file

## Quick Overview This workflow manually exports all records from a WordPress site, converts the returned JSON into a CSV file, and saves the CSV to disk on the n8n server. ## How it works 1. Starts when you manually click Execute in n8n. 2. Fetches all available items from your connected WordPress site via the WordPress API. 3. Converts the WordPress JSON response into a CSV file. 4. Writes the generated CSV to the n8n server as `data.csv`. ## Setup 1. Add WordPress API credentials in n8n (site URL, username, and an Application Password). 2. Choose the WordPress resource to export in the WordPress node and confirm the data shape matches what you want in the CSV. 3. Update the output file path/name in the file-writing step and ensure the target directory is writable on your n8n host (for example `/home/node/.n8n/data.csv`).

View

Aggregate shipment tracking statuses with FedEx, UPS and DHL

## Quick Overview This workflow runs every 15 minutes to fetch active shipments from an n8n Data Table, query FedEx, UPS, or DHL tracking APIs with circuit-breaker protection, normalize each response into a shared status schema, and upsert the latest status back into the same table. ## How it works 1. Runs every 15 minutes on a schedule. 2. Loads all rows from the n8n Data Table `shipment_tracking` and filters out shipments already marked as DELIVERED or RETURNED_TO_SENDER. 3. Routes each remaining shipment by `carrier` and marks unsupported carriers with a canonicalStatus of UNKNOWN. 4. For FedEx, UPS, and DHL shipments, checks a per-carrier circuit breaker and either calls the carrier’s tracking API or skips the call when the breaker is open. 5. Normalizes each carrier response (or skip) into a canonical status (for example PRE_TRANSIT, IN_TRANSIT, OUT_FOR_DELIVERY, DELIVERED, EXCEPTION, UNKNOWN) while updating the breaker state based on 429/5xx/network failures. 6. Merges all carrier results and upserts the latest fields back into the `shipment_tracking` Data Table using `trackingNumber` as the match key. ## Setup 1. Create the n8n Data Table named `shipment_tracking` with columns such as `trackingNumber`, `carrier`, `canonicalStatus`, `rawStatus`, `breakerState`, `httpStatus`, and `checkedAt`, and seed it with shipments (use lowercase carriers: `fedex`, `ups`, `dhl`). 2. Add OAuth2 credentials for the FedEx Track API and select them in the FedEx HTTP request step. 3. Add OAuth2 credentials for the UPS Track API and select them in the UPS HTTP request step. 4. Add DHL API authentication (as configured for the DHL request in this template) and select it in the DHL HTTP request step. 5. Activate the workflow so workflow static data persists between runs and the circuit breaker state is maintained.

View

Clean up watched Jellyfin media and completed torrents with Transmission

## Quick Overview This scheduled workflow cleans up watched media in Jellyfin and removes completed torrents from Transmission by calling both APIs, deleting played items in Jellyfin, refreshing the Jellyfin library, and deleting torrents (including local data) once they reach the completed status. ## How it works 1. Runs daily on a schedule at the configured hour. 2. Sets the Jellyfin base URL, Jellyfin user ID, and Transmission base URL used for subsequent API calls. 3. Fetches played Movies and Episodes from Jellyfin for the configured user, deletes each returned item, and triggers a Jellyfin library refresh. 4. Calls the Transmission RPC endpoint to retrieve the required X-Transmission-Session-Id, then re-requests the torrent list using that session header. 5. Splits the Transmission response into individual torrents, filters to those with status 6 (completed), and removes each matching torrent while also deleting its local data. ## Setup 1. Add Jellyfin HTTP Header Auth credentials (for example, an API key header) and fill in the Jellyfin server URL and target Jellyfin user ID in the Variables step. 2. Add Transmission Bearer Auth credentials and set your Transmission base URL in the Variables step. 3. Confirm your Transmission instance allows RPC access at `/transmission/rpc` and that your Jellyfin server exposes the `/Users/{userId}/Items`, `/Items/{id}`, and `/Library/Refresh` endpoints for the provided credentials.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Clone nested folder structures in Google Drive with custom naming

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Google Drive Nested Folder Structure Cloner

How it works

Set up steps

What you'll need

Pro tips

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - When clicking "Test workflow"

Block 2 - ⚙️ CONFIG - Edit the 3 variables above

Block 3 - 📁 Get All Folders

Block 4 - 🔄 Process Folders

Block 5 - 🔀 Should Create?

Block 6 - ✨ Create Folder

Block 7 - 📊 Final Report

Block 8 - README

Block 9 - Config Help

Block 10 - Processing Info

Block 11 - Troubleshooting

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions