AI-powered file management automation for Google Drive with MCP

Name: AI-powered file management automation for Google Drive with MCP
Availability: InStock
Author: David Olusola

AI-powered file management automation for Google Drive with MCP preview

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.

Overview

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

📁 Google Drive MCP Workflow – AI-Powered File Management Automation 🚀

🧠 Overview

A secure and intelligent n8n workflow that connects with Google Drive via MCP (Model Control Protocol). Ideal for AI agent tasks, compliance-driven storage, and document automation.

🌟 Key Features

🔒 Built-In Safety

Backs up files before edits (timestamped) Supports rollback using file history Validates file size, type, and permissions 📁 Smart Organization

Automatically converts file types (PDF, DOCX, etc.) Moves files to structured folders Auto-archives old files based on age or rules

🔄 MCP Integration

Accepts standardized JSON via webhook Real-time execution for AI agents Fully customizable input (action, fileId, format, etc.)

✅ AI Callable MCP Actions

These are the commands AI agents can perform via MCP:

Download a file (with optional format conversion) Upload a new file to Google Drive Copy a file for backup Move a file to a specific folder Archive old or inactive files Organize documents into folders Convert files to a new format (PDF, DOCX, etc.) Retrieve and review file history for rollback 📝 Example Input { "action": "download", "fileId": "abc123", "folderPath": "/projects/clientA", "convertFormat": "pdf" }

🔐 Security & Performance

OAuth2 secured access to Google Drive API No sensitive data stored in transit Real-time audit logs and alerts Batch-friendly with built-in rate limiting 📌 Ideal For Businesses automating file management AI Agents retrieving, sorting, converting, or archiving files Compliance teams needing file versioning and backups ⚙️ Requirements n8n + Google Drive API v3 MCP server + Webhook integration Google OAuth2 Credentials

David Olusola

92 workflows

Nodes

@n8n/n8n-nodes-langchain.mcptrigger n8n-nodes-base.googledrivetool n8n-nodes-base.stickynote

Complexity

intermediate

Published 28 Jun 2025

Likes 0

View on n8n.io Download Workflow

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

Share Your Workflow

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

Submit Your Template How to Submit

Related Workflows

Organize and back up n8n workflows to Google Drive as consolidated JSON

