Screen and triage Gmail resumes with Gemini and Supabase
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 11 nodes and runs on Gmail events. Along the way it connects Gmail, Google Gemini Chat Model and Supabase.
How it runs
Trigger: On Gmail events.
- Set Configuration (Edit Fields (Set)): sets 6 fields: job_title, required_skills, min_experience_years…
- Extract Resume Text (Extract from File): extracts data from a file (pdf)
- Screen Candidate (Basic LLM Chain): sends a prompt to an LLM, with model: Screening Chat Model; output parser: Screening Parser
- Log Candidate (Supabase): insert
- Route by Decision (Switch): routes items into 3 branches
- Notify Recruiter (Gmail): uses Gmail
- Save Rejection as Gmail Draft (Gmail): work with draft
- Label Email as Needs Review (Gmail): add labels
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
- Still check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll) (New Application Email).
Nodes used (9)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - Edit Fields (Set)
n8n-nodes-base.set - Extract from File
n8n-nodes-base.extractFromFile - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Supabase
n8n-nodes-base.supabase - Switch
n8n-nodes-base.switch - Gmail
n8n-nodes-base.gmail
From the author
Quick overview This workflow watches Gmail for new emails with resume attachments, extracts text from PDF, and uses Google Gemini to evaluate candidates against role requirements. It logs each screening result to Supabase, then either emails the recruiter,…