HumationHuman + Automation
Back to Catalog

Automate job matching with Gemini AI, Decodo scraping & resume analysis to Telegram

Rully SaputraRully Saputra
65 views
2/3/2026
conditional-logicdata-extractionemailautomationregex
Official Page

AI Job Matcher with Decodo, Gemini AI & Resume Analysis

Sign up for Decodo — get better pricing here

Who’s it for

This workflow is built for job seekers, recruiters, founders, automation builders, and data engineers who want to automate job discovery and intelligently match job listings against resumes using AI.

It’s ideal for anyone building job boards, candidate matching systems, hiring pipelines, or personal job alert automations using n8n.

What this workflow does

This workflow automatically scrapes job listings from SimplyHired using Decodo residential proxies, extracts structured job data with a Gemini AI agent, downloads resumes from Google Drive, extracts and summarizes resume content, and surfaces the most relevant job opportunities.

The workflow stores structured results in a database and sends real-time notifications via Telegram, creating a scalable and low-maintenance AI-powered job matching pipeline.

How it works

  1. A schedule trigger starts the workflow automatically
  2. Decodo fetches job search result pages from SimplyHired
  3. Job card HTML is extracted from the page
  4. A Gemini AI agent converts raw HTML into structured job data
  5. Resume PDFs are downloaded from Google Drive
  6. Resume text is extracted from PDF files
  7. A Gemini AI agent summarizes key resume highlights
  8. Job and resume data are stored in a database
  9. Matching job alerts are sent via Telegram

How to set up

  1. Add your Decodo API credentials
  2. Add your Google Gemini API key
  3. Connect Google Drive for resume access
  4. Configure your Telegram bot
  5. Set up your database (Google Sheets by default)
  6. Update the job search URL with your keywords and location

Requirements

  • Self-hosted n8n instance
  • Decodo account (community node)
  • Google Gemini API access
  • Google Drive access
  • Telegram Bot token
  • Google Sheets or another database

> Note: This template uses a community node (Decodo) and is intended for self-hosted n8n only.

How to customize the workflow

  • Replace SimplyHired with another job board or aggregator
  • Add job–resume matching or scoring logic
  • Extend the resume summary with custom fields
  • Swap Google Sheets for PostgreSQL, Supabase, or Airtable
  • Route notifications to Slack, Email, or Webhooks
  • Add pagination or multi-resume processing

Automate Job Matching with Gemini AI: Decodo Scraping & Resume Analysis to Telegram

This n8n workflow automates the process of matching job descriptions with resumes, leveraging AI for analysis and delivering results via Telegram. It's designed to streamline recruitment by extracting job details from web pages, analyzing candidate resumes, and then using Google Gemini AI to find the best matches.

What it does

This workflow performs the following key steps:

  1. Triggers on Schedule: The workflow runs automatically at predefined intervals.
  2. Scrapes Job Postings: It fetches job descriptions from a specified URL using an HTML node.
  3. Extracts Resume Data: It reads resume information from a Google Drive file (likely a PDF or docx) using the "Extract from File" node.
  4. Splits Resume Data: If the resume file contains multiple sections or items, it splits them out for individual processing.
  5. Summarizes Resume: Uses an AI Summarization Chain (LangChain) to create a concise summary of the resume content.
  6. Analyzes Job & Resume with AI: Employs a Google Gemini Chat Model and an AI Agent (LangChain) to compare the job description with the summarized resume, identifying key matching criteria and generating a match score or relevant insights.
  7. Structures AI Output: A Structured Output Parser (LangChain) ensures the AI's response is in a usable, structured format (e.g., JSON).
  8. Stores Data in Google Sheets: The processed job and resume matching data is recorded in a Google Sheet for tracking and further analysis.
  9. Sends Telegram Notification: A summary of the job match results, including relevant details, is sent to a specified Telegram chat.
  10. Edits Fields: A "Set" node is used to manipulate or format data at various stages, ensuring it's in the correct structure for subsequent nodes.
  11. Provides Notes: Sticky notes are included for documentation and explanation within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Configured credentials for Google Sheets to store data.
  • Google Drive Account: Configured credentials for Google Drive to access resume files.
  • Telegram Bot Token & Chat ID: A Telegram bot set up and its token/chat ID configured for sending notifications.
  • Google Gemini API Key: Access to Google Gemini AI for the chat model and agent functionalities. This will be configured within the LangChain nodes.
  • Decodo Scraping (Implicit): The HTML node implies a target URL for job postings that can be scraped.
  • Resume Files: Resumes stored in Google Drive in a format that the "Extract from File" node can process (e.g., PDF, DOCX).

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your Google Drive credentials.
    • Configure your Telegram credentials (Bot Token and Chat ID).
    • Configure your Google Gemini credentials (API Key) within the "Google Gemini Chat Model" and "AI Agent" nodes.
  3. Update Node Parameters:
    • Schedule Trigger (Node 839): Adjust the schedule to your desired frequency for running the job matching.
    • HTML (Node 842): Update the URL to the job board or specific job posting page you want to scrape. Configure the CSS selectors to extract the job description details correctly.
    • Google Drive (Node 58): Specify the file ID or path to the resume file(s) you want to analyze.
    • Extract from File (Node 1235): Ensure this node is correctly configured to parse your resume file types.
    • Google Sheets (Node 18): Specify the Spreadsheet ID and Sheet Name where you want to store the job matching results. Define the columns for mapping the data.
    • Telegram (Node 49): Ensure the correct Chat ID is set for sending notifications. Customize the message content to include relevant job match details.
    • AI Agent (Node 1119), Summarization Chain (Node 1121), Structured Output Parser (Node 1179), Google Gemini Chat Model (Node 1262): Review and adjust any model parameters or prompts as needed to optimize the AI's analysis for your specific job matching criteria.
    • Edit Fields (Node 38): Customize this node to transform or clean data as necessary before sending it to Google Sheets or Telegram.
  4. Activate the Workflow: Once all configurations are complete, activate the workflow to start automating your job matching process.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31