Lead workflow: Yelp & Trustpilot scraping + OpenAI analysis via BrightData
π Lead Workflow: Yelp & Trustpilot Scraping + OpenAI Analysis via BrightData
> Description: Automated lead generation workflow that scrapes business data from Yelp and Trustpilot based on location and category, analyzes credibility, and sends personalized outreach emails using AI.
> β οΈ Important: This template requires a self-hosted n8n instance to run.
π Overview
This workflow provides an automated lead generation solution that identifies high-quality prospects from Yelp and Trustpilot, analyzes their credibility through reviews, and sends personalized outreach emails. Perfect for digital marketing agencies, sales teams, and business development professionals.
β¨ Key Features
-
π― Smart Location Analysis
AI breaks down cities into sub-locations for comprehensive coverage -
π Yelp Integration
Scrapes business details using BrightData's Yelp dataset -
β Trustpilot Verification
Validates business credibility through review analysis -
π Data Storage
Automatically saves results to Google Sheets -
π€ AI-Powered Outreach
Generates personalized emails using Claude AI -
π§ Automated Sending
Sends emails directly through Gmail integration
π How It Works
- User Input: Submit location, country, and business category through a form
- AI Location Analysis: Gemini AI identifies sub-locations within the specified area
- Yelp Scraping: BrightData extracts business information from multiple locations
- Data Processing: Cleans and stores business details in Google Sheets
- Trustpilot Verification: Scrapes reviews and company details for credibility check
- Email Generation: Claude AI creates personalized outreach messages
- Automated Outreach: Sends emails to qualified prospects via Gmail
π Data Output
| Field | Description | Example | |---------------|----------------------------------|----------------------------------| | Company Name | Business name from Yelp/Trustpilot | Best Local Restaurant | | Website | Company website URL | https://example-restaurant.com | | Phone Number | Business contact number | (555) 123-4567 | | Email | Business email address | demo@example.com | | Address | Physical business location | 123 Main St, City, State | | Rating | Overall business rating | 4.5/5 | | Categories | Business categories/tags | Restaurant, Italian, Fine Dining |
π Setup Instructions
β±οΈ Estimated Setup Time: 10β15 minutes
Prerequisites
- n8n instance (self-hosted or cloud)
- Google account with Sheets access
- BrightData account with Yelp and Trustpilot datasets
- Google Gemini API access
- Anthropic API key for Claude
- Gmail account for sending emails
Step 1: Import the Workflow
- Copy the JSON workflow code
- In n8n: Workflows β + Add workflow β Import from JSON
- Paste JSON and click Import
Step 2: Configure Google Sheets Integration
- Create two Google Sheets:
- Yelp data:
Name, Categories, Website, Address, Phone, URL, Rating - Trustpilot data:
Company Name, Email, Phone Number, Address, Rating, Company About
- Yelp data:
- Copy Sheet IDs from URLs
- In n8n: Credentials β + Add credential β Google Sheets OAuth2 API
- Complete OAuth setup and test connection
- Update all Google Sheets nodes with your Sheet IDs
Step 3: Configure BrightData
- Set up BrightData credentials in n8n
- Replace API token with:
BRIGHT_DATA_API_KEY - Verify dataset access:
- Yelp dataset:
gd_lgugwl0519h1p14rwk - Trustpilot dataset:
gd_lm5zmhwd2sni130p
- Yelp dataset:
- Test connections
Step 4: Configure AI Models
-
Google Gemini (Location Analysis)
- Add Google Gemini API credentials
- Configure model:
models/gemini-1.5-flash
-
Claude AI (Email Generation)
- Add Anthropic API credentials
- Configure model:
claude-sonnet-4-20250514
Step 5: Configure Gmail Integration
- Set up Gmail OAuth2 credentials in n8n
- Update "Send Outreach Email" node
- Test email sending
Step 6: Test & Activate
- Activate the workflow
- Test with sample data:
- Country: United States
- Location: Dallas
- Category: Restaurants
- Verify data appears in Google Sheets
- Check that emails are generated and sent
π Usage Guide
Starting a Lead Generation Campaign
- Access the form trigger URL
- Enter your target criteria:
- Country: Target country
- Location: City or region
- Category: Business type (e.g., restaurants)
- Submit the form to start the process
Monitoring Results
- Yelp Data Sheet: View scraped business information
- Trustpilot Sheet: Review credibility data
- Gmail Sent Items: Track outreach emails sent
π§ Customization Options
Modifying Email Templates
Edit the "AI Generate Email Content" node to customize:
- Email tone and style
- Services mentioned
- Call-to-action messages
- Branding elements
Adjusting Data Filters
- Modify rating thresholds
- Set minimum review counts
- Add geographic restrictions
- Filter by business size
Scaling the Workflow
- Increase batch sizes
- Add delays between requests
- Use parallel processing
- Add error handling
π¨ Troubleshooting
Common Issues & Solutions
1. BrightData Connection Failed
- Cause: Invalid API credentials or dataset access
- Solution: Verify credentials and dataset permissions
2. No Data Extracted
- Cause: Invalid location or changed page structure
- Solution: Verify location names and test other categories
3. Gmail Authentication Issues
- Cause: Expired OAuth tokens
- Solution: Re-authenticate and check permissions
4. AI Model Errors
- Cause: API quota exceeded or invalid keys
- Solution: Check usage limits and API key
Performance Optimization
- Rate Limiting: Add delays
- Error Handling: Retry failed requests
- Data Validation: Check for malformed data
- Memory Management: Process in smaller batches
π Use Cases & Examples
1. Digital Marketing Agency Lead Generation
- Goal: Find businesses needing marketing
- Target: Restaurants, retail stores
- Approach: Focus on good-rated but low-online-presence businesses
2. B2B Sales Prospecting
- Goal: Find software solution clients
- Target: Growing businesses
- Approach: Focus on recent positive reviews
3. Partnership Development
- Goal: Find complementary businesses
- Target: Established businesses
- Approach: Focus on reputation and satisfaction scores
β‘ Performance & Limits
Expected Performance
- Processing Time: 5β10 minutes/location
- Data Accuracy: 90%+
- Success Rate: 85%+
- Daily Capacity: 100β500 leads
Resource Usage
- API Calls: ~10β20 per business
- Storage: Minimal (Google Sheets)
- Execution Time: 3β8 minutes/10 businesses
- Network Usage: ~5β10MB/business
π€ Support & Community
Getting Help
- n8n Community Forum: community.n8n.io
- Docs: docs.n8n.io
- BrightData Support: Via dashboard
Contributing
- Share improvements
- Report issues and suggestions
- Create industry-specific variations
- Document best practices
> π Privacy & Compliance: Ensure GDPR/CCPA compliance. Always respect robots.txt and terms of service of scraped sites.
π― Ready to Generate Leads!
This workflow provides a complete solution for automated lead generation and outreach. Customize it to fit your needs and start building your pipeline today!
For any questions or support, please contact:
π§ info@incrementors.com
or fill out this form: Contact Us
n8n Lead Workflow: Yelp/Trustpilot Scraping & OpenAI Analysis
This n8n workflow automates the process of collecting lead information, enriching it with data scraped from Yelp and Trustpilot, and then analyzing the collected data using an AI agent (either Anthropic Claude or Google Gemini) to identify potential leads. Finally, it sends an email notification with the analysis results.
What it does
- Triggers on Form Submission: The workflow starts when a new entry is submitted via an n8n form.
- Reads Data from Google Sheets: It fetches additional lead data from a specified Google Sheet.
- Loops Over Items: Processes each lead individually or in batches.
- Scrapes Yelp and Trustpilot (HTTP Requests): For each lead, it makes HTTP requests to Bright Data's Web Scraper API to scrape review data from Yelp and Trustpilot based on provided URLs.
- Analyzes with AI Agent: It then uses an AI Agent (configured with either Anthropic Chat Model or Google Gemini Chat Model) to analyze the scraped data and the initial lead information. The AI agent is designed to determine if the lead is "good" or "bad" and provide a reason for its decision.
- Conditional Logic (If Node): Based on the AI agent's analysis, it checks if the lead is classified as "good".
- Sends Email Notification: If the lead is classified as "good", it sends an email via Gmail with the AI's analysis and the scraped data.
- Waits (Optional): Includes a wait step, potentially for rate limiting or to introduce a delay between processing leads.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Google Sheets Account: Configured credentials for Google Sheets to read lead data.
- Bright Data Account: API credentials for Bright Data's Web Scraper API to perform web scraping.
- OpenAI API Key (or Anthropic/Google Gemini API Key):
- Anthropic Account: API credentials for Anthropic (e.g., Claude) if using the Anthropic Chat Model.
- Google Account: API credentials for Google Gemini if using the Google Gemini Chat Model.
- Gmail Account: Configured credentials for Gmail to send email notifications.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets credentials.
- Set up your Bright Data credentials for the HTTP Request nodes.
- Set up your Anthropic or Google Gemini credentials for the respective AI Chat Model nodes.
- Set up your Gmail credentials.
- Configure "Google Sheets" Node (ID: 18):
- Specify the Google Sheet ID and the range or sheet name where your lead data is stored.
- Configure "On form submission" Node (ID: 1225):
- Customize the form fields as needed to collect initial lead information.
- Configure "HTTP Request" Nodes (ID: 19):
- Update the Bright Data API endpoints and parameters (e.g., target URLs for Yelp and Trustpilot) to match your scraping requirements. Ensure the URLs are dynamically pulled from the incoming lead data.
- Configure "AI Agent" Node (ID: 1119):
- Select your preferred Language Model (Anthropic Chat Model or Google Gemini Chat Model).
- Review and adjust the prompt for the AI Agent to ensure it correctly identifies "good" leads based on your criteria. The prompt should instruct the AI to analyze the scraped Yelp and Trustpilot data along with the initial lead information.
- Configure "If" Node (ID: 20):
- Adjust the condition to evaluate the output from the "AI Agent" node to determine if a lead is "good" (e.g.,
{{ $json.isGoodLead === true }}).
- Adjust the condition to evaluate the output from the "AI Agent" node to determine if a lead is "good" (e.g.,
- Configure "Gmail" Node (ID: 356):
- Set the recipient email address(es).
- Customize the email subject and body to include relevant lead information, scraped data, and the AI's analysis.
- Activate the Workflow: Once configured, activate the workflow. New form submissions will now trigger the automated lead processing.
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.
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
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.