Documentation Lookup AI Agent using Context7 and Gemini
This n8n workflow template uses community nodes and is only compatible with the self-hosted version of n8n.
This workflow demonstrates how to build and expose a sophisticated n8n AI Agent as a single, callable tool using the Multi-Agent Collaboration Protocol (MCP). It allows external clients or other AI systems to easily query software library documentation via Context7, without needing to manage the underlying tool orchestration or complex conversational logic.
Core Idea: Instead of building complex agentic loops on the client-side (e.g., in Python, a VS Code extension, or another AI development environment), this workflow offloads the entire agent's reasoning and tool-use process to n8n. The client simply sends a natural language query (like "How do I use Flexbox in Tailwind CSS?") to an SSE endpoint, and the n8n agent handles the rest.
Key Features & How It Works:
- Public MCP Endpoint:
- The main workflow uses the
Context7 MCP Server Triggernode to create an SSE endpoint. This makes the agent accessible to any MCP-compatible client. - The path for the endpoint is kept long and random for basic 'security by obscurity'.
- The main workflow uses the
- Tool Workflow as an Interface:
- A
Tool Workflownode (namedcall_context7_ai_agentin this example) is connected to the MCP Server Trigger. This node defines the single "tool" that external clients will see and call.
- A
- Dedicated AI Agent Sub-Workflow:
- The
call_context7_ai_agenttool invokes a separate sub-workflow which contains the actual AI logic. - This sub-workflow starts with a
Context7 Workflow Startnode to receive the user'squery. - A
Context7 AI Agentnode (using Google Gemini in this example) is the brain, equipped with:- A system prompt to guide its behavior.
Simple Memoryto retain context for each execution (using{{ $execution.id }}as the session key).- Two specialized Context7 MCP client tools:
context7-resolve-library-id: To convert library names (e.g., 'Next.js') into Context7-specific IDs.context7-get-library-docs: To fetch documentation using the resolved ID, with options for specific topics and token limits.
- The
- Seamless Tool Use: The AI Agent autonomously decides when and how to use the
resolve-library-idandget-library-docstools based on the user's query, handling the multi-step process internally.
Benefits of This Approach:
- Simplified Client Integration: Clients interact with a single, powerful tool, sending a simple query.
- Reduced Client-Side Token Consumption: The detailed prompts, tool descriptions, and conversational turns are managed server-side by n8n, saving tokens on the client (especially useful if the client is another LLM).
- Centralized Agent Management: Update your agent's capabilities, tools, or LLM model within n8n without any changes needed on the client side.
- Modularity for Agentic Systems: Perfect for building complex, multi-agent systems where this n8n workflow can act as a specialized "expert" agent callable by others (e.g., from environments like Smithery).
- Cost-Effective: By using a potentially less expensive model (like Gemini Flash) for the agent's orchestration and leveraging the free tier or efficient pricing of services like Context7, you can build powerful solutions economically.
Use Cases:
- Providing an intelligent documentation lookup service for coding assistants or IDE extensions.
- Creating specialized AI "micro-agents" that can be consumed by larger AI applications.
- Building internal knowledge base query systems accessible via a simple API-like interface.
Setup:
- Ensure you have the necessary n8n credentials for Google Gemini (or your chosen LLM) and the Context7 MCP client tools.
- The
Pathin theContext7 MCP Server Triggernode should be unique and secure. - Clients connect to the "Production URL" (SSE endpoint) provided by the trigger node.
This workflow is a great example of how n8n can serve as a powerful backend for building and deploying modular AI agents.
I've made a video to try and explain this a bit too https://www.youtube.com/watch?v=dudvmyp7Pyg
AI Agent for Documentation Lookup with Gemini and Context
This n8n workflow sets up an AI Agent capable of performing documentation lookups, leveraging Google Gemini as its language model and an n8n workflow as a tool for context retrieval. It's designed to be invoked by another workflow or an external system via the Model Context Protocol (MCP).
What it does
This workflow orchestrates an AI agent to respond to queries by:
- Receiving Input: It listens for incoming requests, likely containing a user query, via the "Execute Workflow Trigger" or "MCP Server Trigger" nodes.
- Maintaining Context: Utilizes a "Simple Memory" (Buffer Window Memory) to keep track of conversational history, enabling the AI agent to understand and respond within the context of an ongoing dialogue.
- Leveraging Google Gemini: Employs the "Google Gemini Chat Model" as the core large language model for processing natural language, understanding user intent, and generating responses.
- Utilizing an n8n Workflow Tool: Integrates a "Call n8n Workflow Tool" which allows the AI agent to execute another n8n workflow. This is crucial for dynamic actions like documentation lookups, where the agent can programmatically fetch information by invoking a dedicated sub-workflow.
- Orchestrating with an AI Agent: The central "AI Agent" node acts as the brain, combining the language model, memory, and tools to intelligently plan and execute steps to fulfill the user's request.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: An active n8n instance where this workflow can be imported.
- Google Gemini API Key: Credentials for accessing the Google Gemini Chat Model. This typically involves setting up a service account or an API key in your Google Cloud project.
- A "Documentation Lookup" n8n Workflow: This workflow expects another n8n workflow to be available and callable as a tool. This sub-workflow would be responsible for the actual documentation retrieval (e.g., querying a database, searching a knowledge base, or calling an external API). You will need to configure the "Call n8n Workflow Tool" node with the ID of this sub-workflow.
- Understanding of n8n's Model Context Protocol (MCP): If you intend to use the "MCP Server Trigger", you should be familiar with how to interact with n8n workflows via MCP for advanced AI agent integrations.
Setup/Usage
- Import the Workflow: Download the JSON definition and import it into your n8n instance.
- Configure Credentials:
- Set up your Google Gemini credentials within n8n. You will likely need to create a new credential for the "Google Gemini Chat Model" node.
- Configure the "Call n8n Workflow Tool":
- Edit the "Call n8n Workflow Tool" node.
- Specify the Workflow ID of the n8n workflow that performs your documentation lookup. This sub-workflow should be designed to accept inputs from the AI agent and return relevant documentation.
- Provide a clear Description for the tool, explaining what it does (e.g., "Useful for looking up information in the company documentation"). This description is critical for the AI agent to understand when to use the tool.
- Configure the Trigger:
- Decide how you want to trigger this workflow.
- If it's part of a larger n8n AI agent system, the "MCP Server Trigger" might be appropriate.
- If it's invoked by another n8n workflow, the "When Executed by Another Workflow" trigger will be used.
- Decide how you want to trigger this workflow.
- Test the Workflow: Once configured, you can test the workflow by sending a query to its trigger endpoint (if using MCP) or by executing it from another workflow. The AI agent should then use its tools and language model to provide a relevant response based on the documentation lookup.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.