Back to Catalog

AI resume screening & evaluation for HR with GPT-4 & Google Workspace

Trung TranTrung Tran
847 views
2/3/2026
Official Page

Try It Out, HireMind – AI-Driven Resume Intelligence Pipeline!

This n8n template demonstrates how to automate resume screening and evaluation using AI to improve candidate processing and reduce manual HR effort.

A smart and reliable resume screening pipeline for modern HR teams. This workflow combines Google Drive (JD & CV storage), OpenAI (GPT-4-based evaluation), Google Sheets (position mapping + result log), and Slack/SendGrid integrations for real-time communication. Automatically extract, evaluate, and track candidate applications with clarity and consistency.


How it works

  • A candidate submits their application using a form that includes name, email, CV (PDF), and a selected job role.
  • The CV is uploaded to Google Drive for record-keeping and later reference.
  • The Profile Analyzer Agent reads the uploaded resume, extracts structured candidate information, and transforms it into a standardized JSON format using GPT-4 and a custom output parser.
  • The corresponding job description PDF file is automatically retrieved from a Google Sheet based on the selected job role.
  • The HR Expert Agent evaluates the candidate profile against the job description using another GPT-4 model, generating a structured assessment that includes strengths, gaps, and an overall recommendation.
  • The evaluation result is parsed and formatted for output.
  • The evaluation score will be used to mark candidate as qualified or unqualified, based on that an email will be sent to applicant or the message will be send to hiring team for the next process
  • The final evaluation result will be stored in a Google Sheet for long-term tracking and reporting.

Google drive structure

├── jd # Google drive folder to store your JD (pdf) │ ├── Backend_Engineer.pdf │ ├── Azure_DevOps_Lead.pdf │ └── ... │ ├── cv # Google drive folder, where workflow upload candidate resume │ ├── John_Doe_DevOps.pdf │ ├── Jane_Smith_FullStack.pdf │ └── ... │ ├── Positions (Sample: https://docs.google.com/spreadsheets/d/1pW0muHp1NXwh2GiRvGVwGGRYCkcMR7z8NyS9wvSPYjs/edit?usp=sharing) # 📋 Mapping Table: Job Role ↔ Job Description (Link) │ └── Columns: │ - Job Role │ - Job Description File URL (PDF in jd/) │ └── Evaluation form (Google Sheet) # ✅ Final AI Evaluation Results

How to use

  1. Set up credentials and integrations:

    • Connect your OpenAI account (GPT-4 API).
    • Enable Google Cloud APIs:
      • Google Sheets API (for reading job roles and saving evaluation results)
      • Google Drive API (for storing CVs and job descriptions)
    • Set up SendGrid (to send email responses to candidates)
    • Connect Slack (to send messages to the hiring team)
  2. Prepare your Google Drive structure:

    • Create a root folder, then inside it create:
      • /jd → Store all job descriptions in PDF format
      • /cv → This is where candidate CVs will be uploaded automatically
    • Create a Google Sheet named Positions with the following structure:
      | Job Role                     | Job Description Link                   |
      |------------------------------|----------------------------------------|
      | Azure DevOps Engineer        | https://drive.google.com/xxx/jd1.pdf   |
      | Full-Stack Developer (.NET)  | https://drive.google.com/xxx/jd2.pdf   |
      
  3. Update your application form:

    • Use the built-in form, or connect your own (e.g., Typeform, Tally, Webflow, etc.)
    • Ensure the Job Role dropdown matches exactly the roles in the Positions sheet
  4. Run the AI workflow:

    • When a candidate submits the form:
      • Their CV is uploaded to the /cv folder
      • The job role is used to match the JD from /jd
      • The Profile Analyzer Agent extracts candidate info from the CV
      • The HR Expert Agent evaluates the candidate against the matched JD using GPT-4
  5. Distribute and store results:

    • Store the evaluation results in the Evaluation form Google Sheet
    • Optionally notify your team:
      • ✉️ Send an email to the candidate using SendGrid
      • 💬 Send a Slack message to the hiring team with a summary and next steps

Requirements

  • OpenAI GPT-4 account for both Profile Analyzer and HR Expert Agents
  • Google Drive account (for storing CVs and evaluation sheet)
  • Google Sheets API credentials (for JD source and evaluation results)

Need Help?

Join the n8n Discord or ask in the n8n Forum!

Happy Hiring! 🚀

AI Resume Screening & Evaluation for HR with GPT-4 & Google Workspace

This n8n workflow automates the process of screening and evaluating resumes for HR professionals. It leverages AI (GPT-4) to analyze resumes, provides a structured output, and facilitates communication via Slack and email, while maintaining a record in Google Sheets.

What it does

This workflow streamlines the resume screening process through the following steps:

  1. Triggers on Form Submission: Initiates when an n8n form is submitted, likely containing resume details or a link to a resume.
  2. Retrieves Resume from Google Drive: Fetches the resume file from Google Drive based on information provided in the form submission.
  3. Extracts Text from Resume: Processes the binary resume file to extract its textual content.
  4. Evaluates Resume with AI (GPT-4): Sends the extracted resume text to an OpenAI Chat Model (GPT-4) via a LangChain Basic LLM Chain, structured by a Structured Output Parser, to perform an AI-driven evaluation.
  5. Stores Evaluation in Google Sheets: Records the AI evaluation results (and potentially other resume data) into a Google Sheet.
  6. Conditional Notification:
    • If AI Evaluation is Positive: Sends a positive notification to a designated Slack channel and an email to the candidate via SendGrid.
    • If AI Evaluation is Negative: Sends a negative notification to a designated Slack channel and an email to the candidate via SendGrid.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Drive Account: For storing and retrieving resume files.
  • Google Sheets Account: For logging AI evaluation results.
  • OpenAI API Key: For accessing the GPT-4 chat model.
  • Slack Account: For sending internal notifications.
  • SendGrid Account: For sending emails to candidates.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up Google Drive credentials (OAuth 2.0 recommended) to allow n8n to access your Google Drive.
    • Set up Google Sheets credentials (OAuth 2.0 recommended) to allow n8n to write to your Google Sheets.
    • Configure OpenAI credentials with your API Key.
    • Set up Slack credentials (OAuth 2.0 recommended) for posting messages.
    • Configure SendGrid credentials with your API Key for sending emails.
  3. Customize Nodes:
    • On form submission (Node 1225): Configure the form fields to match the data you expect (e.g., candidate name, email, Google Drive file ID for the resume).
    • Google Drive (Node 58): Specify the Google Drive folder or file ID where resumes are stored. Ensure the file ID is passed from the form trigger.
    • Extract from File (Node 1235): Ensure it's correctly configured to handle the resume file type (e.g., PDF, DOCX).
    • OpenAI Chat Model (Node 1153): Select the appropriate GPT-4 model and fine-tune the prompt within the Basic LLM Chain (Node 1123) and AI Agent (Node 1119) to guide the AI evaluation based on your specific hiring criteria. The Structured Output Parser (Node 1179) should be configured to extract key evaluation points.
    • Google Sheets (Node 18): Specify the spreadsheet and sheet name where the evaluation results should be stored. Map the AI-generated evaluation data to the correct columns.
    • If (Node 20): Adjust the conditions to define what constitutes a "positive" or "negative" AI evaluation based on the structured output.
    • Slack (Node 40): Configure the Slack channel and message content for both positive and negative outcomes.
    • SendGrid (Node 439): Customize the email templates for both positive and negative candidate responses.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Test: Submit the n8n form with a test resume to ensure all steps execute correctly and notifications are sent as expected.

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