HumationHuman + Automation
Back to Catalog

Extract and process healthcare claims with VLM Run, Google Drive and Sheets

ShahrearShahrear
548 views
2/3/2026
WebhookAutomationData ExtractionClickUpCSV
Official Page

Automatically process healthcare claims into structured Google Sheets entries with VLM Run extraction

What this workflow does

  • Monitors Google Drive for new files in a target folder
  • Downloads the file inside n8n for processing
  • Sends the file to VLM Run for AI transcription or analysis
  • Fetches extra details from the healthcare.claims-processing domain as JSON
  • Appends normalized fields to a Google Sheet as a new row

Setup

Prerequisites: Google account, VLM Run API credentials, Google Sheets access, n8n. Install the verified VLM Run node by searching for VLM Run in the node list, then click Install. Once installed, you can start using it in your workflows.

Quick Setup:

  1. Create the Drive folder you want to watch and copy its Folder ID
  2. Create a Google Sheet with headers like: timestamp, file_name, file_id, mime_type, size_bytes, uploader_email, form_type, carrier_name, patient_name, patient_birth_date, patient_sex, patient_address, insurance_type, insurance_id, insured_name, total_charge, amount_due, amount_paid, hospitalization_from, hospitalization_to, referring_physician_name, processing_notes, …other claim fields as needed
  3. Configure Google Drive OAuth2 for the trigger and download nodes
  4. Add VLM Run API credentials from https://app.vlm.run/dashboard to the VLM Run node
  5. Configure Google Sheets OAuth2 and set Spreadsheet ID and target sheet tab
  6. Test by uploading a sample file to the watched Drive folder and activate

Perfect for

  • Centralized intake of healthcare claim documents with instant AI summaries
  • Claims and operations teams collecting structured claim insights
  • Customer support attachments that need quick triage to a Sheet
  • Compliance and audit logs for claim documents

Key Benefits

  • End to end automation from Drive to Sheets
  • Accurate AI output via VLM Run with optional timestamps
  • Domain enrichment from healthcare.claims-processing JSON
  • Clean, searchable logs in Google Sheets
  • No manual steps after activation

How to customize

Extend by adding:

  • OCR tuning and field validation for claim forms
  • Per type routing for PDFs, images, or scanned forms
  • Slack notifications on each new Sheet append
  • Keyword extraction and auto tagging for claim categories
  • Error branch that records failures to a second Sheet

Extract and Process Healthcare Claims with VLM, Google Drive, and Google Sheets

This n8n workflow automates the extraction and processing of healthcare claims by leveraging Google Drive for file storage and Google Sheets for data management. It's designed to streamline the handling of claim documents, making it easier to manage and analyze them.

What it does

This workflow simplifies the process of managing healthcare claims by:

  1. Monitoring Google Drive: It listens for new files uploaded to a specified Google Drive folder.
  2. Processing New Files: When a new file (presumably a healthcare claim document) is detected, the workflow initiates its processing.
  3. Storing Data in Google Sheets: The extracted information from the claim document is then recorded into a Google Sheet, allowing for structured data storage and further analysis.
  4. Handling File Operations: It interacts with Google Drive to manage the claim documents, potentially moving or categorizing them after processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Account: A Google account with access to:
    • Google Drive: For storing and triggering on new claim documents.
    • Google Sheets: For storing the processed claim data.
  • Google Credentials in n8n: Configured Google OAuth2 credentials in n8n that have access to both Google Drive and Google Sheets.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Credentials:
    • Ensure your Google OAuth2 credentials are set up correctly in n8n.
    • Verify that these credentials have the necessary permissions for Google Drive (read, write, list files) and Google Sheets (read, write).
  3. Configure Google Drive Trigger:
    • Open the "Google Drive Trigger" node.
    • Select your Google account credential.
    • Specify the Google Drive folder where new healthcare claim documents will be uploaded. This is the folder the workflow will monitor.
  4. Configure Google Sheets Node:
    • Open the "Google Sheets" node.
    • Select your Google account credential.
    • Specify the Spreadsheet ID and Sheet Name where the extracted claim data should be written.
    • Map the data fields from the preceding nodes to the appropriate columns in your Google Sheet.
  5. Activate the Workflow: Once configured, activate the workflow. It will now automatically trigger when new files are added to the specified Google Drive folder.

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 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

Wessel BulteBy Wessel Bulte
247