Back to Catalog

Automatic email invoice archiving & data extraction with Gmail, Drive & AI

Paolo RoncoPaolo Ronco
328 views
2/3/2026
Official Page

Automated Invoice Archiving

Automatically fetch, store, and extract key information from invoices received via email from your ISP or utility provider (electricity, gas, telecom, water, etc.).The workflow saves the invoices to Google Drive (or optionally to your personal FTP/SFTP server) and logs all invoice details into Google Sheets via AI-powered extraction.

Asset1.png

Read: Full setup Guide

How it works

  1. Scheduled TriggerRuns the workflow at a selected interval (e.g., every hour). You can freely adjust the timing.

  2. Gmail – Fetch MessagesReads your Gmail inbox and retrieves only messages coming from your ISP/utility provider’s email address, filtering for messages with PDF attachments.

  3. Gmail – Download Invoice Fetches the full email content and downloads the attached invoice (PDF).

  4. Google Drive – Upload File Uploads the invoice into a specific Google Drive folder of your choice.

  5. (Optional) Upload to FTP/SFTP Sends a copy of the invoice to your personal server via secure FTP/SFTP.

  6. AI Extraction Pipeline

  • Extract PDF Text – converts the PDF into text (OCR not required if text-based).

  • AI Agent (OpenRouter) – understands the invoice content and extracts structured fields (invoice number, date, provider name, total amount, tax info, line items, etc.)

  • Code Node – sanitizes and parses the JSON from the AI model.

  1. Google Sheets – Append Invoice DataAdds a new row to your Google Sheet with all parsed invoice fields.

  2. (Optional) CleanupAutomatically deletes:– the Gmail message– the temporary file in Google Drive(Useful when you only want your FTP or Sheets copy.)

Parameters to configure

| Parameter | Description | Recommended configuration | | --- | --- | --- | | Gmail Credentials | OAuth2 credentials needed to read and delete emails. | Create OAuth credentials on Google Cloud → enable Gmail API → paste Client ID & Secret into n8n → “Connect OAuth2”. | | Sender Email Filter | Email address your provider uses to send invoices. | Example: billing@your-isp.com, invoices@utility.it, ciao@octopusenergy.it | | Google Drive Folder | Destination folder for saving invoices. | Copy the folder ID from the Drive URL and paste it into folderId. | | Google Drive Credentials | OAuth2 connection for file uploads/deletions. | Same Google Cloud project → enable Drive API → OAuth connect in n8n. | | FTP/SFTP Server (optional) | Upload invoices to your private server. | Host / IP · Port · Username · Password or SSH Key · Destination path (e.g. /home/user/invoices/). | | AI Model (OpenRouter) | Large-language model used to parse invoice text. | Example: gpt-4.1, llama-3.1, or any preferred OpenRouter model. | | Google Sheets Document | Destination spreadsheet for structured data. | Create a Sheet → add columns (Vendor, Invoice Number, Date, Amount, Service Type, etc.) → insert documentId & sheet name. | | Sheets Credentials (Service Account) | Used for writing into Google Sheets. | Create Service Account → download JSON → add to n8n → share the Sheet with the Service Account email. | | Trigger Interval | How often the workflow checks for new invoices. | Every hour · every 30 minutes · daily at set ti |

Node-by-node breakdown

1. Schedule Trigger

Runs at the interval you choose (default: hourly).Start → triggers entire workflow.


2. Gmail – Get Many Messages

Filters inbox items using:

  • Sender email (your ISP/utility address)

  • Has attachment

  • Unread or recent messages

Downloads metadata + attachment references.


3. Filter – Contains Attachment

Ensures only messages with binary attachments continue.


4. Gmail – Get Invoice

Downloads:

  • Full email JSON

  • The invoice PDF (binary data)


5. Google Drive – Upload File

Uploads invoice PDF with a dynamic filename:

{{ $json.from.value[0].name }}-{{ $json.date }}.pdf

Requires:

  • Google Drive OAuth2 credentials

  • Folder ID (destination directory)


6. HTTP Request – Download File

Retrieves the raw PDF file from Google Drive for further processing.


7. (Optional) FTP/SFTP Upload

Uploads the PDF to your server using:

  • Host / IP

  • Port (default 22)

  • Username

  • Password or private key

  • Destination path

Filename is sanitized to ensure Unix compatibility.


8. (Optional) Delete Temporary File

Deletes the Google Drive file if you don’t want duplicates.


9. (Optional) Delete Gmail Message

Removes the original email once processed (optional inbox cleanup).


