January 22, 2026

Gmail to Google Sheets, scored resumes in one view

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your inbox turns into a hiring queue. Resumes arrive as PDFs, DOCX files, and the occasional weird text attachment, and then someone has to download everything, rename files, scan for basics, and paste notes into a spreadsheet that’s never quite up to date.

Recruiters feel the pain first, because speed matters. But a hiring manager trying to compare candidates and a small operations lead juggling HR on the side gets buried too. This Gmail Sheets resumes automation turns incoming resume emails into a consistent, scored row in Google Sheets, usually in minutes.

You’ll see how the workflow captures attachments, extracts text, uses GPT-4o to score candidates against your role requirements, and logs everything in one review-ready view.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Gmail to Google Sheets, scored resumes in one view

Click to explore

flowchart LR

    subgraph sg0["Incoming Email Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Incoming Email Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:cog", form: "rounded", label: "Store in Drive", pos: "b", h: 48 }
        n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "File Type Router", pos: "b", h: 48 }
        n3@{ icon: "mdi:cog", form: "rounded", label: "Download Doc PDF", pos: "b", h: 48 }
        n4@{ icon: "mdi:cog", form: "rounded", label: "Parse PDF Content", pos: "b", h: 48 }
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Convert DOCX File"]
        n6@{ icon: "mdi:cog", form: "rounded", label: "Fetch Doc Text", pos: "b", h: 48 }
        n7@{ icon: "mdi:cog", form: "rounded", label: "Grab TXT File", pos: "b", h: 48 }
        n8@{ icon: "mdi:cog", form: "rounded", label: "Read TXT Content", pos: "b", h: 48 }
        n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Normalize Resume Fields", pos: "b", h: 48 }
        n10@{ icon: "mdi:swap-vertical", form: "rounded", label: "Define Role Details", pos: "b", h: 48 }
        n11@{ icon: "mdi:robot", form: "rounded", label: "AI Screening Review", pos: "b", h: 48 }
        n12@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
        n13@{ icon: "mdi:robot", form: "rounded", label: "Structured Result Parser", pos: "b", h: 48 }
        n14@{ icon: "mdi:robot", form: "rounded", label: "Extract Candidate Details", pos: "b", h: 48 }
        n15@{ icon: "mdi:database", form: "rounded", label: "Append Sheet Record", pos: "b", h: 48 }
        n3 --> n4
        n7 --> n8
        n12 -.-> n11
        n12 -.-> n14
        n1 --> n2
        n0 --> n1
        n6 --> n9
        n10 --> n11
        n4 --> n9
        n2 --> n3
        n2 --> n5
        n2 --> n7
        n8 --> n9
        n5 --> n6
        n11 --> n14
        n14 --> n15
        n9 --> n10
        n13 -.-> n11
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n11,n13,n14 ai
    class n12 aiModel
    class n2 decision
    class n15 database
    class n5 api
    classDef customIcon fill:none,stroke:none
    class n5 customIcon

The Problem: Resume screening becomes inbox triage

Manual resume screening is the kind of work that looks “quick” until you do it 30 times in a row. You open an email, download the attachment, realize it’s a DOCX, convert it, skim for role basics, then try to remember what you thought about the last candidate. Meanwhile, someone asks, “Who are our top three?” and you have to reconstruct your own opinions from scattered notes. Errors creep in too: wrong file saved to the wrong folder, duplicate entries, missed attachments, and inconsistent scoring because everyone evaluates differently when they’re rushed.

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

Each resume creates a mini checklist of downloads, naming, saving, and note-taking that quietly eats about 10 minutes per candidate.
PDFs, DOCX, and TXT formats force you into extra steps, and those steps are where people miss details.
When feedback isn’t standardized, “good candidate” means something different depending on who reviewed the file.
Spreadsheets fall behind, so hiring decisions get made from memory instead of a reliable, current view.

The Solution: Gmail-to-Sheets AI resume screening you can trust

This workflow watches your Gmail inbox for resume emails and grabs the attachment as soon as it arrives. It stores the file in Google Drive so you have clean organization (and a consistent place to find originals later). Then it routes the file based on type: PDFs get text extracted, DOCX files get converted and fetched as readable text, and TXT resumes are read directly. Once the resume text is normalized, the workflow adds your role requirements and passes both into a GPT-4o powered screening agent. The AI produces structured scoring and written justification, extracts candidate details like contact info and key qualifications, and finally appends a neat row into Google Sheets for your team to review.

