Automated local business lead generation with Google Maps & GPT-4
AI-Powered Local Lead Generation Workflow with n8n
This workflow solves one of the biggest pain points for freelancers, agencies, and SaaS foundersโfinding accurate local business leads at scale without manual copy-pasting or unreliable scraping tools.
Traditional lead generation is time-consuming and prone to errors.
This template automates the entire process so you can focus on outreach, not data gathering.
โ What the Workflow Does
- Accepts a business type (e.g.,
plumbers) and city (e.g.,Los Angeles) as input - Uses AI to generate hyperlocal search terms for full neighborhood coverage
- Scrapes Google Maps results to extract business details and websites
- Filters out junk, Google-owned links, and duplicates
- Scrapes homepage HTML for each business and extracts valid emails using Regex
- Outputs a clean, deduplicated lead list with business names, websites, and emails
๐ Everything Runs Inside n8n With:
- OpenAI for AI-driven query generation
- Zyte API for reliable scraping
- JavaScript functions for email extraction
- Built-in filtering and batching for clean results
๐ฅ Who is This For?
- Marketing agencies doing local outreach
- Freelancers offering SEO, design, or lead gen services
- SaaS founders targeting SMBs
- Sales teams scaling outbound campaigns
โ Requirements
- n8n account (Cloud or self-hosted)
- OpenAI API key (stored in n8n credentials)
- Zyte API key (stored securely)
- Basic familiarity with Google Sheets if you want to export results
โ๏ธ How to Set Up
- Import the workflow JSON into n8n
- Go to Credentials in n8n and add OpenAI and Zyte API keys
- Replace placeholder credential references in the HTTP Request nodes
- Set your search parameters (business type and city) in the designated Set node
- Test the workflow with a single search to confirm scraping and email extraction steps
- Configure batching if you plan to scrape multiple neighborhoods
- Add an output step (Google Sheets, Airtable, or CRM) to store your leads
๐ง How to Customize
- Update the OpenAI prompt for different search formats (e.g.,
service + zip code) - Adjust the Regex pattern in the JavaScript node for additional email validation rules
- Add extra filtering logic for niche-specific keywords
- Integrate with Instantly, HubSpot, or any email-sending tool for full automation
Automated Local Business Lead Generation with Google Maps & GPT-4
This n8n workflow automates the process of generating leads for local businesses by leveraging Google Maps data and enriching it with AI-powered insights from GPT-4. It streamlines the discovery, qualification, and data enhancement of potential business leads.
What it does
This workflow performs the following key steps:
- Manual Trigger: Initiates the workflow manually, allowing you to control when the lead generation process starts.
- HTTP Request: Fetches raw business data from a specified API endpoint, likely a Google Maps or similar local business data provider.
- Edit Fields (Set): Transforms and prepares the raw data for further processing, potentially renaming fields or extracting specific values.
- Loop Over Items (Split in Batches): Processes the retrieved business data in manageable batches, ensuring efficient handling of large datasets.
- Wait: Introduces a delay between batches, which can be useful for respecting API rate limits or managing workflow load.
- Limit: Restricts the number of items processed, allowing for testing or focusing on a specific subset of leads.
- Remove Duplicates: Ensures that each business lead is unique, preventing redundant processing and data.
- Split Out: Separates nested data structures into individual items for easier manipulation.
- Code: Executes custom JavaScript code to further process or transform the data, offering flexibility beyond standard nodes.
- Filter: Applies conditions to filter out businesses that do not meet specific criteria, helping to qualify leads.
- Basic LLM Chain (Langchain): Utilizes a Langchain LLM (Large Language Model) to process and understand the business data.
- OpenAI Chat Model (Langchain): Specifically uses an OpenAI Chat Model (like GPT-4) to generate insights, summaries, or other enriched data points for each business.
- Structured Output Parser (Langchain): Parses the output from the OpenAI Chat Model into a structured format (e.g., JSON), making it easy to use in subsequent steps.
- Sticky Note: Provides a place for notes or comments within the workflow, aiding documentation and understanding.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- API Key for Google Maps (or similar local business data provider): An API key for the service used in the "HTTP Request" node to fetch business data.
- OpenAI API Key: An API key for OpenAI to utilize their Chat Model (e.g., GPT-4) for lead enrichment.
- Langchain Integration: Ensure the
@n8n/n8n-nodes-langchainpackage is installed and configured in your n8n instance.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up credentials for your Google Maps (or equivalent) API in the "HTTP Request" node.
- Configure your OpenAI API key within the "OpenAI Chat Model" node.
- Customize HTTP Request: Adjust the URL and parameters in the "HTTP Request" node to target your desired geographical area and business categories on Google Maps.
- Refine Filters: Modify the "Filter" node to define your specific lead qualification criteria (e.g., minimum rating, specific keywords in description).
- Adjust LLM Prompts: Customize the prompts within the "Basic LLM Chain" and "OpenAI Chat Model" nodes to guide the AI in generating the desired insights (e.g., "Summarize business services," "Identify unique selling points").
- Run the Workflow: Execute the workflow manually using the "When clicking โExecute workflowโ" trigger.
- Review Outputs: Inspect the output of the final nodes to see the enriched lead data. You can then integrate this data with other systems (e.g., CRM, Google Sheets) using additional n8n nodes.
Related Templates
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.
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use โ Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns Youโll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this โค sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
๐ Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. ๐๐๐ฌ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. ๐งฉ Step 2: Fetches release metadata including version, tag, and publish date. ๐ฆ Step 3: Logs release data into Google Sheets for record-keeping and analysis. ๐ Step 4: Retrieves FAQ or documentation data from Notion. ๐ Step 5: Merges GitHub and Notion data to calculate documentation drift. ๐ Step 6: Flags SDKs whose documentation is over 30 days out of date. โ ๏ธ Step 7: Sends detailed Slack alerts to notify responsible teams. ๐ Key Benefits โ Keeps SDK documentation aligned with product releases โ Prevents outdated information from reaching users โ Provides centralized release tracking in Google Sheets โ Sends real-time Slack alerts for overdue updates โ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.