Find high-intent sales leads by scraping Glassdoor with Bright Data & GPT
🔍 Scrape Glassdoor with Bright Data
Designed for sales teams, recruiters, and marketers aiming to automate job discovery and prospecting.
This workflow scrapes Glassdoor job listings using Bright Data and automatically generates targeted pitches using AI, streamlining lead identification and outreach.
🧩 How It Works
This automation leverages n8n, Bright Data, Google Sheets, and OpenAI:
1. Trigger
- Starts with a custom form input (Location, Keyword, Country).
2. Bright Data Job Scrape
- Triggers a Bright Data dataset snapshot via HTTP Request.
- Polls snapshot progress using a Wait node, ensuring data readiness.
- Retrieves full job listings dataset once ready.
3. Google Sheets Integration
- Writes detailed job data (company, role, location, overview, metrics) into a Google Sheet.
- Uses a pre-built template for organized data storage.
4. Automated Pitch Generation (AI)
- Splits listings into actionable parts: company name, title, and description.
- Sends data to OpenAI (via LangChain) to generate relevant pitches or icebreakers.
- Saves generated content back into the same sheet for easy access.
✅ Requirements
Ensure you have the following:
Google Sheets
- Google account
- Template Sheet with columns for job details and AI-generated pitches
Bright Data
- Active account with Dataset API access
- API key and dataset ID
OpenAI
- Valid OpenAI API key for GPT models
n8n Environment
- Nodes:
HTTP Request,Wait,If,Google Sheets,Split Out,LangChain (OpenAI) - Credentials:
- Google Sheets OAuth2
- Bright Data API credentials
- OpenAI API key
⚙️ Setup Instructions
Step 1: Prepare Google Sheets
- Copy the provided Google Sheets template
- Do not change headers
Step 2: Import & Configure Workflow in n8n
- Import the workflow JSON file
- Set Google Sheets node:
- Link to your copied sheet
- Confirm correct tab name
Step 3: Configure Bright Data
- Replace
<YOUR_BRIGHT_DATA_API_KEY>with your real key - Set your dataset ID in all HTTP Request nodes
Step 4: Configure OpenAI (LangChain)
- Connect OpenAI API key to the LangChain node
- Customize prompt to match tone and outreach style
Step 5: Testing & Scheduling
- Test via manual form trigger
- Schedule runs or leave form enabled for on-demand use
🧠 Tips & Best Practices
- Use specific keywords and locations for better results
- Adjust polling intervals based on dataset size
- Refine AI prompts regularly to improve pitch quality
- Clean unused columns from your sheet to boost performance
💬 Support & Feedback
For help or customization:
📧 Email: Yaron@nofluff.online
📺 YouTube: @YaronBeen
🔗 LinkedIn: linkedin.com/in/yaronbeen
📚 Bright Data Docs: docs.brightdata.com/introduction
Find High-Intent Sales Leads by Scraping Glassdoor with Bright Data & GPT
This n8n workflow automates the process of identifying high-intent sales leads by scraping Glassdoor for company data and then using an AI model to qualify them. It's designed to streamline lead generation for sales teams looking for companies actively hiring for specific roles, indicating potential growth and budget for new solutions.
What it does
- Triggers Manually: The workflow is initiated manually via a form submission within n8n.
- Scrapes Glassdoor: It performs an HTTP request to a Bright Data web scraping proxy, targeting Glassdoor to extract company information.
- Splits Data: The scraped data, which is likely an array of companies, is split into individual items for processing.
- Qualifies Leads with AI: For each company, it uses an OpenAI Chat Model (via a Basic LLM Chain) to analyze the scraped data and determine if it's a "high-intent" sales lead based on predefined criteria.
- Filters Qualified Leads: An "If" node checks the AI's output to see if the company is indeed a high-intent lead.
- Waits (Optional): If a company is a high-intent lead, the workflow includes a "Wait" step, which might be used for rate limiting or to allow for manual review before the next step.
- Saves to Google Sheets: Finally, the qualified high-intent leads are appended to a Google Sheet for further action by the sales team.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Bright Data Account: An account with Bright Data (or a similar web scraping proxy service) configured to scrape Glassdoor.
- OpenAI API Key: An OpenAI API key to access the language model for lead qualification.
- Google Account: A Google account with access to Google Sheets.
- Google Sheets Credential: An n8n credential configured for Google Sheets.
- OpenAI Chat Model Credential: An n8n credential configured for the OpenAI Chat Model.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file for this workflow.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- HTTP Request (Bright Data): Configure the "HTTP Request" node (Node ID 19) with your Bright Data proxy details, including any necessary headers or authentication.
- OpenAI Chat Model: Configure the "OpenAI Chat Model" node (Node ID 1153) with your OpenAI API Key.
- Google Sheets: Configure the "Google Sheets" node (Node ID 18) with your Google Sheets credential. You will need to specify the Spreadsheet ID and Sheet Name where the leads should be stored.
- Customize Lead Qualification Logic:
- Review and adjust the prompt within the "Basic LLM Chain" node (Node ID 1123) to fine-tune how the AI identifies high-intent leads based on your specific criteria (e.g., "Is the company actively hiring for sales roles?", "Does the company show signs of recent growth?").
- Adjust the "If" node (Node ID 20) conditions to accurately filter based on the AI's output.
- Activate the Workflow:
- Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
- Trigger Manually:
- To run the workflow, click the "Execute Workflow" button in the n8n editor or use the "On form submission" trigger (Node ID 1225) if you set up a form. The current JSON indicates a manual form trigger.
Related Templates
Seo blog content automation with GPT-4o-mini and human approval in Google Docs
Overview This n8n workflow automates the entire content creation process for SEO blog posts, from topic submission and AI drafting to human approval, revision, and final storage in Google Docs. It ensures high-quality, SEO-optimized content is generated efficiently while keeping a human in the loop for quality control. Prerequisites To use this workflow, you need the following accounts and credentials: Google Sheets Account: To manage the content tracker. The sheet must contain columns for Topic, Reference URL, Title, Status, and Link to document. OpenAI API Key (for GPT-4o-mini): To power the initial content drafting and subsequent revisions. Gmail Account: To send the content for human approval and wait for feedback. Google Docs Account: To create and store the final approved blog posts. How It Works The workflow operates in four main stages: Topic Submission, AI Content Creation, Human Approval & Revision Loop, and Final Publishing. Stage 1: Topic Submission and Tracking This stage captures a new blog topic and adds it to the content tracker. On form submission (Form Trigger): The workflow is initiated when a user submits a Topic and an optional Reference link through the form. Append row in sheet (Google Sheets): The new topic and reference link are added as a new row in your content tracker sheet. Get Topic from Google Sheets: The workflow fetches the newly added row, including the system-generated row_number for tracking updates. Stage 2: AI Content Creation (Initial Draft) The workflow uses an expert AI agent to generate the first draft of the blog post. Copywriter AI Agent: Acting as an expert SEO content strategist, the agent receives the topic and reference URL. The agent improves the provided topic into an SEO-optimized title. It writes a complete, conversational, SEO-friendly blog post (800–1200 words) using proper Markdown headings and lists. OpenAI Chat Model (GPT-4o-mini): Powers the agent's generation. Structured Output Parser: Ensures the output is in a JSON format with separate title and content keys. Set Data: The AI-generated title and content are mapped to workflow variables (Topic Title, Content) for easy use in subsequent nodes. Stage 3: Human Approval and Revision Loop This is the critical quality control step where a human reviews the draft and decides on the next action. Send Content for Approval (Gmail): The generated title and content are sent via email to the approver (<your email>). This uses a custom form that allows the user to choose Yes (Approve), No (Request Revision), or Cancel. The form also includes a Content Feedback textarea. Approval Result (Switch): The workflow pauses until the approver submits the form, and then directs the flow based on their choice. If "Yes" (Approved): Proceeds to the final publishing stage. The Update Topic Status on Google Sheets node is executed, setting the Status to Approved and logging the new Title. If "No" (Revision Requested): Proceeds to the revision loop. Copywriter Revision Agent: This agent takes the original content, the topic title, and the user's Content Feedback. It is instructed to incorporate the feedback, preserving the existing structure and tone, and outputs a revised blog post. The flow loops back through the Set Data node and then returns to the Send Content for Approval node for a new review. If "Cancel": Stops the workflow, and the Update Topic Status on Google Sheets node is executed. Stage 4: Final Publishing Once approved, the content is stored in Google Docs and the tracker is updated. Create Blog file (Google Docs): A new Google Doc is created using the approved Topic Title. Add blog content in file (Google Docs): The final Content (in Markdown format) is inserted into the newly created document. Update sheet with blog post link (Google Sheets): The final tracker update logs the Link to document and the Published date. Customization Tip Recommend using AI humanazier and AI detector tools before approval to make the SEO score better.
Generate SEO content briefs with GPT-4o, DataForSEO keyword research & SERP analysis
📊 Description Generate high-quality, SEO-optimized content briefs automatically using AI, real-time keyword research, SERP intelligence, and historical content context. This workflow standardizes user inputs, fetches search metrics, analyzes competitors, and produces structured SEO briefs with quality scoring and version control. It also stores all versions in Google Sheets and generates HTML previews for easy review and publishing. 🤖📄📈 What This Template Does Normalizes user input from the chat trigger into structured fields (intent, topic, parameters). ✏️ Fetches real-time keyword metrics such as search volume, CPC, and difficulty from DataForSEO. 🔍 Retrieves SERP insights through SerpAPI for top competitors, headings, and content gaps. 🌐 Loads historical brief versions from Google Sheets for continuity and versioning. 📚 Uses an advanced GPT-4o-mini agent to generate a complete SEO brief with title, metadata, keywords, outline, entities, and internal links. 🤖 Calculates detailed SEO, differentiation, and completeness quality scores. 📊 Validates briefs against quality thresholds (outline length, keywords, word count, overall score). ⚡ Stores approved briefs in Google Sheets with version control and timestamping. 🗂️ Generates an HTML preview with styled formatting for team review or CMS use. 🖥️ Sends Slack alerts when a brief does not meet quality standards. 🚨 Key Benefits ✅ Fully automated SEO content brief generation ✅ Uses real-time keyword + SERP + competitor intelligence ✅ Ensures quality through automated scoring and validation ✅ Built-in version control for content operations teams ✅ Beautiful HTML preview ready for editors or clients ✅ Reduces research time from hours to minutes ✅ Ideal for content agencies, SEO teams, and AI-powered workflows Features Chat-triggered brief generation Real-time DataForSEO keyword metrics SERP analysis tool integration GPT-4o-mini structured AI agent Google Sheets integration for storing & retrieving versions Automated quality scoring (SEO, gaps, completeness) HTML preview builder with rich formatting Slack alerting for low-quality briefs Semantic entities, content gaps, competitor insights Requirements OpenAI API (GPT-4o-mini or compatible model) DataForSEO access credentials (Basic Auth) SerpAPI key for SERP extraction Google Sheets OAuth2 integration Optional: Slack webhook for quality alerts Target Audience SEO teams generating large amounts of content briefs Content agencies scaling production with automation Marketing teams building data-driven content strategies SaaS teams wanting automated keyword-based briefs Anyone needing structured, high-quality content briefs from chat Step-by-Step Setup Instructions Connect your OpenAI API credential and confirm GPT-4o-mini availability. 🔌 Add DataForSEO HTTP Basic Auth for keyword metrics. 📊 Connect SerpAPI for SERP analysis tools. 🌐 Add Google Sheets OAuth2 and link your content_versions sheet. 📄 Optional: Add a Slack webhook URL for quality alerts. 🔔 Test by sending a topic via the chat trigger. Review the generated SEO brief and HTML preview. Enable the workflow for continued use in your content pipeline. 🚀
Automate meeting transcription & minutes distribution with OpenAI and Google Drive
Automated Meeting Recording Transcription & Minutes Distribution Workflow Managing meeting recordings manually—downloading audio, transcribing it, summarizing key points, saving documents, and notifying the team—quickly becomes repetitive and inefficient. This workflow eliminates all of those manual steps by automatically detecting new audio files uploaded to a designated Google Drive folder, converting them into high-quality transcripts using OpenAI, summarizing them into structured meeting minutes, transforming the content into a text file, uploading it back to Google Drive, and finally notifying a Chatwork room with the completed summary. What used to take hours can now be completed automatically within minutes, ensuring consistency, accuracy, and faster information sharing. Who’s it for This workflow is ideal for: Teams that need high-quality, client-ready meeting minutes generated automatically Project managers who require accurate summaries, decision tracking, and action items without manual effort Cross-functional teams handling multiple meetings and requiring structured, searchable documentation Organizations using Google Meet, Zoom, or Teams where recordings must be turned into polished minutes Anyone who wants a consistent, AI-assisted system that analyzes discussions, extracts insights, and formats them professionally By leveraging an advanced Meeting Minutes Generation System—capable of key-point extraction, noise reduction, speaker/topic organization, and review support—this workflow ensures that every meeting is transformed into a clean, structured, and highly usable document. --- How it works Audio file upload triggers the workflow When a new recording is uploaded to the designated Google Drive folder, the Google Drive Trigger immediately activates and begins processing. The audio file is downloaded The file is retrieved from Google Drive and prepared in binary format for accurate transcription. AI-powered transcription The audio is sent to OpenAI’s transcription engine, producing a complete and highly accurate transcript of the meeting. Generate structured, client-ready meeting minutes The transcript is processed by a specialized Meeting Minutes Generation System powered by a multi-step prompt. Instead of using a fixed template, the system intelligently analyzes the transcription and automatically generates a professionally structured document using the following capabilities: Extraction of key points while removing irrelevant conversation Organization of content by speaker, topic, and logical flow Automatic construction of headings and document structure Draft generation based on client-facing writing standards Review-support logic that allows refinement and improved readability Task-based orchestration (ingestion → key-point extraction → draft generation → review → final approval) Because the system dynamically determines the optimal structure, the resulting minutes adapt to the content of each meeting rather than following a rigid set of categories. If certain information cannot be derived from the transcript, the system will appropriately leave it out rather than forcing placeholder sections. Convert the minutes into a file The structured minutes are converted into a .txt or .docx document, ready for submission or archival. Upload the finalized document The completed meeting minutes are uploaded to a specific Google Drive folder and saved using a timestamped filename. Notify Chatwork A formatted notification—including the summarized content—is automatically posted to a Chatwork room, ensuring immediate team visibility. --- How to set up Import the workflow into your n8n environment. Authenticate Google Drive and select the folder to monitor for new recordings. Connect your OpenAI API keys for both transcription and structured minutes generation. Specify the Google Drive folder where the finished documents should be stored. Add your Chatwork API token and room ID for automated notifications. Upload a sample audio file to confirm the full end-to-end pipeline works correctly. --- Requirements n8n instance (cloud or self-hosted) Google Drive account with appropriate folder permissions OpenAI API credentials Chatwork API token Supported audio formats like mp3, wav, m4a, etc. --- How to customize the workflow Modify the minutes-generation prompt to reflect your organization’s preferred format Add Slack, Teams, or Discord notifications in addition to Chatwork Route different types of meetings to different folders or templates Save transcript and structured minutes separately for compliance or analysis Log metadata or decisions into Google Sheets or project management tools Store minutes in a vector database to enable semantic search across past meetings Attach the final document directly as a file in Chatwork Extend the system to support revision cycles, reviewer comments, or approval workflows