HumationHuman + Automation
Back to Catalog

AI job relevancy scorer: Search LinkedIn Jobs with GPT-4o-mini & Google Sheets

YasirYasir
888 views
2/3/2026
AirtableSynchronizationData ManagementCalendar ManagementGoogle Calendar
Official Page

🧠 Workflow Overview — AI-Powered Jobs Scraper & Relevancy Evaluator

This workflow automates the process of finding highly relevant job listings based on a user’s resume, career preferences, and custom filters. It scrapes fresh job data, evaluates relevance using OpenAI GPT models, and automatically appends the results to your Google Sheet tracker — while skipping any jobs already in your sheet, so you don’t have to worry about duplicates.

Perfect for recruiters, job seekers, or virtual assistants who want to automate job research and filtering.

⚙️ What the Workflow Does

  1. Takes user input through a form — including resume, preferences, target score, and Google Sheet link.
  2. Fetches job listings via an Apify LinkedIn Jobs API actor.
  3. Filters and deduplicates results (removes duplicates and blacklisted companies).
  4. Evaluates job relevancy using GPT-4o-mini, scoring each job (0–100) against the user’s resume & preferences.
  5. Applies a relevancy threshold to keep only top-matching jobs.
  6. Checks your Google Sheet for existing jobs and prevents duplicates.
  7. Appends new, relevant jobs directly into your provided Google Sheet.

📋 What You’ll Get

  • A personal Job Scraper Form (public URL you can share or embed).

  • Automatic job collection & filtering based on your inputs.

  • Relevance scoring (0–100) for each job using your resume and preferences.

  • Real-time job tracking Google Sheet that includes:

    • Job Title
    • Company Name & Profile
    • Job URLs
    • Location, Salary, HR Contact (if available)
    • Relevancy Score

🪄 Setup Instructions

1. Required Accounts

You’ll need:

  • ✅ n8n account (self-hosted or Cloud)
  • ✅ Google account (for Sheets integration)
  • ✅ OpenAI account (for GPT API access)
  • ✅ Apify account (to fetch job data)

2. Connect Credentials

In your n8n instance:

  1. Go to Credentials → Add New:

    • Google Sheets OAuth2 API

      • Connect your Google account.

    • OpenAI API

      • Add your OpenAI API key.

    • Apify API

      • Replace <your_apify_api> with your apify api key.

  2. Set Up Apify API

    Get your Apify API key

    • Visit: https://console.apify.com/settings/integrations

    • Copy your API key.

    Rent the required Apify actor before running this workflow

    • Go to: https://console.apify.com/actors/BHzefUZlZRKWxkTck/input

    • Click “Rent Actor”.

Once rented, it can be used by your Apify account to fetch job listings.

3. Set Up Your Google Sheet

  1. Make a copy of this template: 📄 Google Sheet Template
  2. Enable Edit Access for anyone with the link.
  3. Copy your sheet’s URL — you’ll provide this when submitting the workflow form.

4. Deploy & Run

  1. Import this workflow (jobs_scraper.json) into your n8n workspace.

  2. Activate the workflow.

  3. Visit your form trigger endpoint (e.g. https://your-n8n-domain/webhook/jobs-scraper).

  4. Fill out the form with:

    • Job title(s)
    • Location
    • Contract type, Experience level, Working mode, Date posted
    • Target relevancy score
    • Google Sheet link
    • Resume text
    • Job preferences or ranking criteria

  5. Submit — within minutes, new high-relevance job listings will appear in your Google Sheet automatically.

🧩 Example Use Cases

  • Automate daily job scraping for clients or yourself.
  • Filter jobs by AI-based relevance instead of keywords.
  • Build a smart job board or job alert system.
  • Support a career agency offering done-for-you job search services.

💡 Tips

  • Adjust the “Target Relevancy Score” (e.g., 70–85) to control how strict the filtering is.
  • You can add your own blacklisted companies in the Filter & Dedup Jobs node.

AI Job Relevancy Scorer: Search LinkedIn Jobs with GPT-4o Mini & Google Sheets

This n8n workflow automates the process of finding relevant job postings on LinkedIn, scoring their relevancy using OpenAI's GPT-4o Mini, and storing the results in a Google Sheet. It simplifies the job search by intelligently filtering and evaluating opportunities based on your criteria.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data via an n8n form. This form likely collects job search parameters (e.g., desired role, keywords, location).
  2. Searches LinkedIn Jobs: It performs an HTTP request to a LinkedIn job search API (or a similar job board API) using the parameters provided in the form submission.
  3. Scores Job Relevancy with OpenAI: For each job found, it sends the job description and the user's criteria to OpenAI's GPT-4o Mini model. The AI then scores the job's relevancy (e.g., on a scale of 1-10) and provides a brief explanation.
  4. Filters Relevant Jobs: An 'If' node checks the relevancy score provided by OpenAI. Jobs exceeding a certain relevancy threshold are passed to the next step.
  5. Processes and Formats Data: A 'Code' node processes the relevant job data, extracting key fields and formatting them for storage.
  6. Stores Results in Google Sheets: The highly relevant job postings, along with their AI-generated scores and explanations, are appended as new rows to a specified Google Sheet.
  7. Merges Data (Implicit): A 'Merge' node is present, suggesting that different branches of the workflow (e.g., successful AI scoring vs. jobs that didn't meet the threshold) might eventually converge, though the current JSON doesn't show explicit connections to it.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Google Sheets Account: To store the job search results. You'll need to set up a Google Sheets credential in n8n.
  • OpenAI API Key: An OpenAI API key with access to GPT-4o Mini (or a similar model) for job relevancy scoring. You'll need to set up an OpenAI credential in n8n.
  • LinkedIn Job Search API (or similar): Access to an API that can programmatically search for jobs on LinkedIn or another job board. This will be configured in the HTTP Request node.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up a Google Sheets credential.
    • OpenAI: Set up an OpenAI credential with your API key.
  3. Configure the "On form submission" Trigger:
    • Define the form fields that will collect job search criteria (e.g., jobTitle, keywords, location, userProfileSummary).
  4. Configure the "HTTP Request" Node:
    • Update the URL, method, headers, and body to interact with your chosen job search API. Map the form submission data to the API's parameters.
  5. Configure the "OpenAI" Node:
    • Ensure the model is set to gpt-4o-mini (or your preferred model).
    • Craft a prompt that instructs the AI to score job relevancy based on the job description (from the HTTP Request node) and the user's criteria (from the Form Trigger).
  6. Configure the "If" Node:
    • Set the condition to filter jobs based on the relevancy score returned by the OpenAI node (e.g., {{ $json.relevancyScore > 7 }}).
  7. Configure the "Code" Node:
    • Adjust the JavaScript code to extract and format the specific job details you want to save to Google Sheets.
  8. Configure the "Google Sheets" Node:
    • Specify the Google Sheet ID and the sheet name where the job data should be appended.
    • Map the output from the "Code" node to the columns in your Google Sheet.
  9. Activate the Workflow: Once configured, activate the workflow.
  10. Use the n8n Form: Access the public URL for the "On form submission" trigger and submit your job search criteria. The workflow will then run, process the jobs, score them, and update your Google Sheet with relevant opportunities.

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

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93