Back to Catalog

Document analysis & chatbot creation with Llama Parser, Gemini LLM & Pinecone DB

pavithpavith
4101 views
2/3/2026
Official Page

📄Description

This automation workflow enables users to upload files via an N8N form, automatically analyzes the content using Google Gemini agents, and delivers the analyzed results via email along with a chatbot link. The system leverages Llama Cloud API, Google Gemini LLM, Pinecone vector database, and Gmail to provide a seamless, multilingual content analysis experience.

✅ Prerequisites

Before setting up this workflow, ensure the following are in place:

An active N8N instance.

Access to Llama Cloud API.

Google Gemini LLM API keys (for Translator & Analyzer agents).

A Pinecone account with an active index.

A Gmail account with API access configured.

Basic knowledge of N8N workflow setup.

⚙️ Setup Instructions

Deploy the N8N Form

Create a public-facing form using N8N.

Configure it to accept:

File uploads.

User email input.

File Preprocessing

Store the uploaded files temporarily.

Organize and preprocess them as needed.

Content Extraction using Llama Cloud API

Feed the files into the Llama Cloud API.

Extract and parse the content for further processing.

Translation (if required)

Use a Translator Agent (Google Gemini).

Check if the content is in English. If not, translate it.

Content Analysis

Forward the (translated) content to the Analyzer Agent (Google Gemini).

Perform deep analysis to extract insights.

Vector Storage in Pinecone

Store both:

The parsed and translated content.

The analyzed content.

Use Pinecone to store the content as embeddings for chatbot use.

User Notification via Gmail

Send the analyzed content and chatbot link to the user’s provided email using Gmail API.

🧩 Customization Guidance

To add more languages: Update the translation logic to include additional language support.

To modify analysis depth: Adjust the prompts sent to the Gemini Analyzer Agent.

To change the chatbot behavior: Retrain or reconfigure the chatbot to utilize the new Pinecone index contextually.

🔁 Workflow Summary

User uploads files and email via N8N form.

Files are parsed using Llama Cloud API.

Content is translated (if needed) using Gemini Translator Agent.

Translated content is analyzed by the Gemini Analyzer Agent.

Parsed and analyzed data is stored in Pinecone.

User receives email with analyzed results and a chatbot link.

n8n Workflow: Document Analysis and Chatbot Creation with Llama-Parser, Gemini LLM, and Pinecone DB

This n8n workflow provides a comprehensive solution for analyzing documents, extracting information, and building a chatbot using advanced AI components. It leverages Langchain nodes to integrate with various AI services, including a Llama-Parser for document loading, Google Gemini for language modeling, and Pinecone for vector database management.

What it does

This workflow automates the following key steps:

  1. Triggers on Form Submission: Initiates the workflow when a user submits data via an n8n form.
  2. Loads Document Data: Takes the submitted document (expected as binary data) and loads it using a Default Data Loader.
  3. Splits Document into Chunks: Uses a Recursive Character Text Splitter to break down the document into manageable chunks for processing.
  4. Generates Embeddings: Creates vector embeddings for each document chunk using the Mistral Cloud Embeddings service.
  5. Stores Embeddings in Pinecone: Uploads the generated embeddings to a Pinecone Vector Store for efficient similarity search.
  6. Triggers on Chat Message: Waits for incoming chat messages to initiate the chatbot interaction.
  7. Retrieves Relevant Information: Uses a Vector Store Retriever to fetch relevant document chunks from Pinecone based on the chat message.
  8. Answers Questions with Gemini LLM: Processes the retrieved information and user query through a Google Gemini Chat Model to generate a coherent answer.
  9. Extracts Structured Information (Optional): Can extract structured information from the document using an Information Extractor.
  10. Sends Email (Optional): Includes a placeholder for sending emails, potentially for notifications or human-in-the-loop approvals.
  11. Performs HTTP Requests (Optional): Contains a placeholder for making HTTP requests, which could be used for external API calls.
  12. Conditional Logic (Optional): Features an If node for implementing conditional branching based on workflow data.
  13. Loops Over Items (Optional): Includes a Loop Over Items node for iterating through collections of data.
  14. Outputs Markdown (Optional): Can format output into Markdown.
  15. Executes Custom Code (Optional): Allows for custom JavaScript logic execution.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Pinecone Account: An API key and environment for Pinecone.
  • Google Gemini API Key: Access to the Google Gemini LLM.
  • Mistral Cloud Account: API access for Mistral Cloud Embeddings.
  • Gmail Account (Optional): Configured Gmail credentials for sending emails.
  • Langchain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed in your n8n instance.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Pinecone credentials (API Key, Environment, Index Name).
    • Configure your Google Gemini Chat Model credentials (API Key).
    • Set up your Mistral Cloud Embeddings credentials (API Key).
    • (Optional) Configure your Gmail credentials if you plan to use the email functionality.
  3. Configure the Form Trigger:
    • The "On form submission" node acts as the entry point for document uploads. Ensure the form is configured to accept binary data (e.g., a file upload field).
  4. Test Document Analysis:
    • Submit a document through the n8n form trigger.
    • Verify that the document is processed, chunks are created, embeddings are generated, and stored in your Pinecone index.
  5. Test Chatbot Interaction:
    • Use the "When chat message received" trigger to simulate a user query.
    • Observe the chatbot's response, which should leverage the document data stored in Pinecone and the Gemini LLM.
  6. Customize (Optional):
    • Adjust the "Recursive Character Text Splitter" parameters (chunk size, overlap) as needed for your documents.
    • Modify the "Information Extractor" schema to define the specific data you want to extract.
    • Implement the "Gmail" node for notifications or approvals.
    • Utilize the "HTTP Request" and "Code" nodes for additional integrations or custom logic.
    • Adjust the "If" and "Loop Over Items" nodes for more complex conditional flows or batch processing.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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.

Le NguyenBy Le Nguyen
942