Block 1 - Sticky Note: Ingestion
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
How the System Works This automation operates in three distinct phases: Ingestion , Storage , and Generation . Phase Component What Happens 1. The Trigger Google Drive Ever...
n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.vectorstoremongodbatlas, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.embeddingsgooglegemini, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.documentdefaultdataloader, n8n-nodes-base.googledrive, n8n-nodes-base.googledrivetrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Nitesh.
Original n8n.io sourceThis automation operates in three distinct phases: Ingestion, Storage, and Generation.
| Phase | Component | What Happens |
|---|---|---|
| 1. The Trigger | Google Drive | Every time you update your rag_posts.csv in your Drive folder, the system wakes up. |
| 2. The Brain | Gemini Embeddings | It turns your text into "Vectors" (numbers) so the AI understands the meaning of your writing style, not just the words. |
| 3. The Vault | MongoDB Atlas | Your posts are stored in a vector database, acting as a "Style Library" the AI can browse instantly. |
| 4. The Writer | AI Agents | When you ask for a post, the AI searches your vault, finds the best matches, and mimics the formatting exactly. |
rag_posts.csv.Post Text, Hook Type, Engagement, Category.n8n_rag_data.data_index.fileUpdated.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Generate LinkedIn posts using Google Gemini, MongoDB Atlas, Google Drive and Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 18 |
| Categories | Content Creation, AI RAG |
| Author | Nitesh |
| Published | 01 Mar 2026 |
Use the JSON export at /data/workflows/13782/13782.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How the System Works This automation operates in three distinct phases: Ingestion , Storage , and Generation . Phase Component What Happens 1. The Trigger Google Drive Ever...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, AI RAG use case.