Automated invoice data extraction with LlamaParse, Gemini 2.5 & Google Sheets
This n8n template demonstrates how to automate invoice data extraction from PDF attachments received via Gmail. Using LlamaParse and Gemini LLM, this workflow parses structured fields like PO numbers, line items, tax amounts, and totals โ and stores them neatly into a Google Sheet.
Perfect for use cases such as: ๐ผ Finance teams managing vendor invoices ๐ Bookkeeping workflows ๐ Automating monthly reconciliation
Good to Know
At the time of writing, LlamaParse and Gemini may involve API usage costs depending on your subscription tier. Check LlamaIndex Pricing and Gemini Pricing for updated info.
LlamaParse provides Markdown-formatted parsed output which is then passed to an LLM for structured field extraction.
Gemini models may be geo-restricted. If you encounter "model not found" errors, your region might not be supported.
How it Works
- Trigger: Watches your Gmail for new emails with PDF attachments.
- Email Filter: Ensures we only parse fresh emails not already labeled as "invoice synced".
- LlamaParse Upload: Uploads the PDF to LlamaParseโs parsing endpoint.
- Status Polling: Periodically checks whether the parsing is complete.
- Download Markdown: Once ready, it fetches the parsed invoice in Markdown format.
- AI Parsing with Gemini: Sends the Markdown to Gemini LLM to extract structured JSON (like PO number, line items, taxes, etc.) using a predefined schema.
- Google Sheets Upload: Stores extracted data into a predefined spreadsheet.
- Labeling: Marks the email as โinvoice syncedโ to avoid reprocessing.
How to Use
The trigger is based on Gmail, but you can replace this with a webhook or manual trigger for testing.
Setup Instructions
Gmail API
- Enable Gmail API in Google Cloud Console.
- Connect your Gmail account in n8n credentials.
- Allow read + modify access.
Google Sheets
- Create a new Google Sheet with the following headers (row 1): Date | Vendor Name | Invoice Number | PO Number | Line Items | Subtotal | Tax | Total Amount
- Connect Google Sheets in n8n and paste the Sheet ID in the node.
- You can customise the google sheet basis your requirement.
LlamaParse
- Get a LlamaIndex API Key from LlamaIndex.
- Use the LlamaParse upload and polling nodes to process your PDFs.
Gemini (via Vertex AI)
- Set up Gemini access in GCP.
- Use the Gemini 2.5 Model.
- Construct a structured prompt to extract required fields.
Labeling
- Create a Gmail label named "Invoice Synced" for tracking processed emails.
Requirements
Gmail account with API access
LlamaParse (LlamaIndex) account with API Key
Google Sheets API credentials
Access to Gemini 2.5 model via Google Vertex AI
Customising This Workflow
This template is just the beginning. You can expand it to:
- Auto-generate invoices back to vendors
- Run duplicate checks before inserting into Sheets
- Integrate with accounting tools like Zoho, QuickBooks, or Tally
- Trigger Slack/Email notifications on specific vendors or high invoice amounts
Automated Invoice Data Extraction with LLamaParse, Gemini, and Google Sheets
This n8n workflow automates the process of extracting key data from invoice PDFs received via email, processing it with advanced AI models, and storing the structured information in a Google Sheet. It's designed to streamline invoice management, reduce manual data entry, and improve accuracy.
What it does
- Monitors Gmail for New Invoices: The workflow is triggered when a new email arrives in a specified Gmail inbox.
- Filters for Invoice Emails: It checks if the email subject contains "invoice" (case-insensitive) to ensure only relevant emails are processed.
- Extracts PDF Attachments: For each qualifying email, it extracts any attached PDF files.
- Extracts Data from PDFs using LLamaParse: It sends the PDF content to a custom HTTP endpoint (presumably a LLamaParse instance) to extract structured data.
- Processes Extracted Data with Google Gemini: The extracted raw text from the PDF is then sent to the Google Gemini Chat Model, along with a structured output parser, to transform it into a clean JSON format containing specific invoice details (e.g., invoice number, vendor, total amount, line items).
- Formats Data: The extracted and processed data is then formatted into a structured object suitable for Google Sheets.
- Checks for Existing Invoices: It queries a Google Sheet to see if an invoice with the same invoice number already exists.
- Conditionally Adds/Updates Google Sheet:
- If the invoice number is new, it adds a new row with the extracted data to the Google Sheet.
- If the invoice number already exists, it updates the existing row with the new data.
- Sends Confirmation Email: After successfully processing and recording the invoice data, it sends a confirmation email.
- Handles Errors: If an error occurs during the processing (e.g., no PDF found, data extraction failure), it sends an error notification email.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Gmail Account: Connected to n8n with appropriate credentials to read emails and send new ones.
- Google Sheets Account: Connected to n8n with appropriate credentials to read and write data to a specific spreadsheet.
- LLamaParse Instance/Endpoint: An accessible HTTP endpoint for LLamaParse (or a similar PDF parsing service) to extract raw text from PDFs. This is represented by the "HTTP Request" node.
- Google Gemini API Key: Configured within the
Google Gemini Chat Modelnode for AI-powered data extraction and structuring.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Gmail Trigger & Gmail Node: Set up a Google OAuth2 credential for your Gmail account.
- Google Sheets Node: Set up a Google OAuth2 credential for your Google Sheets account.
- Google Gemini Chat Model: Configure your Google Gemini API key.
- Configure Nodes:
- Gmail Trigger: Specify the mailbox and any filters (e.g.,
subject:invoice has:attachment filename:pdf). - HTTP Request (LLamaParse): Update the URL to your LLamaParse (or similar service) endpoint. You may also need to configure any necessary authentication headers or body parameters.
- Google Sheets:
- Specify the Spreadsheet ID and Sheet Name where invoice data will be stored.
- Ensure the column names in your Google Sheet match the keys expected by the workflow (e.g.,
Invoice Number,Vendor,Total Amount,Line Items).
- Gmail (Confirmation/Error): Update the recipient email addresses for confirmation and error notifications.
- Gmail Trigger: Specify the mailbox and any filters (e.g.,
- Activate the Workflow: Once all credentials and configurations are set, activate the workflow.
Now, whenever an email containing "invoice" in the subject and a PDF attachment arrives in your configured Gmail inbox, the workflow will automatically extract the data, process it, record it in your Google Sheet, and send notifications.
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.