HumationHuman + Automation
Back to Catalog

Legal Case Research Extractor, Data Miner with Bright Data MCP & Google Gemini

Ranjan DailataRanjan Dailata
1744 views
2/3/2026
NotificationFeedSlackAutomationRSS
Official Page

Legal Case Research Extractor.png

Notice

Community nodes can only be installed on self-hosted instances of n8n.

Who this is for

The Legal Case Research Extractor is a powerful automated workflow designed for legal tech teams, researchers, law firms, and data scientists focused on transforming unstructured legal case data into actionable, structured insights.

This workflow is tailored for:

  • Legal Researchers automating case law data mining

  • Litigation Support Teams handling large volumes of case records

  • LawTech Startups building AI-powered legal research assistants

  • Compliance Analysts extracting case-specific insights

  • AI Developers working on legal NLP, summarization, and search engines

What problem is this workflow solving?

Legal case data is often locked in semi-structured or raw HTML formats, scattered across jurisdiction-specific websites. Manually extracting and processing this data is tedious and inefficient.

This workflow automates:

  • Extraction of legal case data via Bright Data's powerful MCP infrastructure

  • Parsing of HTML into clean, readable text using Google Gemini LLM

  • Structuring and delivering the output through webhook and file storage

What this workflow does

Input

  • Set the Legal Case Research URL node is responsible for setting the legal case URL for the data extraction.

Bright Data MCP Data Extractor

  • Bright Data MCP Client For Legal Case Research node is responsible for the legal case extraction via the Bright Data MCP tool - scrape_as_html

Case Extractor

  • Google Gemini based Case Extractor is responsible for producing a paginated list of cases

Loop through Legal Case URLs

  • Receives a collection of legal case links to process

  • Each URL represents a different case from a target legal website

Bright Data MCP Scraping

  • Utilizes Bright Data’s scrape_as_html MCP mode

  • Retrieves raw HTML content of each legal case

Google Gemini LLM Extraction

  • Transforms raw HTML into clean, structured text

  • Performs additional information extraction if required (e.g., case summary, court, jurisdiction etc.)

Webhook Notification

  • Sends extracted legal case content to a configurable webhook URL

  • Enables downstream processing or storage in legal databases

Binary Conversion & File Persistence

  • Converts the structured text to binary format

  • Saves the final response to disk for archival or further processing

Pre-conditions

  1. Knowledge of Model Context Protocol (MCP) is highly essential. Please read this blog post - model-context-protocol
  2. You need to have the Bright Data account and do the necessary setup as mentioned in the Setup section below.
  3. You need to have the Google Gemini API Key. Visit Google AI Studio
  4. You need to install the Bright Data MCP Server @brightdata/mcp
  5. You need to install the n8n-nodes-mcp

Setup

  1. Please make sure to setup n8n locally with MCP Servers by navigating to n8n-nodes-mcp
  2. Please make sure to install the Bright Data MCP Server @brightdata/mcp on your local machine.
  3. Sign up at Bright Data.
  4. Create a Web Unlocker proxy zone called mcp_unlocker on Bright Data control panel.
  5. Navigate to Proxies & Scraping and create a new Web Unlocker zone by selecting Web Unlocker API under Scraping Solutions.
  6. In n8n, configure the Google Gemini(PaLM) Api account with the Google Gemini API key (or access through Vertex AI or proxy).
  7. In n8n, configure the credentials to connect with MCP Client (STDIO) account with the Bright Data MCP Server as shown below.

MCPClientAccount.png

Make sure to copy the Bright Data API_TOKEN within the Environments textbox above as API_TOKEN=<your-token>

How to customize this workflow to your needs

Target New Legal Portals

  • Modify the legal case input URLs to scrape from different state or federal case databases

Customize LLM Extraction

  • Modify the prompt to extract specific fields: case number, plaintiff, case summary, outcome, legal precedents etc.

  • Add a summarization step if needed