The workflow starts with a Gmail trigger. From there, Google Drive handles storage and file conversion support, while GPT-4o does the screening and consistent scoring. Google Sheets becomes the single, shared dashboard where candidates land with the same format every time.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Monitors Gmail and detects resume attachments automatically.
Saves each resume to a Google Drive folder with consistent handling.
Extracts text from PDF, DOCX, and TXT without you converting files.
Runs GPT-4o screening and appends structured results to Google Sheets.

Most teams get about 4 hours back per week once volume picks up.
Scoring stays consistent with a standard 1–10 scale and justification.
Shortlists are faster because the top candidates are visible in one view.
Less back-and-forth, since hiring managers see strengths and risks immediately.
A cleaner audit trail because originals are stored in Drive and rows are logged in Sheets.

Example: What This Looks Like

Say you receive 25 resumes a week for one open role. Manually, if each one takes about 10 minutes to download, convert (sometimes), skim, and log into a spreadsheet, that’s roughly 4 hours. With this workflow, the “human time” becomes closer to 1 minute per candidate to review the scored row and decide next steps. The processing runs in the background, so you get most of those hours back without losing structure.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gmail to trigger on incoming resume emails
Google Drive for storing and accessing resume files
Google Sheets to log candidate scores and notes
OpenAI API key (get it from your OpenAI dashboard)

Skill level: Beginner. You will connect accounts, paste an API key, and edit the job description text.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Email trigger from Gmail. When a new resume email arrives (with an attachment), n8n picks it up automatically, so nobody has to “check the inbox” as a process.

File storage and format routing. The attachment is stored in Google Drive, then routed based on file type. PDFs get parsed for text, DOCX files go through conversion and text fetching, and TXT resumes are read directly.

Resume normalization and role context. The workflow cleans the extracted text into a consistent input and merges it with the role requirements you define (the “Define Role Details” part is where your job description lives).

AI screening and structured logging. GPT-4o evaluates the candidate, produces a structured score with reasoning, extracts key candidate details, then appends everything as a new row in Google Sheets for easy sorting and review.

You can easily modify the scoring criteria to match different roles, then map the outputs to new Google Sheets columns based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Incoming Email Trigger

Set up the email trigger to capture incoming resumes and download attachments for processing.

Add the Incoming Email Trigger node and set Simple to false.
In Options, enable Download Attachments to collect resume files.
Set Poll Times to everyMinute.
Credential Required: Connect your gmailOAuth2 credentials.

⚠️ Common Pitfall: If attachments aren’t downloaded, downstream nodes like Store in Drive won’t receive the file data.

Step 2: Connect Google Drive and Route by File Type

Store the resume file in Drive and route it based on the MIME type to the right parser path.

Configure Store in Drive with Name set to ={{ $json.subject.replace(/[^a-zA-Z0-9]/g, '_') }}_resume_{{ $now.format('yyyy-MM-dd_HH-mm') }} and Input Data Field Name set to attachment_0.
Credential Required: Connect your googleDriveOAuth2Api credentials to Store in Drive.
In File Type Router, add rules for PDF, DOCX, and TXT using Left Value ={{ $json.mimeType }} with right values of application/pdf, application/vnd.openxmlformats-officedocument.wordprocessingml.document, and text/plain.
Connect File Type Router outputs to Download Doc PDF, Convert DOCX File, and Grab TXT File respectively.
Credential Required: Connect your googleDriveOAuth2Api credentials to Download Doc PDF, Convert DOCX File, and Grab TXT File.

Tip: File Type Router uses strict MIME checks. Ensure attachments are not zipped or forwarded in a way that changes the MIME type.

Step 3: Extract and Normalize Resume Content

Parse the file content (PDF, DOCX, or TXT) and normalize it into a standard resume field.

In Download Doc PDF, keep Operation as download and ensure the file ID uses ={{ $json.id }} with Google file conversion to application/pdf.
Configure Parse PDF Content with Operation set to pdf and Max Pages set to 10.
In Convert DOCX File, set URL to =https://www.googleapis.com/drive/v2/files/{{ $json.id }}/copy and JSON Body to { "title": "{{ $json.name }}_converted", "mimeType": "application/vnd.google-apps.document" }.
In Fetch Doc Text, keep Operation as download and convert Google Docs to text/plain.
In Read TXT Content, set Operation to text and Destination Key to resumeText.
Configure Normalize Resume Fields with these assignments: candidateResume = ={{ $json.text || $json.data || $json.resumeText }}, originalEmail = ={{ $('Incoming Email Trigger').item.json }}, and driveLink = ={{ $('Store in Drive').item.json.webViewLink }}.