## WORKFLOW INTRODUCTION This automation organizes and consolidates your n8n workflows into categorized JSON files (Active, Template, Done, Archived) and uploads them directly to a Google Drive folder. It is designed to help users manage large instances by creating organized, human-readable backups. ## HOW IT WORKS * **API Connection:** Connects to your n8n instance using the internal API. * **Categorization:** Groups workflows by status and tags. * **WIP Logic:** Any workflow without a specific status or tag is automatically routed to a work-in-progress consolidation file. * **Cloud & Self-Hosted Ready:** Works for both n8n Cloud and self-hosted instances. ## WORKFLOW PROCESS OVERVIEW Fetch -> Filter -> Convert -> Upload -> Wait 5 seconds See below for a full breakdown. ------------------------------ ## USAGE GUIDE & SETUP 1. This workflow is dependent on the n8n internal statuses of Active and Archived, and the tags "Template" and "Done". 2. Anything that is not Active, Archived, or labeled Template or Done, is considered a work-in-progress by default. 3. To make this workflow work for you please tag your templates as Template, and your completed projects as Done. ## PRE-REQS A pre-designated Google Drive folder (and its ID) for housing the folders and files created by this workflow ## REQUIRED CREDENTIALS 1. Google Drive account 2. N8N account > N8N API Key ## THE CONFIGURATION NODE 1. Input the ID of your pre-designated Google Drive folder 2. Input the base URL of your N8N instance (e.g. https://subdomain.app.n8n.cloud, https://n8n.domain.com, http://localhost:5678) 2a. Do **NOT** include anything after the ".cloud", ".com", or the ":5678" ## API KEY INSTRUCTIONS How to get: Settings -> API -> Create API Key -> Name it -> Copy it _**Note: Copy the API key and save it somewhere secure. You won't be able to see it again!!**_ How to use (Two Methods): **Note: The node is set up for Method 2 by default** **Method 1 (Quick Start-Direct Insertion)**. In the Workflows node: - Authentication: None - Send Headers: on - Name: X-N8N-API-KEY - Value: [YOUR N8N API KEY] -**Note:** Queries and Body are not needed for this method._ **Method 2 (Best Practice-N8N Credential)**. In the Workflows node: - Authentication: Generic Credential Type - Generic Auth Type: Header Auth - Header Auth: Select "Create new credential" (**NOTE:** If you already have a Header Auth for your N8N API key select it here) 2a. In the credential creation area: - Name: X-N8N-API-KEY - Value: [YOUR N8N API KEY] _**Note:** Queries, Header, and Body are not needed for this method._ ------------------------------ ## WORKFLOW PROCESS BREAKDOWN (after configuration) 1. Creates a Google Drive folder to house the resulting files 2. Grabs your workflows from the public API 3. Splits out the workflows into individual items for easier processing 4. Filters out the Active workflows (True: a-d; False: Go to 5) 4a. Sorts the active workflows by name 4b. Converts the active workflows into a single JSON file 4c. Uploads the active JSON file to the folder created in Step 1. 4d. Wait 5 seconds to avoid errors caused by the Google spam upload detector 5. Filters out the Not Archived workflows (True: Go to 6; False: a-d) 5a. Sorts the archived workflows by name 5b. Converts the archived workflows into a single JSON file 5c. Uploads the archived JSON file to the folder created in Step 1. 5d. Wait 5 seconds to avoid errors caused by the Google spam upload detector 6. Filters out the workflows tagged "Template" (True: a-d; False: Go to 7) 6a. Sorts the template workflows by name 6b. Converts the template workflows into a single JSON file 6c. Uploads the template JSON file to the folder created in Step 1. 6d. Wait 5 seconds to avoid errors caused by the Google spam upload detector 7. Filters out the workflows tagged "Done" (True: a-d; False: e-g) 7a. Sorts the done workflows by name 7b. Converts the done workflows into a single JSON file 7c. Uploads the done JSON file to the folder created in Step 1. 7d. Wait 5 seconds to avoid errors caused by the Google spam upload detector 7e. Sorts the work-in-progress workflows by name 7f. Converts the work-in-progress workflows into a single JSON file 7g. Uploads the work0in-progress JSON file to the folder created in Step 1. 7h. Wait 5 seconds to avoid errors caused by the Google spam upload detector ------------------------------ ## LIMITATIONS 1. N8N Cloud users on a trial account cannot generate or use the N8N API key. 2. If you use Method 1 (Direct Insertion) in the API Key Instructions your API Key will not be listed as connected to this workflow if you use my [Workflow Credentials Auditor](https://n8n.io/workflows/14423). Same goes for all other credentials directly inserted into a HTTP Request node. ------------------------------ ## ALTERNATIVE VERSIONS AND CUSTOM BUILDS While this version focuses on global status tagging using **Google Drive**, I have developed a parallel version for **Github Repository** storage. * **Need the Github Version?** I provide the standard Workflow Organizer Consolidated Github version free upon request. ![Caption: Preview the Github storage version.](https://github.com/zianamitchell/n8n-workflow-images/blob/main/n8n-workflow-organizer-consolidated-github.png?raw=1) * **Want to backup workflows without consolidating them?** I offer the standard **Workflow Organizer** free upon request for both Google Drive and GitHub. - **Note:** The Google Drive version is meant to work in tandem with this **Workflow Organizer Consolidated Google Drive**. They should be linked to the same parent folder. * **Need a Custom build?** If you require advanced logic (e.g. client-specific routing, multi-tier tagging, unique project tagging, integration with other platforms), I offer custom automation services tailored to your business needs. A custom version of this workflow or the Github version is $15. Contact me here: [email protected]

View

Organize and back up n8n workflows to Google Drive folders

