HumationHuman + Automation
Back to Catalog

Generate business lists from Google Maps search to Sheets or Excel with Serper

AndrewAndrew
72 views
2/3/2026
WebhookHubSpotData TransformationHTTP RequestNext.js
Official Page

Who is this for

This workflow is ideal for lead generation agencies, researchers, and small business owners who need to quickly collect and analyze company data from search results and save them into Google Sheets for further use.

What problem is this workflow solving

Manually searching for companies, compiling them into a list, and formatting them into spreadsheets is time-consuming and error-prone. This workflow automates that process-taking a search request, finding relevant companies, and organizing the data into a ready-to-use format in Google Sheets or downloadable Excel.

What this workflow does

  • Takes a user’s search query via chat
  • Scrapes company data from Google Maps based on that query
  • Returns the results in a downloadable Excel file
  • Saves the same data to a connected Google Sheets document for easy access and sharing.

Setup

  • Add your credentials:
    • Gogle Sheets
    • Serper
  • Run the workflow and enter your search request in the chat interface
  • Retrieve your results from either:
    • The Get XLSX node as an Excel file
    • The linked Google Sheets file (copy Column Names from XLSX File to Google Sheets)
  • Test the bot by sending a search query (e.g., "coffee shops in Berlin") - the bot will return the results automatically.

Generate Business Lists from Google Maps Search to Sheets or Excel with Serper

This n8n workflow automates the process of extracting business information from Google Maps search results and saving it into a Google Sheet or an Excel/CSV file. It's designed to help you quickly build targeted business lists based on specific search queries.

What it does

This workflow performs the following key steps:

  1. Triggers on Chat Message: The workflow is initiated when a chat message is received. This allows for interactive triggering, potentially by providing search parameters directly through a chat interface.
  2. Performs Google Maps Search: It likely uses an HTTP Request node to interface with a search API (e.g., Serper API, as hinted by the directory name) to query Google Maps for businesses based on the input from the chat trigger.
  3. Processes Search Results: The raw data from the search API is then processed. An "Edit Fields (Set)" node is used to transform or extract relevant data points from the search results.
  4. Splits Out Items: A "Split Out" node is used to handle arrays of results, ensuring each business entry is processed individually.
  5. Saves to Google Sheets: The extracted business data is then appended or written to a specified Google Sheet.
  6. Converts to File (Optional/Alternative Output): Optionally, the processed data can be converted into a file format (like CSV or Excel), allowing for flexible output beyond Google Sheets. This suggests the workflow supports both direct Google Sheets integration and file export.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Account: For Google Sheets integration, you'll need a Google account with access to Google Sheets.
  • Google Sheets Credential: An n8n Google Sheets credential configured to access your Google Sheets.
  • Serper API Key (or similar search API): The workflow likely uses an external search API to query Google Maps. While not explicitly visible in the JSON, the "HTTP Request" node and the directory name suggest a need for an API like Serper for Google Maps data. You will need an API key for this service.
  • Chat Integration: The "Chat Trigger" node implies integration with a chat platform (e.g., Slack, Telegram, Discord) to initiate the workflow. You will need to configure this trigger according to your chosen chat 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 credential in n8n.
    • Configure the HTTP Request node with your Serper API key (or other Google Maps search API) and the necessary API endpoint details.
    • Configure the Chat Trigger node to connect to your desired chat platform.
  3. Customize Search Query: The "Chat Trigger" node will likely pass the search query to the "HTTP Request" node. Adjust how the query is extracted from the chat message if needed.
  4. Configure Google Sheets Node:
    • Specify the Spreadsheet ID and Sheet Name where you want to save the business data.
    • Ensure the column headers in your Google Sheet match the data being output by the "Edit Fields (Set)" node.
  5. Configure Convert to File Node (Optional): If you intend to export to a file, configure the output format and how the file should be handled (e.g., saved to a cloud storage, sent via email).
  6. Activate the Workflow: Once configured, activate the workflow.
  7. Trigger the Workflow: Send a chat message to the configured chat trigger to initiate a Google Maps search and generate your business list.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616