AI candidate screening pipeline: LinkedIn to Telegram with Gemini & Apify

Name: AI candidate screening pipeline: LinkedIn to Telegram with Gemini & Apify
Availability: InStock
Rating: 4.5 (94 reviews)
Author: Dean Pike

$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

LinkedIn URL → Scrape → Match → Screen → Decide, all automated

This workflow automatically processes candidate LinkedIn profiles shared via Telegram, intelligently matches them to job descriptions, performs AI-powered screening analysis, and sends actionable summaries to your team in Telegram.

Good to know

Handles LinkedIn profile scraping via Apify API (extracts full profile data including experience, education, skills)
Built-in spam prevention: limits users to 3 LinkedIn profile submissions
Two-stage JD matching: prioritizes role mentioned in candidate's Telegram message, falls back to LinkedIn profile analysis if needed
Uses Google Gemini API for AI screening (generous free tier and rate limits, typically enough to avoid paying for API requests - check latest pricing at Google AI Pricing and rate limits documentation)
Automatic polling mechanism checks Apify extraction status up to 10 times (15-second intervals)
Complete audit trail logged in Google Sheets with unique submission IDs

Who's it for

Hiring teams and recruiters who want to streamline first-round screening for candidates who share LinkedIn profiles directly. Perfect for companies accepting applications via messaging platforms (Telegram, WhatsApp, etc.), especially useful fortech-savvy audiences and remote/global hiring.

How it works

Telegram bot receives message containing LinkedIn profile URL from candidate
Validates URL format and checks spam prevention (max 3 submissions per Telegram username)
Sends confirmation message to candidate and notifies internal talent team via Telegram group
Extracts clean LinkedIn URL and initiates Apify scraping job
Polls Apify API up to 10 times (15-second intervals) until profile extraction completes
AI agent matches candidate to best-fit job description by analyzing Telegram message context first (if candidate mentioned a role), or LinkedIn profile content as fallback (selects up to 3 potential JD matches)
If multiple JDs matched, second AI agent selects the single best fit based on detailed profile analysis
AI recruiter agent analyzes LinkedIn profile against selected JD and generates structured screening report (strengths, weaknesses, risk/reward factors, overall fit score 0-10 with justification)
Logs complete analysis to Google Sheets tracker with unique submission ID
Sends formatted summary to Telegram group with candidate details, matched JD, and overall fit score

Requirements

Telegram Bot Token (Create bot via @BotFather)
Apify account with API token (Sign up for free tier)
Google Drive account (OAuth2)
Google Sheets account (OAuth2)
Google Gemini API key (Get free key here)
Google Drive folder for Job Descriptions (as PDFs or Google Docs)
Telegram group for internal talent team notifications

How to set up

Create Telegram bot and internal Telegram chat group with new bot:
- Message @BotFather on Telegram
- Send /newbot and follow instructions to create your bot
- Save the API token provided
- Create Telegram group chat and invite your new bot + invite the @GetIDs bot
- Note down the group chat ID (How to get group chat ID)
Setup Apify:
- Sign up at Apify
- Get your API token from Settings
- Note: Free tier includes sufficient scraping credits for testing and production ($0.01 per successful LinkedIn profile enriched, a free monthly limit of $5.00) - LinkedIn profile scraper "actor" details
Create Google Sheet:
- Create new sheet named "LinkedIn Profile AI Candidate Screening"
- Add columns: Submission ID, Date, LinkedIn Profile URL, First Name, Last Name, Email (if known), Telegram Username, Strengths, Weaknesses, Risk Factor, Reward Factor, JD Match, Overall Fit, Justification
- Copy the spreadsheet ID from URL
Setup Google Drive folder:
- Create folder named "Job Descriptions"
- Upload your JD files (PDFs or Google Docs) with clear, descriptive filenames
- Copy the folder ID from URL
Configure workflow nodes:
- In "Receive Telegram Msg to Recruiter Bot" node: Add Telegram API credentials
- In "Extract LinkedIn Profile Information" node: Replace YOUR_APIFY_API_TOKEN with your Apify token
- In "Check LinkedIn Profile Extraction Status" node: Replace YOUR_APIFY_API_TOKEN with your Apify token
- In "Get Fully Extracted LinkedIn Profile Data" node: Replace YOUR_APIFY_API_TOKEN with your Apify token
- In "Access JD Files" node: Update folder ID to your "Job Descriptions" folder
- In "Get All Rows Matching Telegram Username" node: Select your Google Sheet
- In "Add Candidate Analysis in GSheet" node: Select your Google Sheet and verify column mappings
- In "Send Msg to Internal Talent Group" node: Update chat ID to your Telegram group chat ID
- In "Send Review Completed Msg to Talent Group" node: Update chat ID and Google Sheet URL
Add your company description:
- In "JD Matching Agent" system message: Replace company description with your details
- In "Detailed JD Matching Agent" system message: Replace company description with your details
- In "Recruiter Scoring Agent" system message: Update company description
Test the workflow:
- Send a LinkedIn profile URL to your bot from Telegram
- Monitor execution to ensure all nodes run successfully
- Check Google Sheets for logged results
Activate workflow

