← All N8N workflows
Data & databasesCodeExtract From FileGoogle DriveHTTP RequestManual Trigger

google drive list files1 and executequery postgres and download google drive

Configured with Extract From File, Google Drive, HTTP Request, Postgres, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking TestworkflowManual TriggerFiles / mediaGoogle Drive - ListFiles1Google DriveData storeDelete old chunksPostgresFiles / mediaGoogle Drive - DownloadFile1Google DriveTransformExtract PDF TextExtract From FileCodeParse File to Text1CodeCodeChunk Text1CodeRoutingLoop Over ItemsLoop Over ItemsWeb / APIOllama - Embed Chunk1HTTP RequestCodeMerge Embedding +Metadata1CodeData storeSupabase - ReplaceChunk1Postgres

Node categories in this workflow

  • Trigger
  • Files / media
  • Data store
  • Transform
  • Code
  • Routing
  • Web / API

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking Test workflowTriggerManual TriggerSee node parameters
Google Drive - List Files1Files / mediaGoogle DrivefileFolder
Delete old chunksData storePostgresexecuteQuery
Google Drive - Download File1Files / mediaGoogle Drivedownload
Extract PDF TextTransformExtract From Filepdf
Parse File to Text1CodeCodeSee node parameters
Chunk Text1CodeCodeSee node parameters
Loop Over ItemsRoutingLoop Over ItemsSee node parameters
Ollama - Embed Chunk1Web / APIHTTP RequestPOST
Merge Embedding + Metadata1CodeCodeSee node parameters
Supabase - Replace Chunk1Data storePostgresexecuteQuery

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

  • googleDriveOAuth2Api
  • postgres

Workflow notes

google drive list files1 and executequery postgres and download google drive

google drive list files1 and executequery postgres and download google drive

Purpose and structure

This folder contains the google drive list files1 and executequery postgres and download google drive workflow. Its executable nodes use code, extractFromFile, googleDrive, httpRequest, manualTrigger, postgres, splitInBatches. 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 clicking Test workflow

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/TahsinTanni/RAG-slackbot/blob/f51615aee91eb029228fc0a9853df0ad2cd5d0b0/index.json MIT; preserve source notices.

More in Data & databases