HumationHuman + Automation
Back to Catalog

AI-powered Google Maps business scraper with enrichment & export to sheets

Msaid Mohamed el hadiMsaid Mohamed el hadi
2561 views
2/3/2026
YouTubeAutomationRSSAPIData Enrichment
Official Page

Overview

This workflow automates the discovery, extraction, enrichment, and storage of business information from Google Maps search queries using AI tools, scrapers, and Google Sheets.

It is ideal for:

  • Lead generation agencies
  • Local business researchers
  • Digital marketing firms
  • Automation & outreach specialists

🔧 Tools & APIs Used

  • Google Maps Search (via HTTP)
  • Custom JavaScript Parsing
  • URL Filtering & De-duplication
  • Google Sheets (Read/Write)
  • APIFY Actor for business scraping
  • LangChain AI Agent (OpenRouter - Gemini 2.5)
  • n8n Built-in Logic (Loops, Conditions, Aggregators)

🧠 Workflow Summary

  1. Trigger The automation starts via schedule (every hour).

  2. Read Queries from Google Sheet Loads unprocessed keywords from a Google Sheet tab named keywords.

  3. Loop Through Keywords Each keyword is used to search Google Maps for relevant businesses.

  4. Extract URLs JavaScript parses HTML to find all external website URLs from the search results.

  5. Clean URLs Filters out irrelevant domains (e.g., Google-owned, example.com, etc.), and removes duplicates.

  6. Loop Through URLs For each URL:

    • Checks if it already exists in the Google Sheet (to prevent duplication).

    • Calls the APIFY Actor to extract full business data.

    • Optionally uses AI Agent (Gemini) to provide detailed insight on the business, including:

      • Services, About, Market Position, Weaknesses, AI suggestions, etc.

    • Converts the AI result (text) to a structured JSON object.

  7. Save to Google Sheet Adds all extracted and AI-enriched business information to a separate tab (Sheet1).

  8. Mark Queries as Processed Updates the original row in keywords to avoid reprocessing.

🗃️ Output Fields Saved

The following information is saved per business:

  • Business Name, Website, Email, Phone
  • Address, City, Postal Code, Country, Coordinates
  • Category, Subcategory, Services
  • About Us, Opening Hours, Social Media Links
  • Legal Links (Privacy, Terms)
  • Logo, Languages, Keywords
  • AI-Generated Description
  • Google Maps URL

📈 Use Cases

  • Build a prospect database for B2B cold outreach.
  • Extract local SEO insights per business.
  • Feed CRMs or analytics systems with enriched business profiles.
  • Automate market research for regional opportunity detection.

📩 Want a Similar Workflow?

If you’d like a custom AI-powered automation like this for your business or agency, feel free to contact me:

📧 msaidwolfltd@gmail.com

AI-Powered Google Maps Business Scraper with Enrichment & Export to Sheets

This n8n workflow provides a robust solution for scraping business data from Google Maps, enriching it with AI, and exporting the results to a Google Sheet. It's designed to be flexible, allowing for scheduled execution and processing of large datasets in batches.

What it does

This workflow automates the following steps:

  1. Triggers on Schedule or Sub-workflow Call: It can be initiated manually, on a set schedule (e.g., daily, weekly), or by another n8n workflow, making it highly adaptable for various use cases.
  2. Scrapes Google Maps Data: It uses an HTTP Request node to interact with a Google Maps scraping API. This node is configured to fetch business details based on predefined search parameters (likely location, keywords, etc., which would be configured within the HTTP Request node).
  3. Processes Data in Batches: To handle potentially large volumes of data efficiently and avoid API rate limits, the workflow splits the scraped items into manageable batches.
  4. Enriches Data with AI: For each item in a batch, it executes a sub-workflow. This sub-workflow likely contains an "AI Agent" and an "OpenRouter Chat Model" to perform enrichment tasks, such as:
    • Analyzing business descriptions.
    • Extracting key information (e.g., services, unique selling propositions).
    • Categorizing businesses.
    • Generating summaries or insights.
  5. Handles AI Processing Delays: A "Wait" node is included within the sub-workflow to introduce a delay between AI processing requests, preventing API overload and ensuring stable operation.
  6. Merges Enriched Data: After the sub-workflow completes its AI enrichment for a batch, the main workflow merges the results back together.
  7. Filters Data: It applies a filter to the processed data, likely to remove irrelevant entries or focus on specific criteria after enrichment.
  8. Removes Duplicates: Ensures data quality by identifying and removing any duplicate entries that might have occurred during scraping or processing.
  9. Aggregates Data: Combines and structures the final, enriched data into a coherent format.
  10. Exports to Google Sheets: The final, cleaned, and enriched business data is then written to a specified Google Sheet, providing an organized and accessible output.
  11. Provides Workflow Notes: Includes sticky notes for documentation and clarity within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Google Sheets Account: To store the scraped and enriched business data. You'll need to configure Google Sheets credentials in n8n.
  • Google Maps Scraping API Key/Endpoint: Access to a Google Maps scraping API (e.g., SerpApi, Bright Data, custom solution). The HTTP Request node will need to be configured with the appropriate URL, headers, and parameters.
  • OpenRouter API Key: For the AI enrichment steps. You'll need to configure OpenRouter credentials in n8n.
  • AI Agent Configuration: The "AI Agent" node will require specific configurations (e.g., prompt, tools) depending on the desired enrichment tasks.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your OpenRouter credentials.
    • Configure any necessary API keys or authentication for the Google Maps Scraping API within the HTTP Request node.
  3. Customize the HTTP Request Node:
    • Update the URL and parameters in the HTTP Request node to target your desired Google Maps search (e.g., "restaurants in New York", "plumbers in London").
    • Adjust headers and authentication as required by your chosen scraping API.
  4. Configure the AI Sub-workflow (Execute Workflow):
    • The Execute Workflow node calls a sub-workflow for AI enrichment. You will need to ensure this sub-workflow exists and is configured correctly with the AI Agent and OpenRouter Chat Model nodes.
    • Customize the AI Agent and OpenRouter Chat Model within the sub-workflow to perform the specific data enrichment you need (e.g., "Summarize business description", "Extract services offered").
    • Adjust the Wait node in the sub-workflow if you need to modify the delay between AI requests.
  5. Adjust Batch Size: Modify the Loop Over Items (Split in Batches) node to control how many items are processed in each batch. This helps manage API limits and processing time.
  6. Refine Filters: Update the Filter node to include any specific conditions you want to apply to the scraped data.
  7. Specify Google Sheet Output: In the Google Sheets node, select the spreadsheet and sheet where you want to export the data. Ensure the column mapping is correct.
  8. Activate the workflow: Once configured, activate the workflow. You can trigger it manually or set up a schedule using the Schedule Trigger node.

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