Back to Catalog

Google Maps lead generation with Apify & email extraction for Airtable

Ezema Kingsley ChibuzoEzema Kingsley Chibuzo
1110 views
2/3/2026
Official Page

🧠 What It Does

This n8n workflow collects leads from Google Maps, scrapes their websites via direct HTTP requests, and extracts valid email addresses β€” all while mimicking real user behavior to improve scraping reliability. It rotates User-Agent headers, introduces randomized delays, and refines URLs by removing only query parameters and fragments to preserve valid page paths (like social media links). The workflow blends Apify actors, raw HTTP requests, HTML-to-Markdown conversion, and smart email extraction to deliver clean, actionable lead data β€” ready to be sent to Airtable, Google Sheets, or any CRM. Perfect for lean, scalable B2B lead generation using n8n’s native logic and no external scrapers.

πŸ’‘Why this workflow

Modest lead scrapers rely on heavy tools or APIs like Firecrawl. This workflow:

  • Uses lightweight HTTP requests (with randomized user-agents) to scrape websites.
  • Adds natural wait times to avoid rate limits and IP bans.
  • Avoid full-page crawlers, yet still pulls emails effectively.
  • Works great for freelancers, marketers, or teams targeting niche B2B leads.
  • Designed for stealth and resilience.

πŸ‘€ Who it’s for

  • Lead generation freelancers or consultants.
  • B2B marketers looking to extract real contact info.
  • Small businesses doing targeted outreach.
  • Developers who want a fast, low-footprint scraper.
  • Anyone who wants email + website leads from Google Maps.

βš™οΈ How It Works

1. πŸ“₯ Form Submission (Lead Input)

A Form Trigger collects: - Keyword - Location
- No. of Leads (defaults to 10)

This makes the workflow dynamic and user-friendly β€” ready for multiple use cases and teams.

2. πŸ“Š Scrape Business Info (via Apify)

  • Apify’s Google Maps Actor searches for matching businesses.
  • The Dataset Node fetches all relevant business details.
  • A Set Node parses key fields like name, phone, website, and category.
  • A Limit Node ensures the workflow only processes the desired number of leads.

3. πŸ” First Loop – Visit & Scrape Website

Each business website is processed in a loop.

  • A Code Node cleans the website URL by removing only query parameters/fragments β€” keeping full paths like /contact.
  • A HTTP Request Node fetches the raw HTML of the site:
    • Uses randomized User-Agent headers (5 variants) to mimic real devices and browsers. This makes requests appear more human and reduces the risk of detection or blocking.
  • HTML is converted to Markdown using the Markdown Node, making it easier to scan for text patterns.
  • A Wait Node introduces a random delay between 2-7 seconds:
    • Helps avoid triggering rate limits,
    • Reduces likelihood of being flagged as a bot.
  • A Merge Node combines scraped markdown + lead info for use in the second loop.

4. πŸ” Second Loop – Extract Emails

In this second loop, the markdown data is processed.

  • A Code Node applies regex to extract the first valid email address.
  • If no email is found, "N/A" is returned.
  • A brief 1 second Wait Node simulates realistic browsing time.
  • Another Merge Node attaches the email result to the original lead data.

5. βœ… Filter, Clean & Store

  • A Filter Node removes all entries with "N/A" or invalid email results.
  • A Set Node ensures only required fields (like website, email, and company name) are passed forward.
  • The clean leads are saved to Airtable (or optionally, Google Sheets) using an upsert-style insert to avoid duplicates.

πŸ›‘οΈ Anti-Flagging Design

This workflow is optimized for stealth:

  • No scraping tools or headless browsers (like Puppeteer or Firecrawl).
  • Direct HTTP requests with rotating User-Agents.
  • Randomized wait intervals (2-7s).
  • Only non-intrusive parsing β€” no automation footprints.

πŸ›  How to Set It Up

Open n8n (Cloud or Self-Hosted). Install Apify node

  • search Apify and click on Install. Do this before importing your file.

Import the provided .json file into your n8n editor. Set up the required credentials:

  • πŸ”‘ Apify API Key (used for Google Maps scraping)
  • πŸ”‘ Airtable API Key (or connect Google Sheets instead)

Recommended

  • Prepare your Airtable base or Google Sheet with fields like: Email, Website, Phone, Company Name.
  • Review the Set node if you'd like to collect more fields from Apify (e.g., Ratings, Categories, etc.).