⚠️ Common Pitfall: If Normalize Resume Fields receives no text, check that the correct branch is connected from File Type Router and that the file conversion in Fetch Doc Text is set to text/plain.

Step 4: Set Up AI Screening and Candidate Extraction

Define role details, run the AI screening review, and extract candidate attributes.

In Define Role Details, set jobDescription to the provided multi-line role description.
Configure AI Screening Review with Text set to =**CANDIDATE RESUME:** {{ $('Parse PDF Content').item.json.text }} **JOB DESCRIPTION:** {{ $json.jobDescription }} and keep Has Output Parser enabled.
Connect OpenAI Chat Model as the language model for AI Screening Review and Extract Candidate Details.
Credential Required: Connect your openAiApi credentials to OpenAI Chat Model. The Structured Result Parser is a sub-node—credentials are added on OpenAI Chat Model, not the parser.
In Structured Result Parser, keep Schema Type as manual and use the provided JSON schema in Input Schema.
Set Extract Candidate Details Text to ={{ $('Normalize Resume Fields').item.json.candidateResume }} and keep the listed attributes (full_name, email_address, phone_number, current_title, years_experience, key_skills).

Tip: Update the OpenAI Chat Model settings (gpt-4o-mini, maxTokens: 2000, temperature: 0.3) only if you need different output length or creativity.

Step 5: Configure Output to Google Sheets

Append structured screening results and candidate details into your tracking sheet.

In Append Sheet Record, set Operation to append, select your Document ID, and choose Sheet Name Sheet1.
Map columns to values, such as Date = ={{ $('Store in Drive').item.json.createdTime }}, Email = ={{ $json.output.email_address }}, Strengths = ={{ $('AI Screening Review').item.json.output.candidate_strengths.join("\n\n") }}, and Overall Fit = ={{ $('AI Screening Review').item.json.output.overall_score }}.
Credential Required: Connect your googleSheetsOAuth2Api credentials.

⚠️ Common Pitfall: Ensure your Google Sheet headers match the column names in Append Sheet Record (e.g., Overall Fit, Risk Factor, Reward Factor).

Step 6: Test and Activate Your Workflow

Verify the workflow end-to-end, then activate it for production use.

Manually send an email with a resume attachment to the account monitored by Incoming Email Trigger.
Run the workflow and confirm that Store in Drive creates a file, and File Type Router sends it to the correct branch.
Verify that Normalize Resume Fields contains candidateResume and that AI Screening Review produces structured output parsed by Structured Result Parser.
Check Append Sheet Record to confirm a new row is appended with strengths, weaknesses, and overall score.
Once verified, switch the workflow to Active to process resumes automatically.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Gmail and Google Drive permissions can be picky. If the workflow suddenly stops seeing attachments, check the OAuth connection inside n8n’s Credentials and confirm the Gmail scope still has access.
If you’re converting DOCX files via HTTP Request, response speed can vary depending on the service and file size. When downstream nodes fail or return blank text, extend waits or add a retry so the next nodes don’t run on empty content.
The default AI prompt will feel generic fast. Bake in your job requirements and your “deal-breakers” early, otherwise you will end up re-reading and re-scoring candidates manually anyway.

Frequently Asked Questions

How long does it take to set up this Gmail Sheets resumes automation?

About 20 minutes if your accounts are ready.

Do I need coding skills to automate Gmail Sheets resumes screening?

No. You’ll connect your accounts and edit the job description and scoring prompt inside n8n.

Is n8n free to use for this Gmail Sheets resumes 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 OpenAI API costs (often a few cents per resume, depending on length).

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.

Can I customize this Gmail Sheets resumes workflow for multiple job roles?

Yes, and it’s one of the best reasons to use n8n here. Update the role requirements in the “Define Role Details” step, then tailor the scoring rubric in the AI Screening Review prompt for each position. Many teams also adjust what gets extracted in “Extract Candidate Details” so different roles capture different fields (portfolio links, certifications, tools, or location). If you want separate spreadsheets per role, you can switch the Google Sheets destination or add simple routing based on the email label.

Why is my Gmail connection failing in this workflow?