10. Extract from File (PDF → Text)

Reads the PDF and extracts raw text for AI processing.


11. OpenRouter Chat Model

LLM backend for the AI agent. Provides:

  • invoice parsing

  • field extraction

  • structured reasoning


12. AI Agent – Extract Invoice Fields

The agent is instructed to return strict JSON only, containing keys such as:

  • vendor_name

  • invoice_number

  • invoice_date

  • total_amount

  • tax_details

  • line_items[]

  • po_number

  • po_date

Works for most standard PDF invoices.


13. Code – Clean & Parse JSON

Sanitizes the AI output:

  • Removes markdown fences

  • Extracts valid JSON

  • Parses into a clean JS object

If the AI output is malformed, debugging info is returned.


14. Google Sheets – Append Data

Appends the extracted fields into a structured row.Example mappings:

  • Vendor{{ $json.vendor_name }}

  • Invoice Number{{ $json.invoice_number }}

  • Date{{ $json.invoice_date }}

  • Amount{{ $json.total_amount }}

  • Service Type{{ $json.line_items[0].description }}


💡 Tips & best practices

  • Add multiple sender filters if you have more than one utility provider.

  • Ensure invoices are text-based PDFs for best extraction results.

  • Use Google Drive as a reliable long-term archive, or keep only FTP if you prefer local storage.

  • Create charts in Google Sheets for tracking:

    • Monthly utility cost trends

    • Year-over-year comparison

    • Consumption spikes (if included in invoices)


⚠️ Important notes

  • Utility invoices contain personal and financial data. Keep your FTP/SFTP server secure.

  • Google APIs require proper OAuth2 or Service Account setup; misconfiguration may cause permission errors.

  • This workflow is for personal automation, not a replacement for official fiscal archiving.

  • AI extraction quality depends on invoice formatting and the model you choose.

n8n Workflow: Automated Email Invoice Archiving and Data Extraction

This n8n workflow automates the process of identifying, extracting data from, and archiving email invoices. It leverages AI for data extraction and organizes the extracted information into a Google Sheet and the original invoice in Google Drive.

What it does

This workflow streamlines your invoice management by performing the following steps:

  1. Triggers on Schedule: The workflow runs on a predefined schedule (e.g., daily, hourly) to check for new emails.
  2. Fetches Unread Emails: It connects to your Gmail account to retrieve unread emails.
  3. Filters for Invoices: It filters these emails, specifically looking for ones containing attachments.
  4. Extracts Invoice Data: For each email with an attachment, it attempts to extract the file content.
  5. AI-Powered Data Extraction: It uses an AI Agent (powered by an OpenRouter Chat Model) to intelligently extract key information (like invoice number, vendor, amount, date) from the invoice document.
  6. Stores Data in Google Sheets: The extracted invoice data is then appended as a new row to a specified Google Sheet.
  7. Archives Invoice in Google Drive: The original invoice attachment is uploaded and archived in a designated folder within Google Drive.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Gmail Account: Configured n8n credentials for your Gmail account with access to the mailbox you want to monitor.
  • Google Drive Account: Configured n8n credentials for your Google Drive account with permissions to create and upload files.
  • Google Sheets Account: Configured n8n credentials for your Google Sheets account with permissions to write to a spreadsheet.
  • OpenRouter API Key: An API key for OpenRouter to power the AI Agent for data extraction.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Gmail credentials.
    • Set up your Google Drive credentials.
    • Set up your Google Sheets credentials.
    • Set up your OpenRouter Chat Model credentials with your API key.
  3. Customize Nodes:
    • Schedule Trigger (Node 839): Adjust the schedule to your preferred frequency for checking emails.
    • Gmail (Node 356): Configure the "Search" options to target specific emails (e.g., from certain senders, with specific subject keywords like "invoice", "bill", etc.). Ensure "Read Emails" is set to false if you only want to process unread emails.
    • Filter (Node 844): Refine the filter conditions to accurately identify emails containing invoices (e.g., item.attachments.length > 0).
    • AI Agent (Node 1119): You may need to refine the prompt for the AI Agent to accurately extract the specific data points you need from your invoices.
    • Google Sheets (Node 18): Specify the Spreadsheet ID and Sheet Name where the extracted data should be stored. Ensure the column headers in your Google Sheet match the keys expected by the AI Agent's output.
    • Google Drive (Node 58): Specify the Folder ID where the invoice attachments should be uploaded.
  4. Activate the Workflow: Once configured, activate the workflow to start automating your invoice archiving and data extraction.

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