Automate CV screening & analysis with Telegram, Gemini AI & Google Workspace

Name: Automate CV screening & analysis with Telegram, Gemini AI & Google Workspace
Availability: InStock
Rating: 4.5 (41 reviews)
Author: Abdullah Alshiekh

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER 🎉 Early Black Friday Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

🧩 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, high-quality candidate data for fast decision-making.

📝 Description

This workflow is built to help HR teams collect and qualify CVs sent over Telegram. It verifies that a candidate submits a valid PDF, stores the file securely, extracts key information using AI, and logs everything neatly in Google Sheets.

🎯 Key Advantages for HR Teams

✅ Automatically filters out non-PDF and invalid messages ✅ Uses AI to extract clean, structured candidate data ✅ Links CV files to Google Sheets for easy HR access ✅ Eliminates manual data entry from physical CVs ✅ Provides a scalable CV pipeline via Telegram

🛠️ Features

Telegram bot for CV collection

MIME-type PDF validation

Google Drive integration for secure storage

Text extraction from PDFs

Gemini AI-powered CV parsing

Google Sheets integration for candidate logging

Merge logic to synchronize multiple streams

JSON-safe parsing for AI output

Automatic job title and experience categorization

Duplicate prevention through name-based matching

🔧 Requirements

A Telegram bot token

Google Drive API credentials

Google Sheets API credentials

Gemini API key (or another LLM)

n8n instance with relevant credentials configured

Candidates sending CVs in PDF format

🧠 Use Case Examples

Recruitment Agencies: Automate pre-screening and reduce manual effort

Small Startups: Collect high-quality CVs without paying for an ATS

Internship Programs: Quickly categorize applicants by experience

Remote Hiring: Accept global CVs via Telegram from mobile users

Freelancer Portals: Auto-log contractor profiles from incoming resumes

⚙️ Configuration Tips

1-Set up Telegram Bot API credentials 2-Configure Google Drive API access 3-Configure Google Sheets API access 4-Configure Google Gemini/PaLM API access 5-Replace all placeholder IDs with your actual values

If you need any help Get in Touch

Abdullah Alshiekh

0 workflows

Nodes

set gmail telegram agent google-gemini

Complexity

advanced

Published 02 Aug 2025

Likes 0

View on n8n.io Download Workflow

✨

Share Your Workflow

Have a great workflow to share? Join the n8n Creator Hub and help the community!

Submit Your Template How to Submit

Related Workflows

Sync your HRIS employee directory with Microsoft Teams, Coda, and Slack