Usually it’s expired OAuth credentials or changed permissions. Reconnect Gmail inside n8n Credentials, then confirm the trigger is watching the correct mailbox and label/filter. Also check if your Google Workspace admin restricted third-party access, which can break previously working setups.

How many resumes can this Gmail Sheets resumes automation handle?

On n8n Cloud, your limit depends on plan executions per month, and self-hosting depends on your server. Practically, most small teams can process dozens to a few hundred resumes a week as long as you stay within OpenAI rate limits and keep file conversion reliable.

Is this Gmail Sheets resumes automation better than using Zapier or Make?

Often, yes. n8n handles branching logic (PDF vs DOCX vs TXT), structured parsing, and richer AI chains in one place, which means fewer fragile “glue” steps. Self-hosting is also a big deal if your resume volume spikes, because you’re not paying per tiny task. Zapier or Make can be fine for simple “email to sheet” capture, but AI screening plus file handling tends to get messy fast. If you want, Talk to an automation expert and we’ll map the cleanest route for your setup.

Once this is running, your spreadsheet becomes the hiring inbox. You review candidates, not attachments, and you get your week back in the process.

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.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": "",
"name": "Automated Resume Screening Pipeline",
"meta": {
"instanceId": "d5cd1409bc4e5261c93cc27c260ff57b8556e371b751d803bb714db3eebb1eeb",
"templateId": null,
"templateCredsSetupCompleted": null
},
"nodes": [
{
"id": "flowpast-topbar-9046",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1280,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "8e49be48-133a-485e-b983-165567da97ed",
"name": "Incoming Email Trigger",
"type": "n8n-nodes-base.gmailTrigger",
"position": [
0,
165
],
"parameters": {
"simple": false,
"filters": [],
"options": {
"downloadAttachments": true
},
"pollTimes": {
"item": [
{
"mode": "everyMinute"
}
]
}
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "d85372c3-dc71-4a37-86a1-aeebdec0a0e3",
"name": "Store in Drive",
"type": "n8n-nodes-base.googleDrive",
"position": [
250,
230
],
"parameters": {
"name": "={{ $json.subject.replace(/[^a-zA-Z0-9]/g, '_') }}_resume_{{ $now.format('yyyy-MM-dd_HH-mm') }}",
"driveId": {
"__rl": true,
"mode": "list",
"value": "My Drive"
},
"options": [],
"folderId": {
"__rl": true,
"mode": "list",
"value": "root",
"cachedResultName": "/ (Root folder)"
},
"inputDataFieldName": "attachment_0"
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 3
},
{
"id": "2194e79e-a17b-417e-9ca3-7a9a43ab231a",
"name": "File Type Router",
"type": "n8n-nodes-base.switch",
"position": [
475,
170
],
"parameters": {
"rules": {
"values": [
{
"outputKey": "PDF",
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "pdf-check",
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $json.mimeType }}",
"rightValue": "application/pdf"
}
]
},
"renameOutput": true
},
{
"outputKey": "DOCX",
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "docx-check",
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $json.mimeType }}",
"rightValue": "application/vnd.openxmlformats-officedocument.wordprocessingml.document"
}
]
},
"renameOutput": true
},
{
"outputKey": "TXT",
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "txt-check",
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $json.mimeType }}",
"rightValue": "text/plain"
}
]
},
"renameOutput": true
}
]
},
"options": []
},
"typeVersion": 3.2
},
{
"id": "2378eb54-7a38-402f-b4b9-1ea0eeae4959",
"name": "Download Doc PDF",
"type": "n8n-nodes-base.googleDrive",
"position": [
755,
160
],
"parameters": {
"fileId": {
"__rl": true,
"mode": "id",
"value": "={{ $json.id }}"
},
"options": {
"googleFileConversion": {
"conversion": {
"docsToFormat": "application/pdf"
}
}
},
"operation": "download"
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 3
},
{
"id": "0c9bb794-48bb-48cd-b672-88eda9aa4106",
"name": "Parse PDF Content",
"type": "n8n-nodes-base.extractFromFile",
"position": [
1055,
120
],
"parameters": {
"options": {
"maxPages": 10
},
"operation": "pdf"
},
"typeVersion": 1
},
{
"id": "90aa13cb-dfcb-41c1-a7b7-598970122bca",
"name": "Convert DOCX File",
"type": "n8n-nodes-base.httpRequest",
"position": [
770,
350
],
"parameters": {
"url": "=https://www.googleapis.com/drive/v2/files/{{ $json.id }}/copy",
"method": "POST",
"options": [],
"jsonBody": "{\n  \"title\": \"{{ $json.name }}_converted\",\n  \"mimeType\": \"application/vnd.google-apps.document\"\n}",
"sendBody": true,
"specifyBody": "json",
"authentication": "predefinedCredentialType",
"nodeCredentialType": "googleDriveOAuth2Api"
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.2
},
{
"id": "c9828dee-ca5b-4945-8768-35c739843724",
"name": "Fetch Doc Text",
"type": "n8n-nodes-base.googleDrive",
"position": [
1040,
345
],
"parameters": {
"fileId": {
"__rl": true,
"mode": "id",
"value": "={{ $json.id }}"
},
"options": {
"googleFileConversion": {
"conversion": {
"docsToFormat": "text/plain"
}
}
},
"operation": "download"
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 3
},
{
"id": "a4dbee46-03d7-4c8d-8cc4-1935cb28d65a",
"name": "Grab TXT File",
"type": "n8n-nodes-base.googleDrive",
"position": [
745,
470
],
"parameters": {
"fileId": {
"__rl": true,
"mode": "id",
"value": "={{ $json.id }}"
},
"options": [],
"operation": "download"
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 3
},
{
"id": "2bb86d12-445b-48cf-93b2-1a29b8508054",
"name": "Read TXT Content",
"type": "n8n-nodes-base.extractFromFile",
"position": [
1030,
530
],
"parameters": {
"options": [],
"operation": "text",
"destinationKey": "resumeText"
},
"typeVersion": 1
},
{
"id": "6c783f5c-271e-4bf7-ab5e-97655267ae27",
"name": "Normalize Resume Fields",
"type": "n8n-nodes-base.set",
"position": [
1180,
295
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "resume-text",
"name": "candidateResume",
"type": "string",
"value": "={{ $json.text || $json.data || $json.resumeText }}"
},
{
"id": "original-email",
"name": "originalEmail",
"type": "object",
"value": "={{ $('Incoming Email Trigger').item.json }}"
},
{
"id": "drive-link",
"name": "driveLink",
"type": "string",
"value": "={{ $('Store in Drive').item.json.webViewLink }}"
}
]
}
},
"typeVersion": 3.4
},
{
"id": "0c0cb748-f4ec-4d5c-a564-ffccaf9a9edd",
"name": "Define Role Details",
"type": "n8n-nodes-base.set",
"position": [
930,
660
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "job-description",
"name": "jobDescription",
"type": "string",
"value": "Job Title: Senior Software Engineer\n\nWe are seeking a Senior Software Engineer to join our growing team. The ideal candidate will have:\n\nRequired Skills:\n- 5+ years of software development experience\n- Strong proficiency in JavaScript, Python, or Java\n- Experience with cloud platforms (AWS, GCP, Azure)\n- Database design and optimization experience\n- Agile development methodology experience\n\nPreferred Skills:\n- Full-stack development experience\n- DevOps and CI/CD pipeline experience\n- Team leadership experience\n- Experience with microservices architecture\n\nResponsibilities:\n- Design and develop scalable software solutions\n- Collaborate with cross-functional teams\n- Mentor junior developers\n- Participate in code reviews\n- Contribute to technical decision making"
}
]
}
},
"typeVersion": 3.4
},
{
"id": "c779750a-750e-44f6-9e22-d5a09a0f533e",
"name": "AI Screening Review",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
605,
725
],
"parameters": {
"text": "=**CANDIDATE RESUME:**\n\n{{ $('Parse PDF Content').item.json.text }}\n\n**JOB DESCRIPTION:**\n\n{{ $json.jobDescription }}",
"options": {
"systemMessage": "You are an expert technical recruiter and hiring manager with 15+ years of experience evaluating candidates across technology, business, and creative roles.\n\n# Your Mission\nAnalyze the candidate's resume against the provided job description and deliver a comprehensive, actionable screening report that helps hiring teams make informed decisions quickly.\n\n# Analysis Framework\nEvaluate the candidate across these dimensions:\n1. **Technical Skills Match** - Hard skills, tools, technologies\n2. **Experience Relevance** - Industry background, role progression\n3. **Cultural & Soft Skills Fit** - Leadership, communication, teamwork\n4. **Growth Potential** - Learning ability, adaptability, ambition\n5. **Red Flags** - Gaps, inconsistencies, concerns\n\n# Output Requirements\nProvide your analysis in this exact JSON structure - be specific and reference actual resume content.\n\n# Quality Standards\n- Reference specific resume content, not generalities\n- Consider both immediate needs and long-term potential\n- Balance optimism with realistic assessment\n- Provide actionable insights for hiring managers\n- Score from 1-10 where 8+ means \"definitely interview\""
},
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 2
},
{
"id": "0bf3800f-5f64-4ee7-abbf-0ea8fa27c273",
"name": "OpenAI Chat Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
525,
490
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4o-mini",
"cachedResultName": "gpt-4o-mini"
},
"options": {
"maxTokens": 2000,
"temperature": 0.3
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "7c14222a-0874-42a8-8044-fca5d58af083",
"name": "Structured Result Parser",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
700,
510
],
"parameters": {
"schemaType": "manual",
"inputSchema": "{\n  \"type\": \"object\",\n  \"properties\": {\n    \"candidate_strengths\": {\n      \"type\": \"array\",\n      \"items\": { \"type\": \"string\" },\n      \"description\": \"List of candidate's key strengths with evidence\"\n    },\n    \"candidate_weaknesses\": {\n      \"type\": \"array\", \n      \"items\": { \"type\": \"string\" },\n      \"description\": \"List of areas where candidate falls short\"\n    },\n    \"risk_assessment\": {\n      \"type\": \"object\",\n      \"properties\": {\n        \"level\": {\n          \"type\": \"string\",\n          \"enum\": [\"Low\", \"Medium\", \"High\"]\n        },\n        \"explanation\": {\n          \"type\": \"string\",\n          \"description\": \"Detailed risk analysis\"\n        }\n      }\n    },\n    \"opportunity_assessment\": {\n      \"type\": \"object\",\n      \"properties\": {\n        \"level\": {\n          \"type\": \"string\", \n          \"enum\": [\"Low\", \"Medium\", \"High\"]\n        },\n        \"explanation\": {\n          \"type\": \"string\",\n          \"description\": \"Upside potential analysis\"\n        }\n      }\n    },\n    \"overall_score\": {\n      \"type\": \"integer\",\n      \"minimum\": 1,\n      \"maximum\": 10,\n      \"description\": \"Overall fit score 1-10\"\n    },\n    \"score_justification\": {\n      \"type\": \"string\",\n      \"description\": \"Detailed explanation of the score\"\n    },\n    \"next_steps_recommendation\": {\n      \"type\": \"string\",\n      \"description\": \"Recommended next actions\"\n    }\n  },\n  \"required\": [\"candidate_strengths\", \"candidate_weaknesses\", \"risk_assessment\", \"opportunity_assessment\", \"overall_score\", \"score_justification\", \"next_steps_recommendation\"]\n}"
},
"typeVersion": 1.3
},
{
"id": "a8b68718-7fcc-49de-b9de-9f22fd821dab",
"name": "Extract Candidate Details",
"type": "@n8n/n8n-nodes-langchain.informationExtractor",
"position": [
400,
710
],
"parameters": {
"text": "={{ $('Normalize Resume Fields').item.json.candidateResume }}",
"options": [],
"attributes": {
"attributes": [
{
"name": "full_name",
"required": true,
"description": "Candidate's full name (first and last name combined)"
},
{
"name": "email_address",
"required": true,
"description": "Primary email address of the candidate"
},
{
"name": "phone_number",
"description": "Phone number or mobile number"
},
{
"name": "current_title",
"description": "Current job title or most recent position"
},
{
"name": "years_experience",
"description": "Total years of relevant work experience"
},
{
"name": "key_skills",
"description": "Top 5 technical or professional skills mentioned"
}
]
}
},
"typeVersion": 1.2
},
{
"id": "cfe547a4-821d-4df3-84f9-d374fd75928f",
"name": "Append Sheet Record",
"type": "n8n-nodes-base.googleSheets",
"position": [
110,
665
],
"parameters": {
"columns": {
"value": {
"Date": "={{ $('Store in Drive').item.json.createdTime }}",
"Email": "={{ $json.output.email_address }}",
"Resume": "={{ $('Store in Drive').item.json.webViewLink }}",
"Full Name": "={{ $json.output.full_name }}",
"Strengths": "={{ $('AI Screening Review').item.json.output.candidate_strengths.join(\"\\n\\n\")  }}",
"Key Skills": "={{ $json.output.key_skills }}",
"Weaknesses": "={{ $('AI Screening Review').item.json.output.candidate_weaknesses.join(\"\\n\\n\") }}",
"Overall Fit": "={{ $('AI Screening Review').item.json.output.overall_score }}",
"Risk Factor": "={{ $('AI Screening Review').item.json.output.risk_assessment.level }}\n{{ $('AI Screening Review').item.json.output.risk_assessment.explanation }}",
"Justification": "={{ $('AI Screening Review').item.json.output.score_justification }}",
"Reward Factor": "={{ $('AI Screening Review').item.json.output.opportunity_assessment.level }} \n\n{{ $('AI Screening Review').item.json.output.opportunity_assessment.explanation }}"
},
"schema": [
{
"id": "Date",
"type": "string",
"display": true,
"required": false,
"displayName": "Date",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Resume",
"type": "string",
"display": true,
"required": false,
"displayName": "Resume",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Full Name",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "Full Name",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Email",
"type": "string",
"display": true,
"required": false,
"displayName": "Email",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Strengths",
"type": "string",
"display": true,
"required": false,
"displayName": "Strengths",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Weaknesses",
"type": "string",
"display": true,
"required": false,
"displayName": "Weaknesses",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Risk Factor",
"type": "string",
"display": true,
"required": false,
"displayName": "Risk Factor",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Reward Factor",
"type": "string",
"display": true,
"required": false,
"displayName": "Reward Factor",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Overall Fit",
"type": "string",
"display": true,
"required": false,
"displayName": "Overall Fit",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Justification",
"type": "string",
"display": true,
"required": false,
"displayName": "Justification",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Key Skills",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "Key Skills",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "append",
"sheetName": {
"__rl": true,
"mode": "list",
"value": "gid=0",
"cachedResultUrl": "",
"cachedResultName": "Sheet1"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "",
"cachedResultName": "Candidate Tracker"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.7
}
],
"pinData": [],
"connections": {
"Download Doc PDF": {
"main": [
[
{
"node": "Parse PDF Content",
"type": "main",
"index": 0
}
]
]
},
"Grab TXT File": {
"main": [
[
{
"node": "Read TXT Content",
"type": "main",
"index": 0
}
]
]
},
"OpenAI Chat Model": {
"ai_languageModel": [
[
{
"node": "AI Screening Review",
"type": "ai_languageModel",
"index": 0
},
{
"node": "Extract Candidate Details",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Store in Drive": {
"main": [
[
{
"node": "File Type Router",
"type": "main",
"index": 0
}
]
]
},
"Incoming Email Trigger": {
"main": [
[
{
"node": "Store in Drive",
"type": "main",
"index": 0
}
]
]
},
"Fetch Doc Text": {
"main": [
[
{
"node": "Normalize Resume Fields",
"type": "main",
"index": 0
}
]
]
},
"Define Role Details": {
"main": [
[
{
"node": "AI Screening Review",
"type": "main",
"index": 0
}
]
]
},
"Parse PDF Content": {
"main": [
[
{
"node": "Normalize Resume Fields",
"type": "main",
"index": 0
}
]
]
},
"File Type Router": {
"main": [
[
{
"node": "Download Doc PDF",
"type": "main",
"index": 0
}
],
[
{
"node": "Convert DOCX File",
"type": "main",
"index": 0
}
],
[
{
"node": "Grab TXT File",
"type": "main",
"index": 0
}
]
]
},
"Read TXT Content": {
"main": [
[
{
"node": "Normalize Resume Fields",
"type": "main",
"index": 0
}
]
]
},
"Convert DOCX File": {
"main": [
[
{
"node": "Fetch Doc Text",
"type": "main",
"index": 0
}
]
]
},
"AI Screening Review": {
"main": [
[
{
"node": "Extract Candidate Details",
"type": "main",
"index": 0
}
]
]
},
"Extract Candidate Details": {
"main": [
[
{
"node": "Append Sheet Record",
"type": "main",
"index": 0
}
]
]
},
"Normalize Resume Fields": {
"main": [
[
{
"node": "Define Role Details",
"type": "main",
"index": 0
}
]
]
},
"Structured Result Parser": {
"ai_outputParser": [
[
{
"node": "AI Screening Review",
"type": "ai_outputParser",
"index": 0
}
]
]
}
},
"versionId": ""
}