Enhance Loop Handling

  • Integrate with a Google Sheet or API to dynamically fetch case URLs

  • Add error handling logic to skip failed cases and log them

Improve Security & Compliance

  • Redact sensitive information before sending via webhook

  • Store processed case data in encrypted cloud storage

Output Formats

  • Save as PDF, JSON, or Markdown

  • Enable output to cloud storage (S3, Google Drive) or legal document management systems

n8n Legal Case Research Extractor & Data Miner with Bright Data MCP & Google Gemini

This n8n workflow automates the process of extracting and summarizing legal case research using a combination of web scraping (implied by the directory name, though not explicitly in the JSON) and advanced AI capabilities from Google Gemini. It's designed to streamline the collection and analysis of information for legal professionals or researchers, transforming raw data into structured, actionable insights.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: Initiates the workflow manually, allowing for on-demand execution.
  2. Code (Prepare Input): Executes custom JavaScript code to prepare the input data for subsequent steps. This likely involves formatting queries or setting up parameters for the data extraction.
  3. HTTP Request (Data Miner): Sends HTTP requests, likely to a web scraping service (like Bright Data's Managed Crawling Platform, as hinted by the directory name) to extract raw legal case data from specified sources.
  4. Loop Over Items (Process Batches): Iterates over the items received from the data miner, processing them in batches. This is crucial for handling large volumes of data efficiently.
  5. Wait: Introduces a pause between processing batches, which can be useful for respecting API rate limits or managing system load.
  6. Edit Fields (Set Output): Transforms and sets specific fields from the extracted data, preparing it for AI processing. This step ensures the data is in the correct format for the language model.
  7. Basic LLM Chain: Utilizes a LangChain node to orchestrate a series of operations with a Large Language Model (LLM). This likely involves defining the overall task for the AI, such as summarizing or extracting specific entities.
  8. Google Gemini Chat Model: Leverages the Google Gemini Chat Model to perform advanced natural language processing tasks. This is where the core AI analysis of the legal case data happens, such as summarizing case details, identifying key arguments, or extracting relevant legal precedents.
  9. Structured Output Parser: Parses the output from the Google Gemini model into a structured format (e.g., JSON), making the AI's insights easily consumable by other systems or for storage.
  10. Read/Write Files from Disk: Saves the processed and summarized legal case data to disk. This could be for archival, further analysis, or integration with other applications.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Google Gemini API Key: An API key for accessing the Google Gemini Chat Model. This will need to be configured as a credential in n8n.
  • Bright Data Account (Managed Crawling Platform - MCP): While not explicitly in the JSON, the directory name "bright-data-mcp" strongly suggests that a Bright Data MCP account is used for web scraping. If so, you will need the necessary API keys or credentials for Bright Data configured in n8n for the "HTTP Request" node.
  • Basic JavaScript Knowledge: For modifying the "Code" node if custom data preparation or manipulation is required.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up a new credential for Google Gemini using your API key.
    • If using Bright Data MCP, configure the necessary HTTP Request node with your Bright Data credentials (e.g., API key, proxy settings, target URLs for legal case data).
  3. Review and Customize Nodes:
    • Code Node: Review the JavaScript code in the "Code" node to ensure it aligns with your specific input data structure and requirements.
    • HTTP Request Node: Update the URL, headers, and body of the "HTTP Request" node to target the specific legal databases or websites you wish to scrape via Bright Data or another service.
    • Basic LLM Chain & Google Gemini Chat Model: Adjust the prompts and model parameters in these nodes to fine-tune the AI's analysis for your legal research needs.
    • Structured Output Parser: Modify the schema in this node if the desired output structure from Gemini differs from the default.
    • Read/Write Files from Disk: Configure the file path and name where you want to save the output.
  4. Execute the Workflow: Click "Execute Workflow" on the "Manual Trigger" node to run the workflow.

This workflow provides a powerful foundation for automating legal case research, combining robust data extraction with advanced AI summarization and structuring.

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://&lt;your-instance&gt;.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