HumationHuman + Automation
Back to Catalog

Auto-collect business leads from Google Maps with APIFY and Gmail

Santhej KalladaSanthej Kallada
368 views
2/3/2026
ExportWebhookData ProcessingFile GenerationCSV
Official Page

Who is this for?

  • Marketers, lead generation agencies, freelancers, consultants, and sales teams who need to collect business leads from Google Maps.
  • Small business owners looking to build targeted local business lists.
  • Anyone interested in automating web scraping without coding skills. What problem is this workflow solving?

Manually scraping business data from Google Maps is time-consuming and repetitive. This automation simplifies the process by:

  • Collecting business details based on search terms and location.
  • Filtering out irrelevant results.
  • Delivering qualified leads directly to your inbox. What this workflow does

This workflow automates Google Maps lead scraping using APIFY and sends the gathered leads via email. The steps include:

  • Collecting user input through a simple form (business type, location, recipient email).
  • Sending an HTTP request to APIFY to run a Google Maps scraper (actor).
  • Filtering results to include only businesses with email addresses.
  • Converting results to CSV format.
  • Sending an automated email with the leads as a CSV attachment via Gmail. Setup
  1. Create an APIFY Account:
  • Sign up at APIFY.COM (https://apify.com/).
  • You get $5 in free credits (~1,000 leads).
  1. Get Your API Key:
  • Copy your API key from APIFY
  1. Prepare n8n:
  • Create a new workflow.
  • Add an HTTP Request node to interact with APIFY.
  • Configure authentication with your API key.
  1. Customize the Form:
  • Build a simple form inside n8n to collect user inputs: Business Type, City, Country, Recipient Email.
  1. Filter Results:
  • Use IF and Filter nodes to remove entries without email addresses.
  1. Convert to CSV:
  • Use a "Spreadsheet File" node to generate a CSV from the filtered leads.
  1. Send Email:

  • Use the Gmail node (or any email node) to send the CSV file to the provided recipient. How to customize this workflow to your needs

  • Change search parameters to target different business niches or locations.

  • Add filters to only include businesses with websites.

  • Customize the email subject and body.

  • Integrate with CRM or marketing platforms for direct lead injection.

  • Expand filtering logic for more refined targeting. Notes

  • This template uses APIFY (paid service after free credits).

  • You will need an APIFY API key and a Gmail account (or SMTP credentials) to run this automation.

  • For self-hosted n8n users: ensure you have internet access and proper credentials set up for external HTTP requests.

Want A Video Tutorial on How To Setup This Automation : https://www.youtube.com/watch?v=Kz_Gfx7OH6o

n8n Workflow: Apify Google Maps Business Lead Collection with Gmail Notification

This n8n workflow automates the process of collecting business leads from Google Maps using Apify and sends a notification email via Gmail upon completion. It allows users to trigger the data collection manually via an n8n form, convert the collected data into a CSV file, and then receive an email with the attached data.

What it does

This workflow simplifies and automates the following steps:

  1. Triggers on Form Submission: The workflow starts when a user submits data through an n8n form. This form likely contains parameters for the Apify Google Maps Scraper (e.g., search query, location).
  2. Initiates Apify Google Maps Scraper: It makes an HTTP request to the Apify API to start a Google Maps Scraper task, using the input provided from the form.
  3. Converts Data to CSV: Once the Apify task is complete and data is retrieved, the workflow converts this data into a CSV file format.
  4. Sends Email Notification: It sends an email via Gmail to a specified recipient (likely the user who triggered the form) with the generated CSV file attached.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Apify Account & API Key: An Apify account with access to the Google Maps Scraper and your Apify API key.
  • Gmail Account: A Gmail account configured as a credential in n8n for sending emails.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Apify: Create an HTTP Request credential in n8n for Apify, using your Apify API key. The "HTTP Request" node (ID 19) will need to be configured with the correct Apify API endpoint and your API key for authentication.
    • Gmail: Configure your Gmail account as a credential in n8n. The "Gmail" node (ID 356) will use this credential to send emails.
  3. Configure the "On form submission" Trigger (ID 1225):
    • Customize the form fields to collect the necessary inputs for your Apify Google Maps Scraper (e.g., searchQuery, location, maxItems).
    • Note the webhook URL provided by the form trigger to integrate it into your desired front-end or manual trigger method.
  4. Configure the "HTTP Request" Node (ID 19):
    • Update the URL to the Apify Google Maps Scraper API endpoint.
    • Ensure the request body correctly passes the parameters from the "On form submission" node to Apify.
    • The node is currently named "HTTP Request" and has n8n-nodes-base.httpRequest type.
  5. Configure the "Convert to File" Node (ID 1234):
    • Ensure this node is correctly configured to convert the output of the Apify HTTP Request node into a CSV file.
    • The node is currently named "Convert to File" and has n8n-nodes-base.convertToFile type.
  6. Configure the "Gmail" Node (ID 356):
    • Set the recipient email address (e.g., an email field from the form submission).
    • Customize the email subject and body.
    • Ensure the CSV file output from the "Convert to File" node is attached to the email.
  7. Activate the Workflow: Once configured, activate the workflow. You can then trigger it by submitting the n8n form.

Note on "Filter" (ID 844) and "Sticky Note" (ID 565) nodes: These nodes are present in the workflow JSON but are not connected to the main flow.

  • The Filter node (ID 844) is intended for conditional logic, allowing you to route data based on specific criteria. If you need to filter Apify results before sending the email, connect this node and define your conditions.
  • The Sticky Note node (ID 565) is typically used for adding comments or documentation within the workflow canvas. It does not perform any operational function.

Related Templates

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 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

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353