Extract Google My Business leads by service or location with Bright Data

1205 views

2/3/2026

Notifications Automation Data Extraction Email Google Forms

📍 Extract Google My Business Leads by Service & Location with Bright Data to Google Sheets

This template requires a self-hosted n8n instance to run.

A comprehensive n8n automation that extracts Google My Business listings by service type and geographic location using Bright Data's Google Maps dataset, with intelligent city expansion and automatic duplicate removal.

👥 Who is this for?

Lead generation professionals
Sales teams
Marketing agencies
Business development representatives
Entrepreneurs conducting outreach or market research

❓ What problem is this solving?

Manual lead generation from Google Maps is time-consuming and inefficient. This workflow automates the process of finding businesses by service type and location, expanding searches across cities, removing duplicates, and organizing results in a structured format.

⚙️ What this workflow does

Input Processing

Accepts service type, state, and country via web form
Uses Claude AI to generate city lists
Auto-categorizes services
Creates search queries per city

Data Collection

Uses Bright Data's Google Maps dataset
Processes in batches with rate limits
Monitors scraping with retry logic
Formats and handles API responses

Quality Control

Removes duplicates by name and phone
Maintains clean data in Google Sheets
Ensures structured, usable datasets

📄 Output Data Points

🚀 Setup Instructions

Prerequisites

n8n instance (self-hosted or cloud)
Google account with Sheets access
Bright Data account with Google Maps dataset access
Anthropic API key for Claude AI

Step-by-Step

Import the workflow JSON into n8n
Configure Bright Data credentials and dataset access
Set up Google Sheets and OAuth2 credentials
Configure Claude AI with your API key
Replace all placeholder credential IDs and tokens. For improved security, use credentials instead of hardcoding the API token placeholder in the HTTP Request node.
Test with sample data (e.g., "Coffee Shop" in California, US)
Activate the workflow and use the form for submissions

🛠 How to Customize

Modify Geographic Scope

Add countries to the form dropdown
Customize Claude prompts for city generation
Adjust search logic for international markets

Enhance Data Collection

Add more fields from Bright Data
Include revenue, employee count, social profiles

Improve Duplicate Detection

Use fuzzy matching for similar names
Include address-based checks

Customize Output Format

Transform data for CRM compatibility
Export to CSV, database, or multiple destinations

Implement Advanced Features

Integrate email finder services
Include lead scoring logic
Discover social media profiles

Batch Processing Optimization

Adjust batch sizes per Bright Data limits
Use parallel processing and retry logic

Integration Options

Connect to CRMs like HubSpot or Salesforce
Trigger email automation
Integrate with marketing platforms

Extract Google My Business Leads by Service or Location with Bright Data

This n8n workflow automates the process of extracting Google My Business (GMB) leads based on specified services or locations. It leverages a Bright Data web scraper through an HTTP Request, processes the results, and then saves the extracted data into a Google Sheet. The workflow is triggered by a form submission, making it easy to initiate lead generation campaigns.

What it does

Triggers on Form Submission: The workflow starts when a user submits data through an n8n form. This form likely contains the search parameters for the GMB leads (e.g., service, location).
Prepares Bright Data Request: It uses a Code node to dynamically construct the payload for the Bright Data API request, incorporating the input from the form trigger.
Initiates Bright Data Scraper: An HTTP Request node sends the prepared payload to the Bright Data API to start a web scraping job for Google My Business data.
Monitors Scraper Job Status: The workflow then enters a loop to repeatedly check the status of the Bright Data scraping job using another HTTP Request node.
Waits for Job Completion: A Wait node introduces a delay between status checks to avoid overwhelming the API and to allow the scraping job to complete.
Retrieves Scraped Data: Once the Bright Data job is complete, another HTTP Request node fetches the final scraped data from Bright Data.
Processes Scraped Data: A Code node is used to parse and transform the raw data received from Bright Data into a structured format suitable for storage.
Splits Data into Batches: The processed data is split into manageable batches using the "Loop Over Items" node (Split in Batches).
Filters Data (Conditional Logic): An If node likely applies conditional logic to filter the scraped data based on specific criteria (e.g., ensuring data quality or relevance).
Saves to Google Sheets: Finally, the filtered and processed lead data is appended to a specified Google Sheet, providing a centralized repository for the extracted leads.

Prerequisites/Requirements

n8n Instance: A running n8n instance to host and execute the workflow.
Bright Data Account: An active Bright Data account with access to a Google My Business scraper. You will need your API key and potentially specific scraper IDs.
Google Account: A Google account with access to Google Sheets. You will need to configure Google Sheets credentials in n8n.
n8n Form Trigger: The workflow is initiated by an n8n Form Trigger. You will need to design this form to capture the necessary inputs for your GMB lead searches.

Setup/Usage

Import the Workflow: Import the provided JSON into your n8n instance.
Configure Credentials:
- Bright Data: Set up an HTTP Request credential for Bright Data, including your API key.
- Google Sheets: Set up Google Sheets OAuth2 credentials in n8n, granting access to your spreadsheets.
Configure Form Trigger (Node 1225 - "On form submission"):
- Customize the form fields to collect the desired search parameters (e.g., "service", "location").
Configure Bright Data HTTP Requests (Nodes 19, 19_1, 19_2):
- Update the URLs and headers with your specific Bright Data API endpoints and authentication details.
- Ensure the payload in the initial HTTP Request (Node 19) correctly references the data from the Form Trigger and the Code node.
Configure Google Sheets Node (Node 18):
- Specify the Spreadsheet ID and Sheet Name where you want the leads to be saved.
- Ensure the "Operation" is set to "Append Row" or similar, and map the incoming data fields to your sheet columns.
Review Code Nodes (Nodes 834, 834_1):
- Examine the JavaScript code to understand how data is transformed and adapted for Bright Data and Google Sheets. Adjust if your data structure or Bright Data API requirements differ.
Review If Node (Node 20):
- Adjust the conditions in the "If" node to match your filtering logic for the scraped GMB data.
Activate the Workflow: Once configured, activate the workflow.
Submit the Form: Access the URL for the "On form submission" trigger and submit your search parameters to initiate the lead extraction.

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.

By 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

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

By Le Nguyen

942