Back to Catalog

Extract business contact leads from Google Maps with RapidAPI and Google Sheets

Javier HitaJavier Hita
3122 views
2/3/2026
Official Page

Follow me on LinkedIn for more!

Category: Lead Generation, Data Collection, Business Intelligence

Tags: lead-generation, google-maps, rapidapi, business-data, contact-extraction, google-sheets, duplicate-prevention, automation

Difficulty Level: Intermediate

Estimated Setup Time: 15-20 minutes

Template Description

Overview

This powerful n8n workflow automates the extraction of comprehensive business information from Google Maps using keyword-based searches via RapidAPI's Local Business Data service. Perfect for lead generation, market research, and competitive analysis, this template intelligently gathers business data including contact details, social media profiles, and location information while preventing duplicates and optimizing API usage.

Key Features

  • πŸ” Keyword-Based Google Maps Scraping: Search for any business type in any location using natural language queries
  • πŸ“§ Contact Information Extraction: Automatically extracts emails, phone numbers, and social media profiles (LinkedIn, Instagram, Facebook, etc.)
  • 🚫 Smart Duplicate Prevention: Two-level duplicate detection saves 50-80% on API costs by skipping processed searches and preventing duplicate business entries
  • πŸ“Š Google Sheets Integration: Seamless data storage with automatic organization and structure
  • 🌍 Multi-Location Support: Process multiple cities, regions, or countries in a single workflow execution
  • ⚑ Rate Limiting & Error Handling: Built-in delays and error handling ensure reliable, uninterrupted execution
  • πŸ’° Cost Optimization: Intelligent batching and duplicate prevention minimize API usage and costs
  • πŸ“± Comprehensive Data Collection: Gather business names, addresses, ratings, reviews, websites, verification status, and more

Prerequisites

Required Services & Accounts

  1. RapidAPI Account with subscription to "Local Business Data" API
  2. Google Account for Google Sheets integration
  3. n8n Instance (cloud or self-hosted)

Required Credentials

  • RapidAPI HTTP Header Authentication for Local Business Data API
  • Google Sheets OAuth2 for data storage and retrieval

Setup Instructions

Step 1: RapidAPI Configuration

  1. Create RapidAPI Account

    • Sign up at RapidAPI.com
    • Navigate to "Local Business Data" API
    • Subscribe to a plan (Basic plan supports 1000 requests/month)
  2. Get API Credentials

    • Copy your X-RapidAPI-Key from the API dashboard
    • Note the host: local-business-data.p.rapidapi.com
  3. Configure n8n Credential

    • In n8n: Settings β†’ Credentials β†’ Create New
    • Type: HTTP Header Auth
    • Name: RapidAPI Local Business Data
    • Add headers:
      • X-RapidAPI-Key: YOUR_API_KEY
      • X-RapidAPI-Host: local-business-data.p.rapidapi.com

Step 2: Google Sheets Setup

  1. Enable Google Sheets API

  2. Configure n8n Credential

    • In n8n: Settings β†’ Credentials β†’ Create New
    • Type: Google Sheets OAuth2 API
    • Follow OAuth2 setup process
  3. Create Google Sheet Structure

Create a new Google Sheet with these tabs:

keyword_searches sheet:

| select | query | lat | lon | country_iso_code |
|--------|-------|-----|-----|------------------|
| X | Restaurants Madrid | 40.4168 | -3.7038 | ES |
| X | Hair Salons Brooklyn | 40.6782 | -73.9442 | US |
| X | Coffee Shops Paris | 48.8566 | 2.3522 | FR |

stores_data sheet:

The workflow will automatically create columns for business data including:
business_id, name, phone_number, email, website, full_address, rating, 
review_count, linkedin, instagram, query, lat, lon, and 25+ more fields

Step 3: Workflow Configuration

  1. Import the Workflow

    • Copy the provided JSON
    • In n8n: Import from JSON
  2. Update Placeholder Values

    • Replace YOUR_GOOGLE_SHEET_ID with your actual Google Sheet ID
    • Update credential references to match your setup
  3. Configure Search Parameters (Optional)

    • Adjust limit: 1-100 results per query (default: 100)
    • Modify zoom: 10-18 search radius (default: 13)
    • Change language: EN, ES, FR, etc. (default: EN)

How It Works

Workflow Process

  1. Load Search Criteria: Reads queries marked with "X" from keyword_searches sheet
  2. Load Existing Data: Retrieves previously processed data for duplicate detection
  3. Filter New Searches: Smart merge identifies only new query+location combinations
  4. Process Each Location: Sequential processing prevents API overload
  5. Configure Parameters: Prepares search parameters from sheet data
  6. API Request: Calls RapidAPI to extract business information
  7. Parse Data: Structures and cleans all business information
  8. Save Results: Stores new leads in stores_data sheet
  9. Rate Limiting: 10-second delay between requests
  10. Loop: Continues until all new searches are processed

