🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Telegram + Google Sheets, LinkedIn screening summaries

Telegram + Google Sheets, LinkedIn screening summaries - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram + Google Sheets, LinkedIn screening summaries - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

First-round screening sounds simple until it’s not. LinkedIn links arrive in chats, context gets lost, different reviewers focus on different things, and suddenly your “quick look” turns into a messy thread nobody trusts.

This is the kind of chaos that slows recruiters down, but hiring managers feel it too. Even a small business owner doing their own hiring gets stuck. A LinkedIn screening automation gives you consistent summaries, a shared record in Google Sheets, and clearer next steps without chasing messages.

You send a LinkedIn URL in Telegram. The workflow screens it against your job descriptions, scores fit, and posts a structured summary to your team. Here’s what that looks like in practice, and what you need to run it.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Telegram + Google Sheets, LinkedIn screening summaries

The Challenge: Consistent LinkedIn Screening Without the Chaos

Most teams don’t fail at hiring because they lack candidates. They fail because early screening is inconsistent and scattered. Someone drops a LinkedIn URL in Telegram, one person skims it on mobile, another opens it later on desktop, and both walk away with different conclusions. Then comes the back-and-forth: “Did they actually have X?”, “Which role are they applying for?”, “Where did we put that profile again?” Meanwhile, good candidates wait, and your team spends real time repeating the same review work.

It adds up fast. Here’s where it breaks down.

  • Reviewers use different mental checklists, so “screening” becomes opinion instead of a repeatable process.
  • Job description matching is often guessed from a quick glance at a headline, which leads to the wrong pipeline and wasted interviews.
  • Telegram threads bury important context, so you re-open profiles and re-ask the same questions later.
  • Manual logging into Google Sheets gets skipped when things get busy, so you lose your audit trail and can’t explain decisions clearly.

The Fix: Telegram to AI Screening Summary + Google Sheets Log

This workflow turns a simple Telegram message into a structured, repeatable screening process. A candidate (or sourcer) sends a LinkedIn profile URL to your Telegram bot. The automation validates the link, blocks obvious spam by limiting submissions per user, and immediately confirms receipt so nobody wonders if it “went through.” Then it scrapes the full LinkedIn profile data through Apify, waits for extraction to complete (with automatic polling), and hands the cleaned profile to AI agents that match the candidate to the best-fitting job description from your Google Drive folder. Finally, it generates a recruiter-style screening report: strengths, weaknesses, risk/reward factors, and a 0–10 fit score with justification. Everything is logged to Google Sheets with a unique submission ID, and your internal Telegram group gets a formatted summary to review together.

The workflow starts in Telegram with a LinkedIn URL. In the middle, Apify extracts profile data and the AI agents handle JD matching and screening analysis. The output lands in two places: a clean Google Sheets tracker for your audit trail, and a Telegram summary for fast team decisions.

What Changes: Before vs. After

Real-World Impact

Say your team screens 20 LinkedIn profiles a week from Telegram. Manually, it’s easy to spend about 10 minutes reviewing the profile, then another 5 minutes writing a summary and logging it into Google Sheets, which is roughly 5 hours a week. With this workflow, the “human time” becomes sending a URL (about a minute) and reading the summary in your internal Telegram group. The scrape and AI analysis run in the background, so you usually get those hours back without rushing the decision.

Requirements

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram to receive LinkedIn URLs and notify teams.
  • Google Sheets to store screening logs and IDs.
  • Apify API token (get it from Apify account settings).
  • Google Gemini API key (get it from Google AI Studio).

Skill level: Intermediate. You’ll connect accounts, paste a few API tokens, and update folder/chat IDs.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

Telegram message triggers the run. A user sends a LinkedIn profile URL (and often a role name) to your Telegram bot, which validates the URL and checks the spam rule (max 3 submissions per Telegram username).

Profile data gets extracted and cleaned. The workflow calls Apify to scrape the LinkedIn profile, then polls up to 10 times (about 15 seconds apart) until the enriched profile data is ready. If the scrape takes longer, it waits instead of failing silently.

