Quick overview Helps Japanese businesses digitizing paper invoices and receipts under Japan's Electronic Bookkeeping Act. Files in a Google Drive INPUT folder are read with Google Gemini OCR, then copied to OUTPUT with a compliant searchable filename (date_partner_amount_type) or to SKIP for human review. Originals are never modified. How it works Runs manually to start processing. Lists up to the configured maximum number of files in a Google Drive INPUT folder and iterates through them one at a time. Downloads each file from Google Drive, detects its MIME type, base64-encodes the content, and prepares a Gemini request payload. Sends supported images and PDFs to the Google Gemini generateContent API to extract document count, transaction date, partner, amount, and document type as JSON. Builds a compliant filename in the format YYYYMMDD_partner_amount_type.ext when the response indicates a single valid document with required fields. Copies the original file to a Google Drive OUTPUT folder using the new filename, or copies it to a SKIP folder unchanged when the file type is unsupported or the extraction is ambiguous (non-document/multiple documents/missing fields).
Tags
Google DriveWHTTP RequestRelated workflows
See all Google Drive→WDeploy Workflows from Google Drive to n8n Instance
Automatically deploy n8n workflows by simply dropping JSON files into a Google Drive folder—this template watches for new exports, cleans and imports them into your n8n instance, applies a tag, and then archives the processed files. Who is this template for? This workflow template is designed for n8n power users, and automation specialists who need a simple, reliable way to bulk‑deploy or version‑control n8n workflows via Google Drive. It’s perfect if you: Manage multiple n8n instances (staging, production, etc.) Want an easy “drop‑in” approach to publish new or updated workflows Prefer storing/exporting JSON in Drive rather than editing in the UI Use case Manually importing .json exports into n8n is slow and error‑prone. With this template you can: Keep your workflows in a shared Drive folder (version control friendly) Automatically sanitize each file so only supported settings go through Tag deployed workflows consistently for easy filtering Move processed files to a “Deployed” folder for clear change tracking How it works Watch “ToDeploy” folder in Google Drive for new .json files Download & parse each file into a JSON object Clean payload: strip out everything except the allowe
WGenerate & Upload Images with Image-to-Image GPT, Google Sheets & Drive
🖼️ Image-to-Image AI Generator from Google Sheets with Google Drive Upload ✅ Use Case Automatically generate AI images from prompts listed in a Google Sheet, upload the images to Google Drive, and log the result back into the sheet. Uses the image-to-image-gpt API for fast, customizable generation. 💡 Problem It Solves Manual image generation workflows are inefficient and error-prone. Creative and content teams often have to: Manually paste prompts into image generation tools Save images locally Upload to Google Drive Paste the link back into tracking spreadsheets This automation removes all that friction—turning one spreadsheet into a complete image creation pipeline. 🌟 Benefits 🔁 Fully automated image generation 📤 Direct uploads to Google Drive 🧾 Image links and timestamps logged in Google Sheets ⚠️ Built-in error logging for API failures 🧩 Modular and easily extensible 📊 Keeps a historical log of successes and errors 🧩 Workflow Overview | Node | Description | |------|-------------| | 1. Manual Trigger | Starts the workflow when executed manually | | 2. Google Sheets2 | Reads all rows from the input Google Sheet | | 3. Loop Over Items | Processes one row (prompt) at a tim
WRecognize invoices / receipts from Google Drive and put them into Google Sheets
This workflow allows you to recognize a folder with receipts or invoices (make sure your files are in .pdf, .png, or .jpg format). The workflow can be triggered via the "Test workflow" button, and it also monitors the folder for new files, automatically recognizing them. Video Demo https://youtu.be/mGPt7fqGQD8 1. n8n import glitch After import, the trigger node "When clicking 'Test workflow'" might be disconnected. You need to connect it via 2 arrows to "Google Sheets1" and "Google Drive" nodes. So, the workflow has 2 triggers - via button, and via Google Sheets "new file" event - both of these triggers should be connected to 2 nodes. Here is how it should look like: https://ocr.oakpdf.com/n8n_fix.png 2. Set up RapidAPI HTTP auth key Create new "HTTP header" n8n credential and paste your RapidAPI key from https://rapidapi.com/restyler/api/receipt-and-invoice-ocr-api into it. https://ocr.oakpdf.com/n8n_api_key.png Make sure "HTTP Request" node uses this credential. 3. Set up your Google Auth You need a Google connection to work with your Google Sheets and Google Drive accounts: https://docs.n8n.io/integrations/builtin/credentials/google/oauth-generic/#finish-your-n8n-credential 4. S