Back to Catalog

Extract Business Emails from Google Maps Listings for Lead Generation

Jose CastilloJose Castillo
708 views
2/3/2026
Official Page

This workflow scrapes Google Maps business listings (e.g., carpenters in Tarragona) to extract websites and email addresses — perfect for lead generation, local business prospecting, or agency outreach.

🔧 How it works

Manual Trigger – start manually using the “Test Workflow” button.

Scrape Google Maps – fetches the HTML from a Google Maps search URL.

Extract URLs – parses all business links from the page.

Filter Google URLs – removes unwanted Google/tracking links.

Remove Duplicates + Limit – keeps unique websites (default: 100).

Scrape Site – fetches each website’s HTML.

Extract Emails – detects valid email addresses.

Filter Out Empties & Split Out – isolates each valid email per site.

(Optional) Add to Google Sheet – appends results to your Sheet.

💼 Use cases

Local business leads: find emails of carpenters, dentists, gyms, etc., in your city.

Agency outreach: collect websites and contact emails to pitch marketing services.

B2B prospecting: identify businesses by niche and region for targeted campaigns.

🧩 Requirements

n8n instance with HTTP Request and Code nodes enabled.

(Optional) Google Sheets OAuth2 credentials.

Tip: Add a “Google Sheets → Append Row” node and connect it to your account.

🔒 Security

No personal or sensitive data included — only credential references. If sharing this workflow, anonymize the “credentials” field before publishing.

Extract Business Emails from Google Maps Listings for Lead Generation

This n8n workflow automates the process of extracting business emails from Google Maps listings, making it an efficient tool for lead generation. It takes a list of business names and locations, searches Google Maps for them, extracts relevant details including email addresses, and then compiles this data into a Google Sheet.

What it does

  1. Manual Trigger: Initiates the workflow upon manual execution.
  2. Google Sheets (Read Data): Reads a list of business names and locations from a specified Google Sheet.
  3. Loop Over Items (Split in Batches): Processes the businesses from the Google Sheet in batches to manage API request limits and ensure stability.
  4. Wait: Pauses the workflow for a specified duration (e.g., 5 seconds) between batches to avoid overwhelming APIs and respect rate limits.
  5. HTTP Request (Google Maps Search): Sends an HTTP request to a Google Maps scraping API (e.g., SerpApi, Bright Data, or a custom solution) to search for each business based on its name and location.
  6. Code (Extract Email): Executes custom JavaScript code to parse the JSON response from the Google Maps search, specifically looking for and extracting email addresses from the listing details.
  7. Filter (Email Found): Checks if an email address was successfully extracted for the current business.
  8. Google Sheets (Write Data - Email Found): If an email is found, the business name, location, and extracted email are appended to a specified "Found Emails" Google Sheet.
  9. Google Sheets (Write Data - No Email): If no email is found, the business name and location are appended to a separate "No Emails Found" Google Sheet, allowing for further manual investigation if needed.
  10. Remove Duplicates: Ensures that only unique email addresses are recorded in the "Found Emails" sheet.
  11. Limit: (Potentially) Limits the number of items processed to manage workflow execution time or testing.
  12. Split Out: (Potentially) Splits out items from an array into individual items for further processing.
  13. Sticky Note: Provides a descriptive note within the workflow for clarity.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host and execute the workflow.
  • Google Sheets Account: Access to Google Sheets to store input data (business names, locations) and output data (found emails, businesses without emails).
  • Google Sheets Credentials: Configured Google Sheets OAuth2 or Service Account credentials in n8n.
  • Google Maps Scraping API Key: An API key for a Google Maps scraping service (e.g., SerpApi, Bright Data, or a similar provider) that can programmatically search Google Maps and return detailed business information. The HTTP Request node will need to be configured with the endpoint and authentication for this 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 credentials (OAuth2 or Service Account) in n8n.
    • Configure the HTTP Request node with your chosen Google Maps scraping API's endpoint and API key/authentication method.
  3. Prepare Input Google Sheet:
    • Create a Google Sheet with at least two columns: "Business Name" and "Location".
    • Populate this sheet with the businesses you want to find emails for.
    • Update the "Google Sheets (Read Data)" node to point to this input sheet and the correct range.
  4. Prepare Output Google Sheets:
    • Create two new Google Sheets: one for "Found Emails" and one for "No Emails Found".
    • Update the "Google Sheets (Write Data - Email Found)" and "Google Sheets (Write Data - No Email)" nodes to point to these respective output sheets. Ensure the column headers in your output sheets match the data being written (e.g., "Business Name", "Location", "Email").
  5. Review and Customize (Optional):
    • Adjust the "Wait" node's duration if you experience rate limit issues or want to speed up/slow down the process.
    • Modify the "Code (Extract Email)" node if your chosen Google Maps scraping API returns data in a different format, or if you want to extract additional information.
    • Adjust the batch size in the "Loop Over Items" node if needed.
  6. Execute the workflow: Click "Execute Workflow" in the "Manual Trigger" node to start the process.

The workflow will then read your businesses, search Google Maps, extract emails, and populate your output Google Sheets with the results.

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

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

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