HumationHuman + Automation
Back to Catalog

Lead generation system: Google Maps to email scraper with Google Sheets export

Nick SaraevNick Saraev
87277 views
2/3/2026
PostgreSQLWhisperOpenAIAutomationMinIO
Official Page

Google Maps Email Scraper System

Categories: Lead Generation, Web Scraping, Business Automation

This workflow creates a completely free Google Maps email scraping system that extracts unlimited business emails without requiring expensive third-party APIs. Built entirely in N8N using simple HTTP requests and JavaScript, this system can generate thousands of targeted leads for any industry or location while operating at 99% free cost structure.

Benefits

  • Zero API Costs - Operates entirely through free Google Maps scraping without expensive third-party services
  • Unlimited Lead Generation - Extract emails from thousands of Google Maps listings across any industry
  • Geographic Targeting - Search by specific cities, regions, or business types for precise lead targeting
  • Complete Automation - From search query to organized email list with minimal manual intervention
  • Built-in Data Cleaning - Automatic duplicate removal, filtering, and data validation
  • Scalable Processing - Handle hundreds of businesses per search with intelligent rate limiting

How It Works

Google Maps Search Integration:

  • Uses strategic HTTP requests to Google Maps search URLs
  • Processes search queries like "Calgary + dentist" to extract business listings
  • Bypasses API restrictions through direct HTML scraping techniques

Intelligent URL Extraction:

  • Custom JavaScript regex patterns extract website URLs from Google Maps data
  • Filters out irrelevant domains (Google, schema, static files)
  • Returns clean list of actual business websites for processing

Smart Website Processing:

  • Loop-based architecture prevents IP blocking through intelligent batching
  • Built-in delays and redirect handling for reliable scraping
  • Processes each website individually with error handling

Email Pattern Recognition:

  • Advanced regex patterns identify email addresses within website HTML
  • Extracts contact emails, info emails, and administrative addresses
  • Handles multiple email formats and validation patterns

Data Aggregation & Cleaning:

  • Automatically removes duplicate emails across all processed websites
  • Filters null entries and invalid email formats
  • Exports clean, organized email lists to Google Sheets

Required Google Sheets Setup

Create a Google Sheet with these exact column headers:

Search Tracking Sheet:

  • searches - Contains your search queries (e.g., "Calgary dentist", "Miami lawyers")

Email Results Sheet:

  • emails - Contains extracted email addresses from all processed websites

Setup Instructions:

  1. Create Google Sheet with two tabs: "searches" and "emails"
  2. Add your target search queries to the searches tab (one per row)
  3. Connect Google Sheets OAuth credentials in n8n
  4. Update the Google Sheets document ID in all sheet nodes

The workflow reads search queries from the first sheet and exports results to the second sheet automatically.

Business Use Cases

  • Local Service Providers - Find competitors and potential partners in specific geographic areas
  • B2B Sales Teams - Generate targeted prospect lists for cold outreach campaigns
  • Marketing Agencies - Build industry-specific lead databases for client campaigns
  • Real Estate Professionals - Identify businesses in target neighborhoods for commercial opportunities
  • Franchise Development - Research potential markets and existing competition
  • Market Research - Analyze business density and contact information across regions

Revenue Potential

This system transforms lead generation economics:

  • $0 per lead vs. $2-5 per lead from paid databases
  • Process 1,000+ leads daily without hitting API limits
  • Sell as a service for $500-2,000 per industry/location
  • Perfect for agencies offering lead generation to local businesses

Difficulty Level: Intermediate
Estimated Build Time: 1-2 hours
Monthly Operating Cost: $0 (completely free)

Watch My Complete Build Process

Want to watch me build this entire system live from scratch? I walk through every single step - including the JavaScript code, regex patterns, error handling, and all the debugging that goes into creating a bulletproof scraping system.

🎥 Watch My Live Build: "Scrape Unlimited Leads WITHOUT Paying for APIs (99% FREE)"

This comprehensive tutorial shows the real development process - including writing custom JavaScript, handling rate limits, and building systems that actually work at scale without getting blocked.

Set Up Steps

Basic Workflow Architecture:

  • Set up manual trigger for testing and Google Sheets integration
  • Configure initial HTTP request node for Google Maps searches
  • Enable SSL ignore and response headers for reliable scraping

URL Extraction Code Setup:

  • Configure JavaScript code node with custom regex patterns
  • Set up input data processing from Google Maps HTML responses
  • Implement URL filtering logic to remove irrelevant domains

