LLM Resume Extraction and Analysis for Recruitment Teams

This workflow automates resume screening by collecting resumes via Gmail, storing them in Google Drive, extracting text, analyzing with OpenAI, and logging results in Google Sheets. Key nodes include Gmail Trigger, Google Drive, Google Sheets, OpenAI, and Condition nodes for validation, enabling efficient candidate evaluation. Install n8n from n8n.io for self-hosting or sign up at cloud.n8n.io. Create a Google Cloud account at console.cloud.google.com to obtain OAuth2 credentials for Gmail Trigger ('Resume Collection'), Google Drive ('Resume Archive'), and Google Sheets ('Recruitment Database', 'Error Logger'). Get an OpenAI API key from openai.com for the OpenAI node ('AI Recruitment Analyst'). Configure environment variables in the Set node ('Screening Session Manager'): RESUME_POLL_INTERVAL_MINUTES, RESUME_SOURCE_EMAIL, RESUME_EMAIL_SUBJECT_FILTER, RESUME_STORAGE_FOLDER_ID, RECRUITMENT_DATABASE_SPREADSHEET_ID, JOB_DESCRIPTION_FILE_ID, OPENAI_MODEL, OPENAI_MAX_TOKENS, OPENAI_TEMPERATURE. Ensure Google Drive folder and Google Sheets are set up with proper permissions. Test by manually triggering the Gmail Trigger node. Verify resume uploads in Google Drive ('Resume Archive') and data in Google Sheets ('Recruitment Database') for candidate_id, overall_fit_rating, and screening_status='completed'. Check Gmail node ('Recruitment Notification') for HTML email reports. Missing OAuth credentials cause 401 errors in Gmail or Google Drive nodes, logged in Google Sheets ('Error Logger') with error_message and recovery_action. Invalid resume formats (e.g., unsupported mimeType) trigger Condition node ('File Type Router') errors, routing to the Error Logger. Deploy by activating the workflow and ensuring environment variables are set. Monitor Google Sheets for candidate data and error logs. If text extraction fails (e.g., text.length < 50), the Condition node ('Text Quality Validator') routes to the Error Logger, providing error details for debugging.