# Employee Directory Sync – Microsoft Teams & Coda **⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template.** This workflow keeps your employee directory perfectly synchronized across your HRIS (or any REST-compatible HR database), Microsoft Teams, Coda docs, and Slack channels. It automatically polls the HR system on a schedule, detects additions or updates, and propagates those changes to downstream tools so everyone always has the latest employee information. ## Pre-conditions/Requirements ### Prerequisites - An active n8n instance (self-hosted or n8n cloud) - ScrapeGraphAI community node installed - A reachable HRIS API (BambooHR, Workday, Personio, or any custom REST endpoint) - Existing Microsoft Teams workspace and a team/channel for announcements - A Coda account with an employee directory table - A Slack workspace and channel where directory updates will be posted ### Required Credentials - **Microsoft Teams OAuth2** – To post adaptive cards or messages - **Coda API Token** – To insert/update rows in your Coda doc - **Slack OAuth2** – To push notifications into a Slack channel - **HTTP Basic / Bearer Token** – For your HRIS REST endpoint - **ScrapeGraphAI API Key** – (Only required if you scrape public profile data) ### HRIS Field Mapping | HRIS Field | Coda Column | Teams/Slack Field | |------------|-------------|-------------------| | `firstName`| `First Name`| First Name | | `lastName` | `Last Name` | Last Name | | `email` | `Email` | Email | | `title` | `Job Title` | Job Title | | `department`| `Department`| Department | *(Adjust the mapping in the Set and Code nodes as needed.)* ## How it works This workflow keeps your employee directory perfectly synchronized across your HRIS (or any REST-compatible HR database), Microsoft Teams, Coda docs, and Slack channels. It automatically polls the HR system on a schedule, detects additions or updates, and propagates those changes to downstream tools so everyone always has the latest employee information. ## Key Steps: - **Schedule Trigger**: Fires daily (or at your chosen interval) to start the sync routine. - **HTTP Request**: Fetches the full list of employees from your HRIS API. - **Code (Delta Detector)**: Compares fetched data with a cached snapshot to identify new hires, departures, or updates. - **IF Node**: Branches based on whether changes were detected. - **Split In Batches**: Processes employees in manageable sets to respect API rate limits. - **Set Node**: Maps HRIS fields to Coda columns and Teams/Slack message fields. - **Coda Node**: Upserts rows in the employee directory table. - **Microsoft Teams Node**: Posts an adaptive card summarizing changes to a selected channel. - **Slack Node**: Sends a formatted message with the same update. - **Sticky Note**: Provides inline documentation within the workflow for maintainers. ## Set up steps **Setup Time: 10-15 minutes** 1. **Import the workflow** into your n8n instance. 2. **Open Credentials** tab and create: - Microsoft Teams OAuth2 credential. - Coda API credential. - Slack OAuth2 credential. - HRIS HTTP credential (Basic or Bearer). 3. **Configure the HRIS HTTP Request node** - Replace the placeholder URL with your HRIS endpoint (e.g., `https://api.yourhr.com/v1/employees`). - Add query parameters or headers as required by your HRIS. 4. **Map Coda Doc & Table IDs** in the Coda node. 5. **Select Teams & Slack channels** in their respective nodes. 6. **Adjust the Schedule Trigger** to your desired frequency. 7. **Optional**: Edit the Code node to tweak field mapping or add custom delta-comparison logic. 8. **Execute the workflow manually once** to verify proper end-to-end operation. 9. **Activate** the workflow. ## Node Descriptions ### Core Workflow Nodes: - **Schedule Trigger** – Initiates the sync routine at set intervals. - **HTTP Request (Get Employees)** – Pulls the latest employee list from the HRIS. - **Code (Delta Detector)** – Stores the previous run’s data in workflow static data and identifies changes. - **IF (Has Changes?)** – Skips downstream steps when no changes were detected, saving resources. - **Split In Batches** – Iterates through employees in chunks (default 50) to avoid API throttling. - **Set (Field Mapper)** – Renames and restructures data for Coda, Teams, and Slack. - **Coda (Upsert Rows)** – Inserts new rows or updates existing ones based on email match. - **Microsoft Teams (Post Message)** – Sends a rich adaptive card with the update summary. - **Slack (Post Message)** – Delivers a concise change log to a Slack channel. - **Sticky Note** – Embedded documentation for quick reference. ### Data Flow: 1. **Schedule Trigger** → **HTTP Request** → **Code (Delta Detector)** 2. **Code** → **IF (Has Changes?)** - If **No** → **End** - If **Yes** → **Split In Batches** → **Set** → **Coda** → **Teams** → **Slack** ## Customization Examples ### Change Sync Frequency ```javascript // Inside Schedule Trigger { "mode": "everyDay", "hour": 6, "minute": 0 } ``` ### Extend Field Mapping ```javascript // Inside Set node items[0].json.phone = item.phoneNumber ?? ''; items[0].json.location = item.officeLocation ?? ''; return items; ``` ## Data Output Format The workflow outputs structured JSON data: ```json { "employee": { "id": "123", "firstName": "Jane", "lastName": "Doe", "email": "[email protected]", "title": "Senior Engineer", "department": "R&D", "status": "New Hire", "syncedAt": "2024-05-08T10:15:23.000Z" }, "destination": { "codaRowId": "row_abc123", "teamsMessageId": "msg_987654", "slackTs": "1715158523.000200" } } ``` ## Troubleshooting ### Common Issues 1. **HTTP 401 from HRIS API** – Verify token validity and that the credential is attached to the HTTP Request node. 2. **Coda duplicates rows** – Ensure the key column in Coda is set to “Email” and the Upsert option is enabled. ### Performance Tips - Cache HRIS responses in static data to minimize API calls. - Increase the Split In Batches size only if your API rate limits allow. **Pro Tips:** - Use n8n’s built-in Version Control to track mapping changes over time. - Add a second IF node to differentiate between “new hires” and “updates” for tailored announcements. - Enable Slack’s “threaded replies” to keep your #hr-updates channel tidy.

View

Score job applications and write AI feedback with OpenAI and Notion

