Back to Catalog

Automate passive candidate sourcing & engagement with Hunter.io, AI scoring & Gmail

MarthMarth
87 views
2/3/2026
Official Page

How It Works: The AI Recruiter Engine

This workflow is a powerful, two-phase system designed to automate the entire passive candidate sourcing and engagement cycle.


Phase 1: Sourcing & Enrichment

This phase is triggered manually and focuses on finding, analyzing, and scoring potential candidates.

  1. Manual Trigger: You start the workflow manually by providing a jobTitle and keywords.
  2. Code (Generate Search Query): This node uses your input to create a sophisticated search query for an external sourcing platform.
  3. HTTP Request (Hunter.io/Clearbit): The workflow queries a third-party API to find public email addresses for the target companies or candidates.
  4. Code (Filter Candidates): This node filters the raw data, keeping only candidates who match your basic criteria.
  5. Airtable/Google Sheets (Log Candidates): All potential candidates are logged into your centralized database to serve as your simple ATS.
  6. Code (AI Analysis & Score): This node prepares a prompt with the candidate's profile data and sends it to a generative AI model (via an HTTP Request). It then calculates a final score based on the AI's analysis and other criteria.
  7. If (Is Score > 75?): This node checks if the candidate’s score meets your threshold. If so, they are passed to the next phase; otherwise, they are filtered out.

Phase 2: Automated Outreach & Nurturing

This phase handles the multi-step, personalized email communication with high-scoring candidates.

  1. Gmail (Send Initial Email): The workflow sends a personalized first email using dynamic data from the candidate's profile.
  2. Airtable/Google Sheets (Update Status): The candidate's status is updated to Contacted in your database.
  3. Wait: The workflow pauses for a set period (e.g., 3 days) to allow time for a response.
  4. If (No Reply?): This node checks the candidate's status in your database. If they haven't replied, the workflow proceeds to the next email.
  5. Gmail (Send Follow-up): A follow-up email is sent to the candidate. This sequence repeats with a final nurture email to close the loop.

How to Set Up

  1. Prepare Your Credentials & Database:

    • Database: Create a database in Airtable or Google Sheets with columns for Name, Email, Score, Status, and any other data you want to track.
    • Email: Set up a Gmail or other email service credential in n8n.
    • Sourcing API: Obtain an API key for a sourcing service like Hunter.io to find public email addresses.
  2. Import the Workflow:

    • Import the JSON code for the AI Recruiter Engine into your n8n instance.
  3. Configure the Nodes:

    • Manual Trigger: When running the workflow, manually input the jobTitle and keywords you are sourcing for.
    • HTTP Request: Update the URL with your sourcing API key.
    • Code Nodes: Review and adjust the JavaScript in the Code nodes to match your specific job criteria and data structure.
    • Airtable/Google Sheets: Connect to your database, select the correct table, and ensure the column names in the node settings match your database.
    • Gmail: Select your email credential and customize the content of the outreach emails in each Gmail node.
    • If: Adjust the finalScore threshold in the If node to your desired value.
  4. Test and Activate:

    • Run the workflow once manually to ensure all nodes are configured correctly and data flows as expected.
    • Once you are confident, the workflow is ready to be run for your sourcing campaigns.

Automate Passive Candidate Sourcing & Engagement with AI Scoring & Gmail

This n8n workflow streamlines the process of identifying, scoring, and engaging with passive candidates. It reads candidate data from a Google Sheet, processes it for potential outreach, and facilitates sending personalized emails via Gmail based on an AI-driven scoring mechanism.

What it does

  1. Triggers Manually: The workflow is initiated manually, allowing for on-demand processing of candidate lists.
  2. Reads Candidate Data: It fetches candidate information from a specified Google Sheet, acting as the primary source for candidate profiles.
  3. Processes Candidate Data (Placeholder): A "Code" node is included, likely intended for custom logic to process or transform the candidate data from the Google Sheet. This could involve data cleaning, formatting, or preparing data for AI scoring.
  4. Scores Candidates (Placeholder for AI): An "HTTP Request" node is present, which would typically be used to send candidate data to an external AI service (e.g., Hunter.io AI scoring as hinted by the directory name) for evaluation and scoring.
  5. Conditional Engagement: An "If" node evaluates the AI score or other criteria, branching the workflow based on whether a candidate meets the engagement threshold.
  6. Engages High-Scoring Candidates: For candidates who meet the specified criteria, a "Gmail" node is used to send personalized outreach emails.
  7. Delays Further Actions: A "Wait" node is included, likely to introduce a delay between sending emails or before any follow-up actions, adhering to best practices for email outreach.
  8. Documents Workflow Steps: A "Sticky Note" is included, which can be used to add comments or explanations directly within the workflow for better understanding and maintenance.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: To store and manage candidate data.
  • Gmail Account: For sending outreach emails.
  • Hunter.io Account (or similar AI scoring service): An API key and access to a candidate scoring service would be required for the "HTTP Request" node to function as intended for AI scoring.
  • Google OAuth Credentials: For both Google Sheets and Gmail nodes to authenticate with your Google account.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Node:
    • Set up your Google Sheets credentials (OAuth).
    • Specify the Spreadsheet ID and Sheet Name where your candidate data is located.
  3. Configure HTTP Request Node (for AI Scoring):
    • Set up the URL for your Hunter.io AI scoring API endpoint (or similar service).
    • Configure the HTTP Method (e.g., POST) and Headers (e.g., Authorization with your API key).
    • Map the candidate data from the previous nodes to the Body of the request in the format required by the AI scoring service.
  4. Configure Code Node:
    • Modify the JavaScript code within this node to perform any necessary data manipulation or preparation before sending to the AI scoring service.
  5. Configure If Node:
    • Set the Conditions based on the output of the AI scoring (e.g., {{ $json.score > 70 }}). This will determine which candidates proceed to the Gmail step.
  6. Configure Gmail Node:
    • Set up your Gmail credentials (OAuth).
    • Define the Recipient Email using an expression to pull the email address from the candidate data (e.g., {{ $json.email }}).
    • Compose the Subject and Body of the email, using expressions to personalize the message with candidate details (e.g., {{ $json.firstName }}).
  7. Configure Wait Node:
    • Adjust the Delay Time as needed to manage your email sending rate.
  8. Execute the Workflow: Click "Execute workflow" to run the process manually.

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