πŸ” Customization Tips

  • The Apify scraper returns rich business data. By default, this workflow collects name, phone, and website β€” but you can add more in the "Grab Desired Fields" node.
  • Need safer scraping at scale? Swap the HTTP Request for Firecrawl’s Single URL scraper (or any headless service like Browserless, Oxylabs, Bright Date, or ScrapingBee) β€” they handle rendering and IP rotation.
  • Want to extract from internal pages (like /contact or /about)? Use Firecrawl’s async crawl mode β€” just note it takes longer.
  • For speed and efficiency, this built-in HTTP + Markdown setup is usually the fastest way to grab emails.

Google Maps Lead Generation with Apify & Email Extraction for Airtable

This n8n workflow automates the process of generating leads from Google Maps, enriching the data with email addresses, and then storing the processed leads in Airtable. It's designed to streamline lead generation for businesses looking to target specific geographical areas and industries.

Description

This workflow simplifies lead generation by integrating Apify for Google Maps data extraction, a custom email extraction service, and Airtable for organized storage. It allows you to define search queries, process the results, and populate your CRM with valuable lead information, including verified email addresses.

What it does

  1. Triggers on Form Submission: The workflow starts when a new form submission is received, likely containing the search query for Google Maps.
  2. Extracts Google Maps Data (Apify): It uses an HTTP Request node to call an Apify actor, specifically the "Google Maps Scraper", to extract business listings based on the provided search query.
  3. Waits for Apify Job Completion: After initiating the Apify job, it enters a loop, periodically checking the job's status via another HTTP Request node until the job is completed. A "Wait" node introduces a delay between checks to avoid excessive API calls.
  4. Fetches Apify Results: Once the Apify job is complete, it retrieves the extracted data using an HTTP Request node.
  5. Limits Results (Optional): A "Limit" node is used to process a specified number of items from the Apify results, useful for testing or managing API usage.
  6. Loops Over Each Result: The workflow then iterates through each business listing obtained from Apify using a "Split in Batches" node.
  7. Extracts Email Addresses: For each business, it makes an HTTP Request to an external email extraction service (likely a custom API or a third-party service) to find associated email addresses.
  8. Merges Data: The extracted email addresses are merged back with the original business data.
  9. Filters Valid Emails: A "Filter" node checks if a valid email address was found.
  10. Prepares Data for Airtable: For items with valid emails, an "Edit Fields (Set)" node transforms and maps the data to match the structure required by Airtable.
  11. Adds Leads to Airtable: Finally, the processed lead information, including the extracted email, is added as a new record to a specified Airtable base.
  12. Generates Markdown Output: A "Markdown" node provides a structured summary of the processed leads.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Apify Account & API Key: An Apify account with access to the "Google Maps Scraper" actor and an API key.
  • Email Extraction Service: Access to an email extraction API or service (e.g., Hunter.io, Dropcontact, or a custom solution). The current workflow uses a generic HTTP Request, implying a custom or self-hosted solution.
  • Airtable Account & API Key: An Airtable account with a base and table configured to store lead data, and a corresponding API key.
  • n8n Form Trigger: The n8n Form Trigger node is used to initiate the workflow, meaning you'll need to create and use the generated form URL.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Apify: Create an HTTP Request credential for Apify using your Apify API token.
    • Email Extraction Service: Configure the HTTP Request node for email extraction with the necessary authentication (API key, bearer token, etc.) for your chosen service.
    • Airtable: Set up an Airtable credential with your API key and base ID.
  3. Update Node Parameters:
    • On form submission: Note the webhook URL generated by this node. You will use this to trigger the workflow.
    • HTTP Request (Apify - Start Scraper): Ensure the actorId and any input parameters for the Google Maps Scraper are correctly configured.
    • HTTP Request (Apify - Check Status): Verify the URL and parameters for checking Apify job status.
    • HTTP Request (Apify - Get Results): Confirm the URL for retrieving Apify job results.
    • Limit: Adjust the Limit value if you want to process a specific number of items.
    • HTTP Request (Email Extraction): Update the URL and request body to correctly send the business website/name to your email extraction service and parse the response.
    • Edit Fields (Set): Map the extracted data to your desired Airtable column names.
    • Airtable: Select your Airtable credential, specify the Base ID, Table Name, and ensure the Fields to Create are correctly mapped from the previous "Edit Fields (Set)" node.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Trigger the Workflow: Submit data to the n8n Form Trigger URL with your Google Maps search query to start the lead generation process.

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