# Screen resumes & save candidate scores to Notion with OpenAI This template helps you automate the initial screening of job candidates by analyzing resumes against your specific job descriptions using AI. ### 📺 How It Works The workflow automatically monitors a **Notion** database for new job applications. When a new candidate is added: 1. It checks if the candidate has already been processed to avoid duplicates. 2. It downloads the resume file (supporting both **PDF** and **DOCX** formats). 3. It extracts the raw text and sends it to **OpenAI** along with the specific job description and requirements. 4. The AI acts as a "Senior Technical Recruiter," scoring the candidate on skills, experience, and stability. 5. Finally, it updates the **Notion** entry with a fit score (0-100), a one-line summary, detected skills, and a detailed analysis. ### 📄 Notion Database Structure You will need two databases in Notion: **Jobs** (containing descriptions/requirements) and **Candidates** (containing resume files). * **Candidates DB Fields:** `AI Comments` (Text), `Resume Score` (Text), `Top Skills Detected` (Text), `Feedback` (Select), `One Line Summary` (Text), `Resume File` (Files & Media). * **Jobs DB Fields:** `Job Description` (Text), `Requirements` (Text). ### 👤 Who’s it for This workflow is for **recruiters, HR managers, founders**, and **hiring teams** who want to reduce the time spent on manual resume screening. Whether you are handling high-volume applications or looking for specific niche skills, this tool ensures every resume gets a consistent, unbiased first-pass review. ### 🔧 How to set up 1. **Create** the required databases in Notion (as described above). 2. **Import** the `.json` workflow into your n8n instance. 3. **Set up credentials** for Notion and OpenAI. 4. **Link** those credentials in the workflow nodes. 5. **Update Database IDs:** Open the "Fetch Job Description" and "On New Candidate" nodes and select your specific Notion databases. 6. **Run a test** with a sample candidate and validate the output in Notion. ### 📋 Requirements * An n8n instance (Cloud or Self-hosted) * A Notion account * OpenAI API Key (GPT-4o or GPT-4 Turbo recommended for best reasoning) ### 🧩 How to customize the workflow The system is fully modular. You can: * **Adjust the Persona:** In the `Analyze Candidate` agent nodes, edit the system prompt to change the "Recruiter" persona (e.g., make it stricter or focus on soft skills). * **Change Scoring:** Modify the scoring matrix in the prompt to weight "Education" or "Experience" differently. * **Filter Logic:** Add a node to automatically disqualify candidates below a certain score (e.g., < 50) and move them to a "Rejected" status in Notion. * **Multi-language:** Update the prompt to translate summaries into your local language if the resume is in English.

View

Schedule and track interviews using Calendly, Zoom, Asana, and Gmail

## 📊 Description This workflow automates interview scheduling by orchestrating Calendly, Zoom, Asana, and Gmail into a single, reliable hiring pipeline. When a candidate books an interview, the automation ensures the interview is properly scheduled, tracked, assigned, and communicated — without any manual follow-ups. The workflow listens for new Calendly bookings, normalizes scheduling data, creates a Zoom meeting, assigns a structured interview task in Asana, and notifies the appropriate interviewer via email. Conditional routing ensures the right stakeholders are involved while keeping candidate communications separate. Designed for real-world hiring operations, this automation provides consistency, accountability, and scalability as interview volume grows. ## 🔁 What this template does - Receives interview booking events from Calendly via webhook. - Normalizes and structures scheduling details such as time, timezone, and invitee information. - Creates a Zoom meeting automatically for the scheduled interview. - Routes the interview based on type (for example, HR or Technical). - Creates a structured Asana task assigned to the appropriate interviewer. - Stores interview context and Zoom meeting links directly in the Asana task. - Sends automated email notifications to interviewers with complete interview details. - Ensures interviewer-side visibility without exposing candidate-facing communications. - Executes fully automatically with no manual intervention. ## ⭐ Key benefits - Eliminates manual interview coordination and follow-ups - Ensures every interview has a correctly configured Zoom meeting - Keeps interviewers aligned through structured Asana task tracking - Provides reliable, role-based notifications - Reduces scheduling errors and missed interviews - Production-ready automation for growing hiring teams ## 🧩 Features - Calendly webhook-based trigger - Normalized interview data handling - Automated Zoom meeting creation - Interview-type routing and interviewer assignment - Interview-focused Asana task management - Automated Gmail notifications - Clean, interviewer-only communication flow - Scalable interview orchestration design ## 🔐 Requirements - Calendly account with webhook access enabled - Zoom API credentials - Asana OAuth2 credentials - Gmail OAuth2 credentials - n8n (cloud or self-hosted) ## 🎯 Target audience - Hiring managers - Technical interviewers - HR and recruitment teams - Startups and SaaS companies - Automation engineers building internal hiring pipelines

View

👨‍💻

Need Custom Automation?

N8N Automation Expert

Specialized in N8N automation, I design custom workflows that connect your tools and automate your processes.