## WORKFLOW INTRODUCTION This automation organizes your n8n workflows files into categorizes (Active, Template, Done, Archived) and uploads them directly to a categorized Google Drive folders. It is designed to help users manage large instances by creating organized, human-readable backups. ## HOW IT WORKS * **API Connection:** Connects to your n8n instance using the internal API. * **Categorization:** Groups workflows by status and tags. * **WIP Logic:** Any workflow without a specific status or tag is automatically routed to a work-in-progress folder. * **Cloud & Self-Hosted Ready:** Works for both n8n Cloud and self-hosted instances. ## WORKFLOW PROCESS OVERVIEW Fetch -> Filter -> Convert -> Start Loop -> Create Category Folder -> Upload -> Wait 5 seconds -> Return to loop for next upload batch See below for a full breakdown. ------------------------------ ## USAGE GUIDE & SETUP 1. This workflow is dependent on the n8n internal statuses of Active and Archived, and the custom tags "Template" and "Done". 2. Anything that is not Active, Archived, or labeled Template or Done, is considered a work-in-progress by default. 3. To make this workflow work for you please tag your templates as Template, and your completed projects as Done. 3a. Finished templates should not be labelled done, as per best practice they have placeholder text and no real data is processed by them ## PRE-REQS A pre-designated Google Drive parent folder (and its ID) for housing the folders and files created by this workflow ## REQUIRED CREDENTIALS 1. Google Drive account 2. N8N account > N8N API Key ## THE CONFIGURATION NODE 1. Input the ID of your pre-designated Google Drive parent folder 2. Input the base URL of your N8N instance (e.g. https://subdomain.app.n8n.cloud, https://n8n.domain.com, http://localhost:5678) 2a. Do **NOT** include anything after the ".cloud", ".com", or the ":5678" ## API KEY INSTRUCTIONS How to get: Settings -> API -> Create API Key -> Name it -> Copy it _**Note: Copy the API key and save it somewhere secure. You won't be able to see it again!!**_ How to use (Two Methods): **Note: The node is set up for Method 2 by default** **Method 1 (Quick Start-Direct Insertion)**. In the Workflows node: - Authentication: None - Send Headers: on - Name: X-N8N-API-KEY - Value: [YOUR N8N API KEY] -**Note:** Queries and Body are not needed for this method._ **Method 2 (Best Practice-N8N Credential)**. In the Workflows node: - Authentication: Generic Credential Type - Generic Auth Type: Header Auth - Header Auth: Select "Create new credential" (**NOTE:** If you already have a Header Auth for your N8N API key select it here) 2a. In the credential creation area: - Name: X-N8N-API-KEY - Value: [YOUR N8N API KEY] _**Note:** Queries, Headers, and Body are not needed for this method._ ------------------------------ ## WORKFLOW PROCESS BREAKDOWN (after configuration) 1. Creates a Google Drive folder to house the resulting files 2. Grabs your workflows from the public API 3. Splits out the workflows into individual items for easier processing 4. Filters out the Active workflows (True: a-f; False: Go to 5) 4a. Sorts the active workflows by name 4b. Converts the active workflows into individual JSON files 4c. Loops through the JSON files, uploading them in batches of 5 4d, Creates the active-backups folder once 4e. Uploads the JSON files to the folder created in Step 4d. 4f. Wait 5 seconds to avoid errors caused by the Google spam upload detector 5. Filters out the Not Archived workflows (True: Go to 6; False: a-f) 5a. Sorts the archived workflows by name 5b. Converts the archived workflows into individual JSON files 5c. Loop through the JSON files, uploading them in batches of 5 5d, Create the archived-backups folder once 5e. Uploads the JSON files to the folder created in Step 5d. 5f. Wait 5 seconds to avoid errors caused by the Google spam upload detector 6. Filters out the workflows tagged "Template" (True: a-f; False: Go to 7) 6a. Sorts the template workflows by name 6b. Converts the template workflows into individual JSON files 6c. Loop through the JSON files, uploading them in batches of 5 6d, Create the template-backups folder once 6e. Uploads the JSON files to the folder created in Step 6d. 6f. Wait 5 seconds to avoid errors caused by the Google spam upload detector 7. Filters out the workflows tagged "Done" (True: a-f; False: g-l) 7a. Sorts the done workflows by name 7b. Converts the done workflows into individual JSON files 7c. Loops through the JSON files, uploading them in batches of 5 7d, Creates the done-backups folder once 7e. Uploads the JSON files to the folder created in Step 7d. 7f. Wait 5 seconds to avoid errors caused by the Google spam upload detector 7g. Sorts the work-in-progress workflows by name 7h. Converts the work-in-progress workflows into individual JSON files 7i. Loops through the JSON files, uploading them in batches of 5 7j. Creates the wip-backups folder once 7k. Uploads the JSON files to the folder created in Step 7j. 7l. Wait 5 seconds to avoid errors caused by the Google spam upload detector ------------------------------ ## LIMITATIONS 1. N8N Cloud users on a trial account cannot generate or use the N8N API key. 2. If you use Method 1 (Direct Insertion) in the API Key Instructions your API Key will not be listed as connected to this workflow if you use my [Workflow Credentials Auditor](https://n8n.io/workflows/14423). Same goes for all other credentials directly inserted into a HTTP Request node. ------------------------------ ## ALTERNATIVE VERSIONS AND CUSTOM BUILDS While this version focuses on global status tagging using **Google Drive**, I have developed a parallel version for **Github Repository** storage. * **Need the Github Version?** I provide the standard Workflow Organizer Github version free upon request. ![Caption: Preview the Github storage version.](https://github.com/zianamitchell/n8n-workflow-images/blob/main/n8n-workflow-organizer-github.png?raw=1) * **Want to consolidate workflows before backing them up?** I offer the standard **Workflow Organizer Consolidated** free upon request for both Google Drive and GitHub. - **Note:** The Google Driver version is meant to be used in tandem with this **Workflow Organizer Google Drive**. They should be linked to the same parent folder. * **Need a Custom build?** If you require advanced logic (e.g. client-specific routing, multi-tier tagging, unique project tagging, integration with other platforms), I offer custom automation services tailored to your business needs. A custom version of this workflow or the Github version is $15. Contact me here: [email protected]

