Screen, score and route job applicants with Gemini, Gmail, Sheets and Slack
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 workflow has 14 nodes and runs on a schedule (every day at 08:00). Along the way it connects Google Sheets, Slack and Gmail. It also calls generativelanguage.googleapis.com over HTTP.
How it runs
Trigger: On a schedule (every day at 08:00).
- Get New Applicants (Google Sheets): uses Google Sheets
- Set Job Requirements (Edit Fields (Set)): sets 5 fields: jobTitle, mustHave, niceToHave…
- Build Screening Prompt (Code): runs custom JavaScript code
- Score Applicant with Gemini (HTTP Request): calls generativelanguage.googleapis.com (POST)
- Parse Score (Code): runs custom JavaScript code
- Report Scoring Failure (Slack): uses Slack
- Update Applicant Row (Google Sheets): append or update
- Route by Verdict (Switch): routes items into 3 branches
- Notify Hiring Team (Slack): uses Slack
- Flag for Human Review (Slack): uses Slack
…plus 3 more steps. See the full node list below.
Services it uses
HTTP calls to: generativelanguage.googleapis.com
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.
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets
n8n-nodes-base.googleSheets - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Gmail
n8n-nodes-base.gmail
From the author
Quick Overview This workflow runs daily to pull job applicants from Google Sheets, score each candidate against role requirements using the Google Gemini API, log results back to Google Sheets, and notify a Slack channel when an applicant meets or exceeds a…