HumationHuman + Automation
Back to Catalog

Restaurant lead generation from Google Maps with Apify, Airtable & AI newsletter

Pramod RathourePramod Rathoure
569 views
2/3/2026
Google DriveAutomationFilesEmailAttachment
Official Page

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

🚀 Automating Google Maps Lead Generation with n8n + Apify

Finding quality leads can be time-consuming. What if you could scrape restaurant data from Google Maps, filter the best ones, and email a Morning Brew–style newsletter automatically?

That’s exactly what this n8n workflow does.

🔎 What This Workflow Does

  • Takes a location input (Bangkok or Bareilly in this case)
  • Runs a Google Maps scraper via Apify Actor
  • Extracts restaurant essentials (name, category, rating, reviews, address, phone, Google Maps link)
  • Sorts & filters results (only high-review, highly-rated places)
  • Saves data to Airtable for lead management
  • Uses AI to generate a newsletter in a Morning Brew–style HTML email
  • Emails the newsletter automatically to your chosen recipients

🛠️ Workflow Breakdown

1. Form Trigger

  • User selects location from a dropdown (Bangkok or Bareilly)
  • Submits form to kickstart the process

2. Google Maps Scraper

  • Powered by Apify
  • Collects up to 1,000 restaurants with details:
    • Name
    • Category
    • Price Range
    • Rating
    • Reviews
    • Address
    • Phone
    • Google Maps URL
  • Skips closed places and pulls detailed contact data

3. Extract & Transform Data

  • n8n Set node extracts only the essentials
  • Formats them into a clean text block (Restaurant_Data)

4. Sort & Filter

  • Sorted by:
    • Review Count (descending)
    • Rating (descending)
  • Filter: Only restaurants with 500+ reviews

5. Airtable Lead Storage

  • Each record is saved to Google Map Leads - Restaurants Airtable table
  • Fields include:
    • Title
    • Category
    • Price Range
    • Rating
    • Review Count
    • Address
    • Phone
    • Location

6. AI-Powered Newsletter

  • n8n’s LangChain + OpenAI node generates an HTML newsletter
  • Tone: Breezy, witty, like Morning Brew
  • Content: Sorted restaurant picks with ratings, reviews, and contact links
  • Output is JSON with "Subject" and "Body"

7. Automatic Email

  • Gmail node sends the newsletter directly to your inbox
  • Example recipient: prath002@gmail.com

🎯 Why This Workflow Rocks

  • End-to-End Automation: From scraping → filtering → emailing, no manual effort
  • Lead Enrichment: Only keeps high-quality restaurants with strong social proof
  • Scalable: Works for any city you plug into the form
  • Engaging Output: AI crafts the results into a ready-to-send newsletter

🔮 Next Steps

  • Add more cities to the dropdown for multi-location scraping
  • Customize the email template for branding
  • Integrate with CRM tools for automated outreach

👉 With just a few clicks, you can go from raw Google Maps data → polished newsletter → fresh leads in Airtable.

That’s the power of n8n + Apify + AI.

n8n Restaurant Lead Generation and AI Newsletter Workflow

This n8n workflow automates the process of generating leads for restaurants from Google Maps data, enriching that data, and then using AI to create personalized newsletter content. It leverages Apify for data extraction, Airtable for storage, and OpenAI for content generation, with Gmail for sending the final newsletter.

What it does

This workflow streamlines several key tasks:

  1. Triggers on Form Submission: The workflow starts when a new request is submitted via an n8n form.
  2. Retrieves Data from Airtable: It fetches existing restaurant data from a specified Airtable base.
  3. Applies Conditional Logic:
    • If there's no data from Airtable, it proceeds to a "No Operation" step (which can be customized for initial setup or error handling).
    • If data exists, it sorts the data.
  4. Edits Fields (Set): This node is present but not connected in the provided JSON, suggesting it might be a placeholder for future data manipulation or an incomplete part of the workflow.
  5. Aggregates Data: It combines data from previous steps, likely preparing it for further processing.
  6. Generates AI Content: An AI Agent node, powered by an OpenAI Chat Model and a Structured Output Parser, is used to generate content. This is likely where the personalized newsletter content is created based on the restaurant data.
  7. Sends Email via Gmail: The final step sends the generated content as an email using Gmail.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Airtable Account: With a base and table configured to store restaurant lead data.
  • OpenAI API Key: For the AI Agent and OpenAI Chat Model nodes to generate content.
  • Gmail Account: Configured as a credential in n8n for sending emails.
  • Apify Account (Implied): While not directly present in the provided JSON, the directory name "restaurant-lead-generation-from-google-maps-with-apify" strongly suggests that an Apify node would be used upstream to extract Google Maps data. This workflow appears to start after the data extraction, assuming the data is already in Airtable or passed through the trigger.

Setup/Usage

  1. Import the Workflow: Download the JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Airtable credential with access to your restaurant lead base.
    • Set up your OpenAI API Key credential.
    • Set up your Gmail credential.
  3. Configure Nodes:
    • On form submission (Node 1225): Configure the form fields if you intend to pass initial parameters or triggers into the workflow.
    • Airtable (Node 2): Specify your Airtable Base ID and Table Name to retrieve existing restaurant data.
    • AI Agent (Node 1119), OpenAI Chat Model (Node 1153), and Structured Output Parser (Node 1179): Configure the AI prompts, model settings, and desired output structure for your newsletter content generation.
    • Gmail (Node 356): Configure the recipient, subject, and body of the email, referencing the output from the AI Agent node for dynamic content.
  4. Activate the Workflow: Once configured, activate the workflow to start processing form submissions and generating newsletters.
  5. Integrate Apify (Optional, but Recommended for full solution): If you want to use Apify for lead generation, you would typically have an upstream workflow or process that populates the Airtable base (or directly triggers this workflow with data) using Apify's Google Maps Scraper.

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