Save time hiring with AI: automate screening, assessments & interviews
AI Recruitment Automation Pipeline – Resume Parsing, GPT-4 Evaluation, Assessment Triggers & Interview Scheduling
This end-to-end AI-powered recruitment automation workflow helps HR and talent acquisition teams automate the complete hiring pipeline—from resume intake and parsing to GPT-4-based evaluation, TA approvals, assessment delivery, and interview scheduling.
Built using n8n, this template integrates with OpenAI GPT-4, Google Sheets, Google Drive, Slack, and SMTP to reduce time-to-hire, improve candidate quality, and eliminate repetitive manual tasks. The workflow enables scalable, consistent, and intelligent decision-making by automating resume evaluation, semantic fit analysis, and candidate communication.
This template is ideal for recruiters, TA teams, and founders looking to optimize hiring for tech, sales, support, and other roles with high applicant volume.
Who is this for?
- HR and TA teams handling high-volume recruitment
- Startups and SMBs looking to reduce hiring time and cost
- Hiring managers seeking to automate CV parsing and candidate evaluation
What problem does this solve?
- Eliminates manual resume screening
- Sends real-time updates to TA team on assessment completion
- Automates assessments, scoring, and interview scheduling
- Keeps candidate communication consistent and timely
What this workflow does
Smart Resume Intake Form
- Collects candidate data: name, email, phone, LinkedIn, job role, and CV (PDF).
- Custom-designed UI with branding-ready CSS.
PDF Resume Parsing & Storage
- CV is uploaded to a dedicated Google Drive folder.
- Resume text is extracted for semantic analysis.
AI-Based Candidate Evaluation (GPT-4 via LangChain)
- Extracts: City, Education, Job History, Skills.
- Summarizes candidate profile (100 words).
- Retrieves and summarizes job description from Google Sheets.
- Performs detailed evaluation:
- ✅ Semantic fit scoring (0–100%)
- ✅ Key matches and skill gaps
- ✅ Soft skills extraction
- ✅ Red flag detection (job-hopping, missing info)
- ✅ Final score (1–10) with rationale
Google Sheets Integration
- Logs and updates candidate data at each stage:
CV Submitted → Scored → Shortlisted → Assessment Sent → Interview Scheduled → Rejected
TA Approval via Email (Send & Wait)
- TA receives evaluation summary and gives one-click approve/reject.
- ✅ Approved → Status: Resume Selected
- ❌ Rejected → Status: Resume Rejected
Assessment Trigger (Post Approval)
- Sends assessment link to shortlisted candidates.
- Notifies TA via Slack and Email when assessment is submitted.
Interview Scheduling
- Sends Calendly link for self-scheduled interview booking.
- Candidate receives detailed next-step instructions.
Status-Based Candidate Emails
- Automatically sends:
- ✔️ Shortlisting confirmation + interview setup
- ❌ Rejection email with branded message
Business Benefits
- Save 80%+ time spent on manual resume reviews and coordination
- Reduce cost-per-hire by eliminating manual tasks
- Improve hiring accuracy with structured, AI-based decision-making
- Scalable recruitment for 100s of candidates per week
- Enhance candidate experience with instant status updates
- Centralize data in Google Sheets for full team visibility
🔧 Setup Instructions
1. Google Service Account Setup (One-Time)
Before using Google Sheets or Google Drive in n8n:
- Go to Google Cloud Console.
- Create a Service Account under your project.
- Enable these APIs:
- Google Sheets API
- Google Drive API
- Download the JSON credentials for the service account.
- IMPORTANT:
Share your target Google Sheets and Docs with the service account email
(e.g.,your-service-account@your-project.iam.gserviceaccount.com).
Add Applicant's Details to Google Sheet
- Document: Select the
ProfilesGoogle Sheet document. - Sheet: Select the
Applicant's Detailssheet. - Fields to Map:
EMAIL:{{ $('On form submission').item.json.Email }}DATE:{{ $now.format('dd-MM-yyyy') }}NAME:{{ $('On form submission').item.json.Name }}LINKEDIN URL:{{ $('On form submission').item.json["LinkedIn Profile URL"] }}JOB PROFILE:{{ $('On form submission').item.json["Job Openings"] }}STATUS:CV SUBMITTEDLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Extract Applicant's Resume Text
- Text:
{{ $('Extract from File').item.json.text }}
Get Job Description from Google Sheet
- Document:
Profiles - Sheet:
Job Openings - Filter:
- Column:
Job Profile - Value:
{{ $('On form submission').item.json["Job Openings"] }}
Save Evaluation Results in Google Sheets
- Document:
Profiles - Sheet:
Applicant's Details - Column Match On:
EMAIL - Fields to Map:
EMAIL:{{ $('On form submission').item.json.Email }}CITY:{{ $('Applicant\'s Details').item.json.output.City }}EDUCATIONAL:{{ $('Applicant\'s Details').item.json.output["Educational Qualification"] }}JOB HISTORY:{{ $('Applicant\'s Details').item.json.output["Job History"] }}SKILLS:{{ $('Applicant\'s Details').item.json.output.Skills }}SUMMARIZE:{{ $('Summarize Applicant\'s Profile').item.json.response.text }}SEMANTIC FIT SCORE:{{ $json.output.semantic_fit.score }}KEY MATCHES:{{ $json.output.semantic_fit.key_matches.toJsonString() }}KEY GAPS:{{ $json.output.semantic_fit.key_gaps.toJsonString() }}SEMANTIC FIT CONSIDERATION:{{ $json.output.semantic_fit.consideration }}SOFT SKILLS:{{ $json.output.soft_skills.toJsonString() }}EXPERIENCE GAP DETECTED:{{ $json.output.experience_analysis.experience_gap_detected }}OVER QUALIFICATION DETECTED:{{ $json.output.experience_analysis.overqualification_detected }}EXPERIENCE ANALYSIS CONSIDERATION:{{ $json.output.experience_analysis.consideration }}RED FLAGS ISSUES DETECTED:{{ $json.output.red_flags.issues_detected.toJsonString() }}RED FLAGS CONSIDERATION:{{ $json.output.red_flags.consideration }}VOTE:{{ $json.output.overall_evaluation.final_vote }}FINAL CONSIDERATION:{{ $json.output.overall_evaluation.consideration }}STATUS:CV SCOREDLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Update Applicant Statuses
Resume Selected
- Document:
Profiles - Sheet:
Applicant's Details - Column Match On:
EMAIL - Update:
STATUS:RESUME SELECTEDLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Resume Rejected
- Update:
STATUS:RESUME REJECTEDLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Assessment Sent
- Email:
{{ $('Loop to Send Assessment Link to Each Candidate').item.json.EMAIL }} - Update:
STATUS:ASSESSMENT SENTLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Assessment Submitted
- Email:
{{ $json["Enter Your Email Address"] }} - Update:
STATUS:ASSESSMENT SUBMITTEDLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Interview Booked
- Email:
{{ $json.payload.email }} - Update:
STATUS:INTERVIEW BOOKEDLAST UPDATED DATE:{{ $now.format('dd-MM-yyyy hh:mm:ss') }}
Fetch Applicants with Specific Status
Status: RESUME SELECTED
- Document:
Profiles - Sheet:
Applicant's Details - Filter:
- Column:
STATUS - Value:
RESUME SELECTED
Get Assessment Form URL from Job Profile
- Document:
Profiles - Sheet:
Job Openings - Filter:
- Column:
Job Profile - Value:
{{ $json["JOB PROFILE"] }}
Trigger on Applicant Status Update
- Document:
Profiles - Sheet:
Applicant's Details - Trigger Settings:
- Columns to Watch:
STATUS
⚠️ Important Notes
- Always use “Select Document from List” instead of manually pasting the sheet/document ID.
- Share your Sheets/Docs with the Google Service Account email for proper access.
- Keep your date formats consistent using
{{ $now.format('dd-MM-yyyy hh:mm:ss') }}.
- Add credentials for:
- Google Drive
- Google Sheets
- SMTP (for emails)
- OpenAI API Key (GPT-4)
- Replace placeholders:
- Google Sheet & Folder IDs
- Calendly Link
- Assessment Link
- (Optional) Customize GPT-4 prompts for domain-specific scoring
- (Optional) Use your Slack webhook for TA notifications
🛠️ Tools & Integrations
- Form Trigger – Candidate form with file upload
- Google Drive + Extract PDF – CV parsing
- Google Sheets – Database for all applicant statuses
- LangChain GPT-4 Nodes – AI profile + job analysis
- Email Send & Send & Wait – Candidate/TA communication
- IF Node – Logic for approve/reject
- Slack Integration – TA notification
- Calendly Link – Interview scheduling
AI resume screening, GPT-4 recruitment workflow, automated hiring pipeline, semantic fit evaluation, LangChain for HR, resume parsing automation, AI in talent acquisition, assessment workflow automation, interview scheduling automation, candidate shortlisting automation, OpenAI HR integration, Google Sheets recruitment tracker, n8n HR automation template, self-scheduling interviews with Calendly, Slack notifications in recruitment
Automate AI-Powered Candidate Screening and Interview Scheduling
This n8n workflow streamlines the hiring process by automating candidate screening, assessment, and interview scheduling using AI and various integrated services. It helps save time by intelligently processing candidate data and facilitating communication.
What it does
This workflow automates the following key steps:
- Triggers on new candidate submissions: It can be initiated by new entries in a Typeform, Google Sheet, or even a Calendly booking.
- Extracts information from files: If candidate data is submitted in a file format, it extracts relevant information.
- Processes candidate data with AI:
- Summarizes candidate information using an OpenAI Chat Model and a Summarization Chain.
- Extracts structured information (e.g., skills, experience, contact details) from candidate inputs using an Information Extractor.
- Performs basic LLM chain operations for further AI processing or analysis.
- Conditional Logic for Screening: Uses an If node and a Switch node to apply conditional logic, likely for screening candidates based on AI analysis or predefined criteria.
- Manages candidate data: Interacts with Google Sheets, potentially to log candidate details, scores, or status.
- Stores files: Can upload candidate-related files to Google Drive.
- Notifies and communicates:
- Sends email notifications (e.g., to candidates, hiring managers).
- Posts messages to Slack for team notifications or approvals.
- Loops over items: Uses a "Loop Over Items (Split in Batches)" node, suggesting it can process multiple candidate submissions or data points efficiently.
- Scheduled tasks: Includes a Schedule Trigger, indicating that certain parts of the workflow can run at predefined intervals (e.g., to check for new data, send reminders).
- Form Trigger: Can also be initiated by a generic n8n form submission.
Prerequisites/Requirements
To use this workflow, you will need accounts and API keys for the following services:
- Typeform: For collecting candidate applications (if using Typeform Trigger).
- Google Sheets: For managing candidate data.
- Google Drive: For storing candidate documents or related files.
- OpenAI API Key: For the OpenAI Chat Model to power AI summarization and information extraction.
- Slack Account: For sending internal notifications.
- SMTP/Email Service: For sending emails.
- Calendly: For scheduling interviews (if using Calendly Trigger).
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Set up your Typeform credentials (if using Typeform Trigger).
- Set up your Google Sheets credentials.
- Set up your Google Drive credentials.
- Configure your OpenAI API Key for the OpenAI Chat Model.
- Set up your Slack credentials.
- Configure your SMTP credentials for sending emails.
- Set up your Calendly credentials (if using Calendly Trigger).
- Customize Nodes:
- Typeform Trigger: Select the specific Typeform you want to monitor for new submissions.
- Google Sheets: Specify the spreadsheet and sheet names for reading/writing candidate data.
- Google Drive: Configure the folder where files should be uploaded.
- OpenAI Chat Model / Summarization Chain / Information Extractor: Adjust prompts and parameters to suit your specific screening criteria and desired output.
- If / Switch nodes: Define the conditions for screening and routing candidates based on the AI output or other data.
- Send Email: Customize email templates for candidate communications or internal alerts.
- Slack: Configure the channel and message content for notifications.
- Calendly Trigger: Select the Calendly event type to monitor for new bookings.
- Schedule Trigger: Configure the desired interval for scheduled tasks.
- n8n Form Trigger: If using, customize the form fields.
- Activate the workflow: Once configured, activate the workflow to start automating your hiring process.
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.