Always Authenticate Your Server!
Configured with Execute Workflow Trigger, Extract From File, Google Drive, Google Drive Tool, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Files / media
- Routing
- Transform
- Subworkflow
- AI & models
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When Executed by Another Workflow | Trigger | Execute Workflow Trigger | See node parameters |
| Google Drive MCP Server | Trigger | Mcp Trigger | See node parameters |
| Download File1 | Files / media | Google Drive | download |
| FileType | Routing | Switch | See node parameters |
| Operation | Routing | Switch | See node parameters |
| Extract from PDF | Transform | Extract From File | |
| Extract from CSV | Transform | Extract From File | See node parameters |
| Get PDF Response | Transform | Edit Fields | See node parameters |
| Get CSV Response | Transform | Edit Fields | See node parameters |
| Read File From GDrive | Subworkflow | Tool Workflow | See node parameters |
| Search Files from Gdrive | Files / media | Google Drive Tool | fileFolder |
| Analyse Image | AI & models | Open Ai | image / analyze |
| Transcribe Audio | AI & models | Open Ai | audio / transcribe |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDriveOAuth2ApiopenAiApi
Workflow notes
1. Set up an MCP Server Trigger
1. Set up an MCP Server Trigger
Always Authenticate Your Server!
Always Authenticate Your Server!
Before going to production, it's always advised to enable authentication on your MCP server trigger.
2. Handle Multiple Binary Formats via Conversion and AI
2. Handle Multiple Binary Formats via Conversion and AI
Read more about the PostgreSQL Node
MCP clients (or rather, the AI agents) still expect and require text responses from our MCP server. N8N can provide the right conversion tools to parse most text formats such as PDF, CSV and XML. For images, audio and video, consider using multimodal LLMs to describe or transcribe the file instead.
Try It Out!
Try It Out!
This n8n demonstrates how to build a simple Google Drive MCP server to search and get contents of files from Google Drive.
This MCP example is based off an official MCP reference implementation which can be found here -https://github.com/modelcontextprotocol/servers/tree/main/src/gdrive
How it works
- A MCP server trigger is used and connected to 1x Google Drive tool and 1x Custom Workflow tool.
- The Google Drive tool is set to perform a search on files within our Google Drive folder.
- The Custom Workflow tool downloads target files found in our drive and converts the binaries to their text representation. Eg. PDFs have only their text contents extracted and returned to the MCP client.
How to use
- This Google Drive MCP server allows any compatible MCP client to manage a person or shared Google Drive. Simple select a drive or for better control, specify a folder within the drive to scope the operations to.
- Connect your MCP client by following the n8n guidelines here - https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/#integrating-with-claude-desktop
- Try the following queries in your MCP client:
- "Please help me search for last month's expense reports."
- "What does the company policy document say about cancellations and refunds?"
Requirements
- Google Drive for documents.
- OpenAI for image and audio understanding.
- MCP Client or Agent for usage such as Claude Desktop - https://claude.ai/download
Customising this workflow
- Add additional capabilities such as renaming, moving and/or deleting files.
- Remember to set the MCP server to require credentials before going to production and sharing this MCP server with others!
Always Authenticate Your Server!
Always Authenticate Your Server!
Purpose and structure
This folder contains the Always Authenticate Your Server! workflow. Its executable nodes use executeWorkflowTrigger, extractFromFile, googleDrive, googleDriveTool, mcpTrigger, openAi, set, switch, toolWorkflow. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When Executed by Another Workflow, Google Drive MCP Server
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Googledrivetool/0875_Googledrivetool_Extractfromfile_Import_Triggered.json MIT; preserve source notices.