Duplicate Prevention Logic

Search Level: Compares new queries against existing data using query+latitude combination, skipping already processed searches.

Business Level: Each business receives a unique business_id to prevent duplicate entries even across different searches.

Data Extracted

Business Information

  • Business name, full address, phone number
  • Website URL, Google My Business rating and review count
  • Business type, price level, verification status
  • Geographic coordinates (latitude/longitude)
  • Detailed location breakdown (street, city, state, country, zip)

Contact Details

  • Email addresses (when publicly available)
  • Social media profiles: LinkedIn, Instagram, Facebook, Twitter, YouTube, TikTok, Pinterest
  • Additional phone numbers
  • Direct Google Maps and reviews links

Search Metadata

  • Original search query and parameters
  • Extraction timestamp and geographic data
  • API response details for tracking

Use Cases

Lead Generation

  • Generate targeted prospect lists for B2B sales
  • Build location-specific customer databases
  • Create industry-specific contact lists
  • Develop territory-based sales strategies

Market Research

  • Analyze competitor density in target markets
  • Study business distribution

Extract Business Contact Leads from Google Maps with RapidAPI and Google Sheets

This n8n workflow is designed to automate the process of extracting business contact leads from Google Maps using a RapidAPI service and then storing the collected data in a Google Sheet. It's ideal for lead generation, market research, or building targeted contact lists.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: Initiates the workflow manually, allowing you to control when the lead extraction process begins.
  2. Google Sheets (Read Input): Reads a list of search queries (e.g., business categories, locations) from a specified Google Sheet. This acts as the input for what businesses to search for.
  3. Loop Over Items: Processes each search query from the Google Sheet individually, allowing for multiple searches to be performed in a single workflow run.
  4. Edit Fields (Set Query): Prepares the search query for the RapidAPI request by setting the necessary input parameters.
  5. HTTP Request (RapidAPI Google Maps): Sends an HTTP request to a RapidAPI endpoint (presumably a Google Maps scraper or search API) with the prepared query to fetch business data.
  6. Code (Process API Response): Executes custom JavaScript code to parse and transform the raw data received from the RapidAPI response into a structured format suitable for storage.
  7. Wait: Introduces a pause between API requests to avoid hitting rate limits or to space out operations.
  8. Merge: Combines the processed data from all individual API requests into a single dataset.
  9. Google Sheets (Write Output): Appends the final, structured business contact leads to another specified Google Sheet.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Google Account: For Google Sheets integration.
  • RapidAPI Account and API Key: Access to a Google Maps-related API on RapidAPI. You will need an API key for authentication.
  • Google Sheet for Input: A Google Sheet containing your search queries (e.g., a column for "query" or "location").
  • Google Sheet for Output: A Google Sheet where the extracted leads will be saved.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots next to "New workflow" and select "Import from JSON".
    • Paste the JSON content or upload the file.
  2. Configure Credentials:

    • Google Sheets Node:
      • Click on the "Google Sheets" nodes (both input and output).
      • Add or select your Google Sheets credentials. If creating new credentials, follow the n8n documentation for Google Sheets OAuth setup.
    • HTTP Request Node:
      • Click on the "HTTP Request" node.
      • Configure the authentication for your RapidAPI service. This typically involves adding an X-RapidAPI-Key header and potentially other headers or query parameters as required by the specific RapidAPI endpoint.
  3. Update Google Sheets Node Settings:

    • Google Sheets (Read Input):
      • Specify the Spreadsheet ID and Sheet Name where your search queries are located.
      • Ensure the data is structured correctly for the workflow to read.
    • Google Sheets (Write Output):
      • Specify the Spreadsheet ID and Sheet Name where you want to save the extracted leads.
      • Ensure the sheet has appropriate headers if you want the data to align correctly.
  4. Review and Customize (Optional):

    • Edit Fields (Set Query): Adjust the fields being set if your RapidAPI endpoint requires different parameter names.
    • Code Node: Review the JavaScript code within the "Code" node. This code is crucial for parsing the RapidAPI response. You may need to modify it if the RapidAPI's response structure changes or if you want to extract different data points.
    • Wait Node: Adjust the Wait Time if you need to increase or decrease the delay between API calls.
  5. Execute the Workflow:

    • Click "Save" to save your workflow.
    • Click "Execute Workflow" to run it manually.
    • Monitor the execution to ensure data is being read, processed, and written correctly.

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