Resume Screening & Behavioral Interviews with Gemini, Elevenlabs, & Notion ATS copy — AI Product | Success.
Resume Screening & Behavioral Interviews with Gemini, Elevenlabs, & Notion ATS copy Resume Screening & Behavioral Interviews with Gemini, Elevenlabs, & Notion ATS copy — free, ready-to-import n8n workflow (67 nodes, Google Sheets Drive).
AI Product Reusable license
from $0
Understand this workflow before you use it.
Structure unavailable 1 to review Health 86/100 Workflow structure could not be fully reconstructed from the source file The source file lists the steps but not how they connect. Steps, integrations and security checks are analyzed; execution order and structure-based checks are not. This is a limitation of the file, not necessarily a problem with the workflow.
This workflow starts from Webhook, Form Trigger, Form Trigger and Form Trigger and works with documents, files, form submissions and spreadsheets.
Sale models Live demo Payments run through a deterministic mock provider in this environment — no real money moves.
**Resume Screening & Behavioral Interviews with Gemini, Elevenlabs, & Notion ATS copy**
Category: Google Sheets Drive · 67 nodes
Nodes/integrations used: extractFromFile, filter, formTrigger, googleDrive, googleSheets, httpRequest, notion, notionTool
How to use: download the JSON below, then in n8n choose Import from File (or open the demo link, copy the JSON, and paste with Ctrl+V into the n8n canvas). Add your own credentials and activate.
Source: Zie619/n8n-workflows (MIT). Credentials were removed and files modified for redistribution — see the library's ATTRIBUTION_AND_LICENSES.md for full license text.
Resume Screening & Behavioral Interviews with Gemini, Elevenlabs, & Notion ATS copy
from $0
Sign in to buy
Steps 33
Integrations 3
Connections Unavailable
Complexity Advanced
Technical health 86/100
Security 1 to review Google Drive Google Sheets Notion Workflow structure Steps and detected references (no diagram) Execution order can't be reliably reconstructed from this file, so no diagram is shown. Here is what the workflow contains.
15 × Logic 8 × App 3 × Trigger 2 × Storage 1 × AI component 1 × File 1 × Flow control 1 × HTTP 1 × Webhook Merge · Merge Structured Output Parser · No-Op HR Expert · No-Op Upload CV · Google Drive Extract Resume · Extract From File Applicant Summary · No-Op Job Description Summary · No-Op Applicant Qualifications · No-Op Applicant Personal Data · No-Op Application Data · Set ElevenLabs Web Hook · Webhook ai_convo_items · Set Detected references These steps name another step whose data they read. That shows a data dependency, not the order the steps run in.
HR Expert reads data from Applicant Summary Filter_Notion_db reads data from ai_convo_items Link Audio in Notion reads data from Applicant Record Get Job Description reads data from Application Data Applicant Data Backup reads data from Merge Applicant Data Backup reads data from Application Data Applicant Data Backup reads data from Get Job Description Create Applicant Record reads data from Application Data Create Applicant Record reads data from Merge Create Applicant Record reads data from HR Expert Create Applicant Record reads data from Applicant Personal Data Create Applicant Record reads data from Applicant Qualifications Create Applicant Record reads data from Security 1 note(s) to review 0 Critical0 High1 Medium0 Low0 InfoMedium Webhook accepts unauthenticated requests
Anyone who learns the webhook URL can trigger this workflow with arbitrary data.
Confidence: medium · Heuristic
Suggested fix: Enable header or basic auth on the Webhook node, or verify a signature from the sending service.
Health How the technical score is made up Overall 86/100 .
Technical hygiene signals detected statically from the workflow file. Not a guarantee of correctness or fitness for a particular use.
Execution profile What one run touches Starts from: Webhook, Form Trigger, Form Trigger, Form Trigger
HTTP requests 1
File storage operations 2 Loops and branching can't be measured without the workflow's connections.
Documentation Generated from the workflow's structure What it does This workflow starts from Webhook, Form Trigger, Form Trigger and Form Trigger and works with documents, files, form submissions and spreadsheets.
Services involved: Google Drive, Google Sheets and Notion.
This description is generated from the workflow's node types and wiring. It does not interpret each node's configuration.
Inputs Data enters through the trigger(s) below.
Some steps read fields from the incoming request body, query or headers.
ElevenLabs Web Hook (Webhook) Application Form 1 of 3 (Form Trigger) Application Form 2 of 3 (Form Trigger) Application form 3 of 3 (Form Trigger) Main flow This file does not contain its real connections, so the execution order cannot be documented.
It contains: 15 × logic, 8 × productivity, 3 × trigger, 2 × storage, 1 × ai subnode, 1 × file, 1 × flow, 1 × http, 1 × webhook.
Some steps name another step whose data they read. This shows data dependencies only, not the order steps run in:
HR Expert (No-Op) reads data from Applicant Summary (No-Op) Filter_Notion_db (Filter) reads data from ai_convo_items (Set) Link Audio in Notion (Notion) reads data from Applicant Record (Notion) Get Job Description (Notion) reads data from Application Data (Set) Applicant Data Backup (Google Sheets) reads data from Merge Applicant Data Backup (Google Sheets) reads data from Application Data (Set) Applicant Data Backup (Google Sheets) reads data from Get Job Description (Notion) Create Applicant Record (Notion) reads data from Application Data (Set) Create Applicant Record (Notion) reads data from Merge Create Applicant Record (Notion) reads data from HR Expert (No-Op) Outputs Without connection data, final outputs can't be identified precisely. These nodes write to external services:
Upload CV (Google Drive) Link Audio in Notion (Notion) Get Applicant Record (Notion) Embed Resume in Notion (Notion) Get Job Description (Notion) Applicant Data Backup (Google Sheets) Create Applicant Record (Notion) Upload Audio to Drive (Google Drive) Applicant Record (Notion) Update_Applicant_Record (Notion) Requirements No credentials are attached in this file. You will need your own n8n credentials for each service below.
Google Drive Notion Google Sheets Setup Import the JSON file into n8n (Workflows → Import from File). Create credentials for each service and select them on the matching nodes. Set environment variable(s): BASE_URL, WEBHOOK_URL. Reconnect the nodes in the n8n editor: this file's original connections are missing. Run it once manually with test data before activating. Important considerations No node is configured to retry or continue on failure.
There is no Error Trigger in this workflow.
No error handling around external calls Generated automatically from the workflow's structure. Verify behaviour in n8n before relying on it.
Optimization ideas Advisory suggestions Potential optimization · high confidence
No-op placeholder nodes
9 "No Operation" nodes do nothing at runtime.
Possible impact: Cleaner graph; no runtime change.
No-op nodes are sometimes kept deliberately as visual end markers.
Automated static analysis (engine 1.1.0). Nothing was executed. Not a guarantee of correctness or safety.
The seller has not attached downloadable files yet.
Uploaded by the seller and security-scanned before any buyer can download them.
Documentation
LeadBot 24h — WhatsApp AI Lead Qualification Bot — free, ready-to-import n8n workflow (6 nodes, WhatsApp).
AI Product Reusable
Extract_Audio
· HTTP Request
Filter_Notion_db · Filter
AI Agent · No-Op
Link Audio in Notion · Notion
Resume URL · Set
Get Applicant Record · Notion
Embed Resume in Notion · Notion
Wait · Wait
Application Form 1 of 3 · Form Trigger
Application Form 2 of 3 · Form Trigger
Application form 3 of 3 · Form Trigger
Get Job Description · Notion
Job Description Mapping · Set
Applicant Data Backup · Google Sheets
Create Applicant Record · Notion
Upload Audio to Drive · Google Drive
Google Gemini · No-Op
Evaluation Criteria · Notion Tool
Applicant Record · Notion
Update_Applicant_Record · Notion
Google Gemini Model · No-Op Applicant Summary
Create Applicant Record reads data from Get Job Description
Update_Applicant_Record reads data from ai_convo_items Be the first to review this product.