AI matches the candidate to the right JD. It checks the role mentioned in Telegram first. If that’s missing or vague, it falls back to the LinkedIn content itself and selects up to three possible job description matches from your Google Drive folder, then narrows it down to one.

Screening results go to Sheets and your team chat. A recruiter-style report is generated (strengths, weaknesses, risk/reward, fit score with justification), logged into Google Sheets with a unique submission ID, and summarized in your internal Telegram group for quick review.

You can easily modify the spam limit to allow more submissions, or tighten screening criteria to focus on culture fit or technical depth based on your needs. See the full implementation guide below for customization options.

Watch Out For

  • Telegram bot permissions can trip you up in group chats. If notifications don’t appear, confirm the chat ID is correct and the bot is allowed to post messages.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Similar Automations

If your team also collects resumes in a shared Drive folder, Google Drive to Google Sheets, resumes logged and scored pairs nicely with this Telegram-based LinkedIn screening automation so every candidate ends up in one consistent tracker.

For teams that want to move from “screened” to “ranked list” quickly, Google Drive to Google Sheets, ranked CV shortlist helps you shortlist in batches after the initial LinkedIn screening summaries are done.

When sourcing turns into outreach, LinkedIn + Gmail: outreach drafts ready to review makes the handoff smoother by generating drafts your team can approve instead of writing each message from scratch.

Need a simpler lead-style pipeline before screening? LinkedIn + Google Sheets: outreach leads, ready to send gives you a structured outbound list so you’re not hunting through bookmarks and DMs.

Finally, if you already live in Airtable for recruiting ops, Apollo to Airtable, smarter candidate shortlists complements this workflow by feeding higher-volume sourcing into the same decision process.


Quick reference:

Common Questions

How quickly can I implement this LinkedIn screening automation?

About an hour if you already have your tokens and Google Drive folder ready.

Can non-technical teams implement this LinkedIn screening automation?

Yes, but someone needs to be comfortable pasting API keys and updating a few IDs. No coding, just careful setup.

Is n8n free to use for this LinkedIn screening automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Apify scraping costs (often a few dollars a month for modest volume) and any Gemini usage if you exceed the free tier.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

How do I adapt this LinkedIn screening automation solution to my specific challenges?

You can raise or lower the submission limit by editing the spam check node (the one that caps users at 3 submissions). For matching, update the system message in the “JD Matching Agent” and “Detailed JD Matching Agent” so it weights what you care about (current title, industry, leadership, technical depth). For screening quality, tweak the “Recruiter Scoring Agent” prompt to add your must-haves and deal-breakers, then keep the output structure the same so your Google Sheets log stays clean.

Why is my Telegram connection failing in this LinkedIn screening automation workflow?

Usually it’s a bad bot token or the user never sent /start to the bot. In group chats, it can also be the wrong chat ID (group IDs are often negative numbers) or the bot lacking permission to post. If the bot responds in private chat but not in the internal talent group, check the group notification nodes and confirm the bot is actually in that group.

What’s the capacity of this LinkedIn screening automation solution?

On n8n Cloud Starter, you’re generally fine for a small team screening a steady flow each week. If you self-host, there’s no execution limit (it mostly depends on your server) and this workflow’s main bottleneck becomes Apify extraction time plus AI rate limits. Practically, it works best as a “one profile in, one summary out” pipeline, and you can queue plenty of submissions as long as you’re not hitting API limits.

Is this LinkedIn screening automation better than using Zapier or Make?

Often, yes. This workflow has polling, branching logic, and multi-stage AI decisions, and n8n handles that kind of flow without forcing awkward workarounds. Self-hosting also matters if your screening volume spikes, because you’re not paying per tiny step the way many tools price it. That said, Zapier or Make can be perfectly fine for lightweight “log a link to a sheet” automations. If you want a quick sanity check before you build, Talk to an automation expert.

Once this is running, your team stops debating what they think they saw on LinkedIn and starts working from the same structured summary. Set it up once, then let the workflow do the repetitive part.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.