AI-powered RAG workflow for stock earnings report analysis
This n8n workflow creates a financial analysis tool that generates reports on a company's quarterly earnings using the capabilities of OpenAI GPT-4o-mini, Google's Gemini AI and Pinecone's vector search. By analyzing PDFs of any company's earnings reports from their Investor Relations page, this workflow can answer complex financial questions and automatically compile findings into a structured Google Doc.
How it works:
- Data loading and indexing
- Fetches links to PDF earnings document from a Google Sheet containing a list of file links.
- Downloads the PDFs from Google Drive.
- Parses the PDFs, splits the text into chunks, and generates embeddings using the Embeddings Google AI node (text-embedding-004 model).
- Stores the embeddings and corresponding text chunks in a Pinecone vector database for semantic search.
- Report generation with AI agent
- Utilizes an AI Agent node with a specifically crafted system prompt. The agent orchestrates the entire process.
- The agent uses a Vector Store Tool to access and retrieve information from the Pinecone database.
- Report delivery
- Saves the generated report as a Google Doc in a specified Google Drive location.
Set up steps
- Google Cloud Project & Vertex AI API:
- Create a Google Cloud project.
- Enable the Vertex AI API for your project.
- Google AI API key:
- Obtain a Google AI API key from Google AI Studio.
- Pinecone account and API key:
- Create a free account on the Pinecone website.
- Obtain your API key from your Pinecone dashboard.
- Create an index named company-earnings in your Pinecone project.
- Google Drive - download and save financial documents:
- Go to a company you want to analize and download their quarterly earnings PDFs
- Save the PDFs in Google Drive
- Create a Google Sheet that stores a list of file URLs pointing to the PDFs you downloaded and saved to Google Drive
- Configure credentials in your n8n environment for:
- Google Sheets OAuth2
- Google Drive OAuth2
- Google Docs OAuth2
- Google Gemini(PaLM) Api (using your Google AI API key)
- Pinecone API (using your Pinecone API key)
- Import and configure the workflow:
- Import this workflow into your n8n instance.
- Update the List Of Files To Load (Google Sheets) node to point to your Google Sheet.
- Update the Download File From Google Drive to point to the column where the file URLs are
- Update the Save Report to Google Docs node to point to your Google Doc where you want the report saved.
AI-Powered RAG Workflow for Document Analysis
This n8n workflow demonstrates a powerful Retrieval Augmented Generation (RAG) system designed to process documents, create embeddings, store them in a vector database, and then use an AI agent to answer questions based on the stored information. This can be particularly useful for analyzing large sets of documents like stock earnings reports, research papers, or legal documents.
What it does
This workflow automates the following steps:
- Manual Trigger: Initiates the workflow execution manually.
- Google Drive Integration: Retrieves a list of files (e.g., Google Docs, Google Sheets) from a specified Google Drive folder.
- Loop Over Items: Processes each retrieved file individually or in batches.
- Google Docs / Google Sheets Integration: Depending on the file type, it reads the content from Google Docs or Google Sheets.
- Default Data Loader: Loads the content of the document into a format suitable for text processing.
- Recursive Character Text Splitter: Breaks down the document content into smaller, manageable chunks (e.g., paragraphs or sentences) to optimize for embedding and retrieval.
- Embeddings Google Gemini: Generates vector embeddings for each text chunk using the Google Gemini embedding model.
- Pinecone Vector Store: Stores these text chunks and their corresponding embeddings in a Pinecone vector database, making them searchable for semantic similarity.
- AI Agent: Utilizes an AI agent (configured with either an OpenAI Chat Model or Google Gemini Chat Model) to answer questions.
- Vector Store Question Answer Tool: Equips the AI agent with a tool to query the Pinecone vector store, retrieve relevant document chunks, and use them as context to generate accurate and informed answers.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Account: For Google Drive, Google Docs, and Google Sheets integrations. Ensure your Google account has access to the relevant files and folders.
- Google Cloud Project (for Google Gemini): If using Google Gemini for embeddings and chat, you'll need a Google Cloud Project with the Gemini API enabled and appropriate credentials.
- OpenAI API Key: If using the OpenAI Chat Model for the AI Agent.
- Pinecone Account: An active Pinecone account with an API key and environment configured to store vector embeddings.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up Google OAuth2 credentials for the
Google Drive,Google Docs, andGoogle Sheetsnodes. - Configure your
Pineconecredentials (API Key and Environment). - Set up
OpenAIcredentials (API Key) if you plan to use the OpenAI Chat Model. - Set up
Google Geminicredentials (API Key) if you plan to use the Google Gemini Chat Model and Embeddings.
- Set up Google OAuth2 credentials for the
- Customize Nodes:
- Google Drive: Specify the folder ID where your target documents are located.
- Google Docs / Google Sheets: Ensure these nodes are correctly configured to read the content of your documents. You might need to adjust settings based on your document structure.
- Recursive Character Text Splitter: Adjust
chunkSizeandchunkOverlapparameters based on the nature of your documents and desired retrieval granularity. - Pinecone Vector Store: Configure the
indexNameand other settings to match your Pinecone index. - AI Agent: Select your preferred
Language Model(OpenAI Chat Model or Google Gemini Chat Model) and configure its settings (e.g., model name, temperature). - Vector Store Question Answer Tool: Ensure the tool is correctly linked to your Pinecone Vector Store.
- Execute the Workflow: Click the "Execute workflow" button in the Manual Trigger node to run the workflow. The workflow will process your documents, populate the vector store, and then the AI agent will be ready to answer questions based on this knowledge base.
Related Templates
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 Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte
🎓 How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.