Website Processing Pipeline:

  • Add "Split in Batches" node for intelligent loop processing
  • Configure HTTP request nodes with proper delays and redirect handling
  • Set up error handling for websites that can't be scraped

Email Extraction System:

  • Implement JavaScript code node with email-specific regex patterns
  • Configure email validation and format checking
  • Set up data aggregation for multiple emails per website

Data Cleaning & Export:

  • Configure filtering nodes to remove null entries and duplicates
  • Set up "Split Out" node to aggregate emails into single list
  • Connect Google Sheets integration for organized data export

Testing & Optimization:

  • Use limit nodes during testing to prevent IP blocking
  • Test with small batches before scaling to full searches
  • Implement proxy integration for high-volume usage

Advanced Optimizations

Scale the system with:

  • Multi-Page Scraping: Extract URLs from homepages, then scrape contact pages for more emails
  • Proxy Integration: Add residential proxies for unlimited scraping without rate limits
  • Industry Templates: Create pre-configured searches for different business types
  • Contact Information Expansion: Extract phone numbers, addresses, and social media profiles
  • CRM Integration: Automatically add leads to sales pipelines and marketing sequences

Important Considerations

  • Rate Limiting: Built-in delays prevent IP blocking during normal usage
  • Scalability: For high-volume usage, consider proxy services for unlimited requests
  • Compliance: Ensure proper usage rights for extracted contact information
  • Data Quality: System includes filtering but manual verification recommended for critical campaigns

Check Out My Channel

For more advanced automation systems and business-building strategies that generate real revenue, explore my YouTube channel where I share proven automation techniques used by successful agencies and entrepreneurs.

5385-lead-generation-system-google-maps-to-email-scraper-with-google-sheets-export

This n8n workflow is designed to process and manage data, likely from an external source, by applying various transformations and ultimately exporting the refined data to a Google Sheet. It focuses on data cleaning, structuring, and batch processing to ensure efficient and reliable data handling.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: Initiates the workflow manually, allowing for on-demand execution.
  2. Limit Data: Restricts the number of items processed, useful for testing or managing API call limits.
  3. Remove Duplicates: Identifies and removes duplicate items based on specified criteria, ensuring data uniqueness.
  4. Loop Over Items (Split in Batches): Processes items in manageable batches, which can be beneficial for rate limiting or memory management with external services.
  5. Wait: Introduces a pause between processing batches, typically used to respect API rate limits or allow time for external systems to process requests.
  6. HTTP Request: Makes an HTTP request to an external API or service. This node is typically used to fetch additional data, enrich existing data, or send data to another system.
  7. Code: Executes custom JavaScript code, providing flexibility for complex data manipulation, formatting, or conditional logic that is not covered by standard n8n nodes.
  8. Split Out: Splits a single item containing an array or object into multiple individual items, making it easier to process nested data structures.
  9. Filter: Conditionally filters items based on specific criteria, allowing only relevant data to proceed to subsequent nodes.
  10. Google Sheets: Appends or updates data in a Google Sheet, serving as the final destination for the processed information.
  11. Sticky Note: Provides an annotation within the workflow for documentation or explanation purposes.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Google Account: A Google account with access to Google Sheets for data export. You will need to set up a Google Sheets credential in n8n.
  • External API/Service: If the "HTTP Request" node is configured to call an external API, you will need the necessary API keys or authentication details for that service.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credential in n8n.
    • If the "HTTP Request" node requires authentication, configure the necessary credentials for the external service.
  3. Review and Customize Nodes:
    • Limit: Adjust the Limit node as needed to control the number of items processed.
    • Remove Duplicates: Configure the Remove Duplicates node to specify which fields should be used for identifying duplicates.
    • Loop Over Items (Split in Batches): Adjust the batch size and delay in the Loop Over Items and Wait nodes if you are interacting with an API that has rate limits.
    • HTTP Request: Update the URL, method, headers, and body of the HTTP Request node to match the external API you intend to call.
    • Code: Modify the JavaScript code in the Code node to fit your specific data transformation needs.
    • Split Out: Configure the Split Out node to correctly extract nested data.
    • Filter: Define the conditions in the Filter node to ensure only desired items pass through.
    • Google Sheets: Specify the Spreadsheet ID, Sheet Name, and the data to be written to the Google Sheet.
  4. Execute Workflow: Click the "Execute workflow" button to run the workflow manually.

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