Google Drive Automation
Configured with Agent, Chat Trigger, Document Default Data Loader, Embeddings Google Gemini, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- AI & models
- Trigger
- Files / media
- Transform
- Data store
- Code
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 |
|---|---|---|---|
| AI Agent | AI & models | Agent | See node parameters |
| Monitor Google Drive for New Files | Trigger | Google Drive Trigger | See node parameters |
| Download File from Google Drive | Files / media | Google Drive | download |
| Extract PDF Content | Transform | Extract From File | |
| Insert Document into Pinecone Vector Store | Data store | Vector Store Pinecone | See node parameters |
| Generate Document Embeddings (Google Gemini) | AI & models | Embeddings Google Gemini | See node parameters |
| Clean and Normalize PDF Text | Code | Code | See node parameters |
| Load Document Data for Processing | Files / media | Document Default Data Loader | See node parameters |
| Split Document Text into Chunks | Transform | Text Splitter Recursive Character Text Splitter | See node parameters |
| Chat Message Trigger | Trigger | Chat Trigger | See node parameters |
| Retrieve Relevant Documents from Pinecone | Data store | Vector Store Pinecone | See node parameters |
| Generate Query Embeddings (Google Gemini) | AI & models | Embeddings Google Gemini | See node parameters |
| Generate Chat Prompt with Context | Code | Code | See node parameters |
| OpenRouter Chat Model Interface | AI & models | LM Chat Open Router | See node parameters |
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
googleDriveOAuth2ApigooglePalmApiopenRouterApipineconeApi
Workflow notes
Google Drive Automation
Google Drive Automation
Purpose and structure
This folder contains the Google Drive Automation workflow. Its executable nodes use agent, chatTrigger, code, documentDefaultDataLoader, embeddingsGoogleGemini, extractFromFile, googleDrive, googleDriveTrigger, lmChatOpenRouter, textSplitterRecursiveCharacterTextSplitter, vectorStorePinecone. 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
Monitor Google Drive for New Files, Chat Message Trigger
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/Code/1906_Code_Extractfromfile_Automate_Triggered.json MIT; preserve source notices.