Extract sales leads from Google Jobs, LinkedIn & Indeed with GPT-4o and Apify
Who is this for?
This template is designed for B2B sales teams, recruiters, and business development professionals who want to identify sales opportunities by monitoring hiring signals from target companies. It's particularly useful for:
- Sales teams selling HR tech, recruitment software, or staffing services
- Consultancies offering technical talent or project-based work
- Any B2B company that uses "intent data" from job postings to time their outreach
What this workflow does
This workflow automates the entire process of monitoring job postings and converting hiring signals into actionable sales leads:
- Daily Job Scraping: Automatically scrapes job postings from Google Jobs, LinkedIn, and Indeed for your target companies using Apify actors
- Data Normalization: Standardizes job data from multiple sources into a unified format
- Keyword Filtering: Filters jobs based on your target keywords to identify relevant opportunities
- AI-Powered Analysis: Uses GPT-4o to analyze each qualified job posting and generate:
- Inferred pain points from the hiring signal
- Strategic sales approach angles
- Urgency scoring (1-10)
- Ready-to-send cold email drafts
- Slack Notifications: Sends real-time alerts with AI insights to your sales channel
- Weekly Reports: Generates comprehensive trend analysis reports every Monday with AI-powered insights
Setup
-
Google Sheets: Create a spreadsheet with 4 sheets:
Target Companies(columns: Company Name, Target Keywords, My Solution)Raw Jobs(for all scraped jobs)Qualified Leads(for filtered opportunities)Weekly Reports(for trend analysis)
-
Apify: Set up accounts and get Actor IDs for:
- Google Jobs Scraper
- LinkedIn Jobs Scraper
- Indeed Scraper
-
Credentials: Connect your Google Sheets, Slack, Gmail, OpenAI, and Apify credentials
-
Configuration: Update the placeholder values in the workflow for your specific IDs and channel names
Requirements
- n8n instance (self-hosted or cloud)
- Apify account with credits
- OpenAI API key (GPT-4o access)
- Google Sheets access
- Slack workspace (optional, for notifications)
- Gmail account (optional, for email reports)
Customization
- Adjust
maxJobsPerSourceanddaysToCheckin the Configuration node - Modify AI prompts to match your sales style and language preferences
- Add or remove job sources based on your needs
- Customize Slack message format and notification triggers
Extract Sales Leads from Google Jobs, LinkedIn & Indeed with GPT-4o and Apify
This n8n workflow automates the process of extracting sales leads from job postings on Google Jobs, LinkedIn, and Indeed. It leverages Apify for web scraping, GPT-4o for intelligent data extraction and enrichment, and then routes the refined leads to either Google Sheets, Slack, or Gmail for further action.
The workflow is designed to streamline lead generation for sales teams, recruiters, or anyone looking to identify potential clients or partners based on hiring needs.
What it does
- Triggers Manually: The workflow is currently set up for manual execution, allowing you to initiate the lead extraction process on demand.
- Scrapes Job Postings (Apify - Implicit): Although not explicitly present in the provided JSON, the workflow's name suggests it integrates with Apify for scraping job postings from Google Jobs, LinkedIn, and Indeed. The output of this scraping would then be fed into the subsequent nodes.
- Processes with AI Agent: An "AI Agent" (likely a LangChain agent) is used to process the scraped job data. This agent probably orchestrates calls to language models and tools to extract relevant sales lead information.
- Extracts Structured Data: A "Structured Output Parser" (LangChain) is employed to ensure the AI agent's output is consistently formatted, likely into a JSON structure containing key lead details.
- Enriches with OpenAI Chat Model: An "OpenAI Chat Model" (GPT-4o, as per the directory name) is utilized, likely for tasks such as:
- Identifying key decision-makers or relevant roles.
- Inferring company details or industry.
- Summarizing job requirements for lead qualification.
- Generating personalized outreach messages.
- Edits/Sets Fields: A "Set" node is used to transform or refine the data structure, ensuring all extracted lead information is in a consistent and usable format.
- Conditional Routing: An "If" node evaluates the processed leads, likely based on criteria such as lead quality, completeness, or specific keywords.
- Merges Data: A "Merge" node is present, suggesting that different branches of the workflow (e.g., successful extraction vs. partial extraction) might be combined before final output.
- Sends to Google Sheets: Qualified leads can be automatically added to a Google Sheet for centralized tracking and management.
- Notifies via Slack: Alerts or summaries of new leads can be sent to a designated Slack channel, keeping the team informed in real-time.
- Sends Emails via Gmail: The workflow can send personalized emails, potentially for outreach or internal notifications, based on the extracted leads.
- Executes Custom Code: A "Code" node allows for custom JavaScript logic, which could be used for advanced data manipulation, validation, or integration with other services.
- Sticky Note for Documentation: A "Sticky Note" is included for internal documentation or comments within the workflow.
Prerequisites/Requirements
- n8n Instance: A running instance of n8n.
- Apify Account: (Implicit) An Apify account with access to relevant job scraping actors.
- OpenAI API Key: For the "OpenAI Chat Model" node (GPT-4o).
- Google Account: With access to Google Sheets, for the "Google Sheets" and "Gmail" nodes.
- Slack Account: For the "Slack" node.
- n8n Credentials: Configured credentials for OpenAI, Google (OAuth), and Slack within your n8n instance.
Setup/Usage
- Import the Workflow: Download the workflow JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your OpenAI API key credential.
- Configure Google OAuth credentials for Google Sheets and Gmail.
- Set up your Slack API token credential.
- Customize Apify Integration (Implicit): If the Apify integration is not fully defined in the JSON, you will need to add and configure the Apify node to scrape the desired job platforms (Google Jobs, LinkedIn, Indeed) with your specific search queries.
- Adjust AI Agent and Output Parser: Review the configuration of the "AI Agent" and "Structured Output Parser" nodes. You may need to refine the prompts or schema definitions to optimize lead extraction for your specific needs.
- Configure "Edit Fields" (Set) Node: Adjust the "Edit Fields" node to map and transform the extracted data into your desired output structure.
- Define "If" Node Conditions: Customize the conditions in the "If" node to filter leads based on your qualification criteria.
- Configure Output Nodes:
- Google Sheets: Specify the Spreadsheet ID and Sheet Name where leads should be added.
- Slack: Define the channel and message content for Slack notifications.
- Gmail: Configure recipient, subject, and body for email notifications.
- Review Custom Code (if present): If the "Code" node contains custom logic, ensure it aligns with your requirements.
- Activate the Workflow: Once configured, activate the workflow.
- Execute Manually: Since it's a manual trigger, click "Execute Workflow" to run it and begin extracting leads. For automated runs, consider replacing the manual trigger with a "Schedule Trigger" or "Webhook" node.
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
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
🎓 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.