Automate CV screening & analysis with Telegram, Gemini AI & Google Workspace
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 12 nodes and runs on Telegram events (message). Along the way it connects Telegram, Google Gemini Chat Model, Google Drive and Google Sheets.
How it runs
Trigger: On Telegram events (message).
- File Validation (If): checks a condition and branches into true / false
- Download CV File (HTTP Request): calls an HTTP API
- PDF Request (Telegram): uses Telegram
- Download Actual File (HTTP Request): calls an HTTP API
- Store CV (Google Drive): uses Google Drive
- Merge: merges the data from its input branches
- Extract cv content (Extract from File): extracts data from a file (pdf)
- Qualify CV Agent (AI Agent): runs an AI agent, with model: Google Gemini Chat Model
- Clean & Map Extracted Data (Edit Fields (Set)): sets 5 fields: full name, phone number, experiene…
- Save Candidate Info to Sheet (Google Sheets): append or update
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.
Nodes used (11)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Extract from File
n8n-nodes-base.extractFromFile - AI Agent
@n8n/n8n-nodes-langchain.agent - Telegram
n8n-nodes-base.telegram - Google Drive
n8n-nodes-base.googleDrive - Merge
n8n-nodes-base.merge - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets
From the author
🧩 What Problem Does It Solve? Manually reviewing CVs from Telegram job applicants is slow, error-prone, and often inconsistent. This workflow automates the collection, analysis, and storage of CVs — saving HR teams hours while ensuring structured,…