View

Upload images to Webflow via API as a reusable sub-workflow

Uploading an image to Webflow's Asset Manager through the API is surprisingly complex. It requires computing an MD5 hash, announcing the file to Webflow, then uploading the binary to Amazon S3 with specific headers. This template wraps that entire process into a clean, reusable sub-workflow you can call from any main workflow. ## How it works - **Sub-workflow trigger** receives `imageData` (binary), `fileName`, and `wfSiteId`. - **MD5 hash computation** generates the file hash that Webflow's API requires. - **First HTTP node** (POST to Webflow's `/v2/sites/:site_id/assets`) announces the file and returns an S3 upload URL along with required upload details (credentials, policy, signature). - **Second HTTP node** (POST to the S3 upload URL) sends the binary file as a multipart form request using the upload details from the previous step. - **Set node** extracts and returns `originalFileName`, `fileId`, and `assetUrl` to the calling workflow. ## How to use 1. **Import** this template as a workflow in your n8n instance. 2. **Set up Webflow credentials**: Create a Bearer Auth credential with your Webflow API token. The token must have the `assets:write` scope. 3. **Call this workflow as a sub-workflow** from your main workflow using the Execute Workflow node. 4. **Provide the required inputs:** - `imageData`: The binary image data - `fileName`: File name including extension (max 100 characters) - `wfSiteId`: Your Webflow site ID 5. **Use the output**: The sub-workflow returns `originalFileName`, `fileId`, and `assetUrl`, which you can then use in subsequent steps (e.g., updating a CMS item, sending a notification, etc.). ## Requirements - **Webflow** account with API access, Bearer Auth credential with `assets:write` scope ## Notes & customization - **Upload to a specific folder:** Webflow's API accepts an optional `parentFolder` parameter in the first request. If you want to upload into a specific folder in the Asset Manager, add the folder ID to the body of the first HTTP node. - **Other file types:** While this template is designed for images, Webflow's Asset API may accept other file types (e.g., videos, PDFs). The upload mechanism is the same, so worth testing if your use case requires it. - **CMS integration:** A natural next step after uploading is attaching the asset to a CMS collection item. This is a single additional HTTP request in your main workflow using the returned `assetUrl` and the relevant collection/item IDs. - **File name limit:** Webflow requires file names under 100 characters including the extension. Consider adding validation in your calling workflow if file names come from user input.

View

Need Custom Automation?

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

AI-powered file management automation for Google Drive with MCP

Workflow preview

Important notice

Overview

📁 Google Drive MCP Workflow – AI-Powered File Management Automation 🚀

🧠 Overview

🌟 Key Features

🔄 MCP Integration

✅ AI Callable MCP Actions

🔐 Security & Performance