Manage Gemini File Search RAG Stores with n8n Form

Manage Gemini File Search RAG stores end-to-end—upload documents from an n8n Form and query via an Agents tool

This n8n workflow lets you create, manage, and query Google Gemini File Search (RAG) stores, while ingesting documents through an n8n Form that uploads files to the Google Generative Language API for indexing.

What this workflow does

• Receives tool calls from an n8n Chat Agent with inputs such as action, storeName, documentName, query, and force.
• Normalizes and routes requests to the correct operation: list stores, create a new store, get store status, run a grounded query against a selected store, list documents, delete a document, or delete a store.
• Connects to Google Generative Language API to:
  • list/create fileSearchStore resources,
  • fetch store status,
  • execute Gemini grounded queries against a chosen store.
• Manages documents by listing documents in a store or deleting a specific document using documentName.
• Safeguards store deletion: it deletes an entire store only when force is explicitly set; otherwise it returns a “force-required” error message.
• Ingests files via an n8n Form: the form trigger either creates a new store or targets an existing one, then uploads/imports each file into the Gemini File Search store for indexing.
• Outputs a completion page showing the store ID (storeName) so you can use it in the Agents tool for ongoing querying and management.

Use cases

• Build a SaaS “knowledge base” where operators upload documents through an n8n Form and users query them via Gemini File Search.
• Manage multiple RAG stores for different tenants by creating per-tenant stores and ingesting files on demand.
• Delete outdated documents from a store without touching the rest of the indexed content.

Technical details

• Integrations: Google Generative Language API (Gemini File Search / fileSearchStore endpoints).
• n8n nodes/tools: if, set, code, form, switch, sticky note.
• Setup: add Google Gemini credentials in n8n with access to the File Search and Gemini models endpoints; publish the workflow form and use its URL for file ingestion. For existing stores, paste the fileSearchStores/... ID into the form.