Customizing this workflow

Change spam limits: Edit "Spam Check: Sent <4 LinkedIn Profiles?" node to adjust maximum submissions (currently 3)
Adjust polling attempts: Edit "Checked 10x for LinkedIn Profile Data?" node to change maximum polling attempts (currently 10) or modify wait time in "Wait for LinkedIn Profile" node (currently 15 seconds)
Change JD matching logic: Edit "JD Matching Agent" node prompt to adjust how LinkedIn profiles are matched to roles (e.g., weight current role vs. overall experience)
Modify screening criteria: Edit "Recruiter Scoring Agent" node system message to focus on specific qualities (culture fit, leadership potential, technical depth, industry experience, etc.)
Add more messaging platforms: Add nodes to support WhatsApp, Discord, or other messaging platforms using similar URL-based triggers
Customize Telegram messages: Edit notification nodes to change formatting, add emojis, or include additional candidate data
Auto-proceed logic: Add IF node after screening to auto-proceed candidates with fit score above threshold (e.g., 8+/10) and trigger different notification paths
Add candidate responses: Connect nodes to automatically message candidates back via Telegram (confirmation, rejection, interview invite)
Add interview scheduling: For approved candidates, send Telegram message with Cal.com or Calendly link so they can book their interview
Enrich with additional data: Add nodes to cross-reference candidate data with other sources (GitHub, Twitter/X, company websites)
Multi-language support: Add translation nodes to support candidates submitting profiles in different languages
Add human approval step: Create buttons in Telegram group messages for instant Approve/Reject decisions that update Google Sheets

Pro tip: Add your Telegram bot to your company's careers page with instructions like: "Want fast-track screening? Share your LinkedIn profile with our AI recruiter: @YourBotName"

Troubleshooting

Telegram bot not responding: Ensure bot token is correct in "Receive Telegram Msg to Recruiter Bot" node, and users have sent /start to your bot at least once
"LinkedIn profile URL invalid" error: Check that candidates are sending full URLs in format https://www.linkedin.com/in/username (not shortened links or text without URL)
Apify extraction failing: Verify Apify API token is correctly set in all three HTTP Request nodes ("Extract LinkedIn
Profile Information", "Check LinkedIn Profile Extraction Status", "Get Fully Extracted LinkedIn Profile Data")
LinkedIn extraction timeout: Increase polling attempts in "Checked 10x for LinkedIn Profile Data?" node (currently 10) or increase wait time in "Wait for LinkedIn Profile" node (currently 15 seconds)
Spam check blocking valid users: Check "Get All Rows Matching Telegram Username" node is pointing to correct Google Sheet, and adjust limit in "Spam Check: Sent <4 LinkedIn Profiles?" node if needed
JD matching returns no results: Check "Access JD Files" node folder ID points to your Job Descriptions folder, and JD files are named clearly (e.g., "Marketing Director JD.pdf")
JD matching is not relevant for my company: Update the "Company Description" in the System Messages in all three AI agent nodes ("JD Matching Agent", "Detailed JD Matching Agent", "Recruiter Scoring Agent")
"Can't find matching JD": Ensure candidate's Telegram message mentions role name OR their LinkedIn profile clearly indicates relevant experience for available JDs
Google Sheets errors: Verify sheet name is "LinkedIn Profile AI Candidate Screening" and column headers exactly match workflow expectations (Submission ID, Date, LinkedIn Profile URL, First Name, Last Name, etc.)
Telegram group notifications not appearing: Verify chat ID is correct in "Send Msg to Internal Talent Group" and "Send Review Completed Msg to Talent Group" nodes (use negative number for group chats, e.g., -4954246611)
Missing candidate data in Google Sheets: LinkedIn profile may be incomplete - verify Apify successfully extracted data by checking "Get Fully Extracted LinkedIn Profile Data" node output
Loop counter not working: Check "Restore Loop Counter" code node references correct node names ("Checked 10x for LinkedIn Profile Data?" and "Initialize Loop Counter to Poll for Completion")
401/403 API errors: Re-authorize all OAuth2 credentials (Google Drive, Google Sheets) and verify Apify and Telegram API tokens are valid
AI analysis quality issues: Edit system prompts in "JD Matching Agent", "Detailed JD Matching Agent", and "Recruiter Scoring Agent" nodes to refine screening criteria and provide more context about your hiring needs
Gemini API rate limit errors: Check your usage at Google AI Studio and consider upgrading to paid tier if exceeding free tier limits (see rate limits documentation)

Sample Outputs

Google Sheets - LinkedIn AI Candidate Screening - sample

Telegram messages between AI recruiter bot and job applicant

Telegram messages from AI recruiter bot in internal group chat

Dean Pike

0 workflows

Nodes

set gmail telegram agent google-gemini

Complexity

advanced

Published 22 Oct 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.