Reset Postgres Tables & Download Google Drive Docs in n8n

Reset your PostgreSQL tables and queue Google Drive docs for download in n8n

This n8n workflow clears specific PostgreSQL tables (so you start fresh) and then scans a designated Google Drive folder to download each document by file ID—ready for your downstream processing.

What this workflow does

Built for clean re-runs and repeatable document ingestion, the workflow performs these steps:

• Deletes existing PostgreSQL vector data by removing the n8n_vectors table (in the public schema) to clear previously stored vector records.
• Clears previous scrape results by deleting the scraped_pages table (in public) so old page data doesn’t carry over.
• Scans a specific Google Drive folder and returns each file’s ID, name, and webViewLink.
• Downloads each Google Drive document using its file ID so the files can be used in subsequent steps.

Use cases

• Re-ingesting a content library: when your Google Drive folder changes and you want a clean refresh of stored results.
• Recovering from partial runs: if a previous n8n run was interrupted, reset the PostgreSQL state and re-download documents.
• Periodic maintenance for SaaS operators managing document ingestion pipelines and avoiding stale data.

Technical details

• PostgreSQL: requires credentials with permission to delete tables; targets public.n8n_vectors and public.scraped_pages.
• Google Drive: OAuth2 connection to list files in a folder and download documents by file ID.
• Workflow logic / nodes: uses if, set, code, html, filter, and switch to control execution and prepare data for downstream steps.

Setup checklist

• Confirm your PostgreSQL environment matches the public.n8n_vectors and public.scraped_pages tables.
• Add a Google Drive OAuth2 connection with access to the target folder and its files.
• Update the Google Drive folder URL/ID in the folder scan step to point to your source directory.