Process documents with Slack & Google Drive
Runs on a schedule across Slack, Google Drive and PostgreSQL, looks the answer up in a vector store, then parses the incoming file into rows. Built for summarization, around a "List Changed Docs (Google Drive)" step, in 17 documented nodes.
Process documents with Google Drive and PostgreSQL for your team. An original, ready-to-import n8n workflow built around the 'File Processing' pattern for legal & compliance. It runs on a schedule and orchestrates 17 nodes across Slack, Google Drive, PostgreSQL. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. What used to take a morning now runs on its own.
Key benefits
- ✓Keeps Slack and Google Drive in step for summarization, without anyone re-typing a row
- ✓Safe to re-run: records already in Slack or Google Drive are skipped, across all 17 nodes of this summarization build
- ✓A failed Slack or Google Drive call is retried rather than dropped, at any of the 17 nodes in this summarization build
- ✓Fans the same result out to PostgreSQL in the same run, for summarization
- ✓Summarization answers come from your indexed content, not model recall, before reaching Slack
Use cases
- →Teams keeping Slack and Google Drive aligned by hand for summarization
- →Answering summarization questions from your own indexed documents, then replying in Slack
- →Summarization work where "List Changed Docs (Google Drive)" is still a manual step before Slack
- →Summarization work that only reaches Slack on a schedule, when someone remembers to start it
Integrations
Workflow preview (17 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (17 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Advanced levelAdds branching depth and audit logging on top of the core pattern.
- •Downloading and parsing CSV, XLSX, or PDF into JSON items
- •Archiving the processed file
- •Moving data between Google Drive, PostgreSQL and Slack in a single run
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Slack, Google Drive, PostgreSQL). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Extract from uploaded files: Slack & Google Drive
Summarization on n8n: runs on a schedule across Slack, Google Drive and PostgreSQL, starting at "List Changed Docs (Google Drive)". Looks the answer up in a vector store. 18 documented nodes.
Extract from documents for summarization
Summarization on n8n: runs on a schedule across Slack, Google Drive and PostgreSQL, starting at "List Changed Docs (Google Drive)". Looks the answer up in a vector store. 16 documented nodes.
Parse receipts for summarization
Summarization on n8n: runs on a schedule across Slack, PostgreSQL and Google Drive, starting at "Export All Rows (PostgreSQL)". Branches on the check before anything is written. 18 documented nodes.
Parse receipts: Slack for summarization
Summarization on n8n: runs on a schedule across Slack, Google Sheets, PostgreSQL and Google Drive, starting at "Export All Rows (Google Sheets)". 22 documented nodes.