HumationHuman + Automation
Back to Catalog

Generate tailored interview questions with GPT-4 based on CV, JD, and round

Trung TranTrung Tran
1007 views
2/3/2026
AIOpenAIAutomationEmailSupabase
Official Page

🤖 Smart Interview Assistant: Tailored Questions Based on CV, JD, and Round

Watch the demo video below:

Watch the video

📌 Who’s it for

This workflow is designed for:

  • Recruiters and Talent Acquisition Specialists who want to automate candidate interview prep.
  • Hiring Managers conducting multiple interviews and needing personalized question sets.
  • Technical Interviewers who want to save time and be well-prepared with relevant questions.

⚙️ How it works / What it does

The Smart Interview Assistant automates the interview preparation process in a few clicks:

  1. Accepts:
    • Multiple resumes (PDFs)
    • Selected job role
    • Chosen interview round
  2. Extracts structured data from:
    • The candidate’s CV
    • The corresponding Job Description (JD)
  3. Uses GPT-4 to analyze:
    • Candidate profile
    • Role requirements
    • Interview round context
  4. Generates:
    • Tailored interview questions
    • Expected answers
    • A summarized interview prep report
  5. Sends the report directly to the hiring team via email (SMTP)

📁 Google Drive Structure

📂 Root Folder
├── 📁 jd/                          # Stores all job descriptions in PDF format
│   ├── Backend_Engineer.pdf
│   ├── Azure_DevOps_Lead.pdf
│   └── ...
└── 📄 Positions (Google Sheet)    # Maps Job Role ↔ JD File Link

📝 Sample Mapping Sheet:
Positions Sheet

Columns:

  • Job Role
  • Job Description File URL (pointing to PDF in jd/ folder)

🛠️ How to Set Up

Step 1: Configure API Integrations

  • ✅ Connect your OpenAI GPT-4 API Key
  • ✅ Enable Google Cloud APIs:
    • Google Sheets API (to read job roles)
    • Google Drive API (to access CV and JD files)
  • ✅ Set up SMTP credentials (for email delivery)

Step 2: Prepare Google Drive & Mapping Sheet

  1. Create a root folder on Google Drive
  2. Inside the root folder:
    • Create a folder named /jd/ and upload all job descriptions (PDFs)
  3. Create a Google Sheet named Positions with the following format:
| Job Role                     | Job Description File URL                   |
|-----------------------------|--------------------------------------------|
| Azure DevOps Engineer        | https://drive.google.com/xxx/jd1.pdf       |
| Full-Stack Developer (.NET)  | https://drive.google.com/xxx/jd2.pdf       |

Step 3: Build the Application Form

Use any form tool (e.g., Typeform, Tally, or custom HTML) that collects:

  • 📎 Resume file (PDF)
  • 🧾 Job Role (dropdown)
  • 🔄 Interview Round (dropdown)

Step 4: Resume & JD Extraction

  • 🔍 Use Extract from PDF to parse the resume content
  • 📄 Retrieve the JD link from the Positions sheet based on the selected Job Role
  • 🔗 Use Download file to pull the PDF for processing

Step 5: Analyze with GPT-4

  • Run both Resume and JD through a Profile Analyzer Agent (GPT-4 with JSON output)
  • Merge results
  • Add manual input or mapping for the Interview Round metadata

Step 6: Generate Interview Report

  • Use a second GPT-4 agent (e.g., HR Expert Agent) to:
    • Generate 6–8 tailored interview questions
    • Include expected answers and rationale

Step 7: Deliver Final Report

  • Format the content as:
    • 📄 PDF (optional)
    • 📨 Email body
  • Send the report to the recruiter, hiring manager, or interviewer via SMTP

✅ Requirements

  • 🔑 OpenAI GPT-4 API Key
  • 📁 Google Drive (for resume and JD storage)
  • 📊 Google Sheet (job role mapping)
  • 📬 SMTP credentials (host, username, password)
  • 🧰 n8n self-hosted or cloud instance with:
    • PDF Parser
    • Google Sheets node
    • HTTP Download node
    • Email node

✏️ How to Customize the Workflow

| Part | Customization Options | |----------------------------|-------------------------------------------------------------| | Form UI | Modify the design, dropdown options, or input validations | | Job Description Source | Replace Google Sheet with Notion, Airtable, or database | | Interview Metadata | Add job level, region, or language preference | | AI Prompt Tuning | Adjust prompt phrasing or temperature in GPT nodes | | Report Format | Generate PDF instead of email body using PDF node | | Delivery Method | Add internal HR portal webhook or generate downloadable link |

Generate Tailored Interview Questions with GPT-4 based on CV, JD, and Round

This n8n workflow automates the creation of highly personalized interview questions using GPT-4. It takes a candidate's CV, a job description (JD), and the interview round as input, then generates relevant questions, stores them in Google Sheets, and sends them via email.

What it does

This workflow streamlines the interview preparation process by:

  1. Triggering from a form submission: Initiates when a new entry is submitted via an n8n form, providing the CV, JD, and interview round details.
  2. Extracting text from files: Reads the content of the provided CV and JD files (presumably PDF or similar document types) to extract their textual information.
  3. Preparing input for AI Agent: Combines the extracted text from the CV and JD, along with the specified interview round, into a structured prompt suitable for an AI agent.
  4. Generating interview questions with GPT-4: Utilizes an AI Agent (likely powered by GPT-4 via OpenAI) to generate tailored interview questions based on the combined input. It uses a structured output parser to ensure the questions are in a usable format.
  5. Storing questions in Google Sheets: Appends the generated interview questions and associated candidate/job details to a specified Google Sheet for record-keeping and easy access.
  6. Sending questions via email: Composes and sends an email containing the generated interview questions to a designated recipient.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: Configured as an n8n credential for the "OpenAI Chat Model" node. This is essential for the AI Agent to function.
  • Google Sheets Account: Configured as an n8n credential for the "Google Sheets" node, with access to the target spreadsheet.
  • Google Drive Account: Configured as an n8n credential for the "Google Drive" node, with read access to the CV and JD files.
  • SMTP/Email Service: Configured as an n8n credential for the "Send Email" node to send out the generated questions.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI API key credential.
    • Set up your Google Sheets credential.
    • Set up your Google Drive credential.
    • Set up your SMTP/Email credential.
  3. Configure the "On form submission" Trigger:
    • Activate the trigger node.
    • Note the webhook URL for your form. You will use this URL to submit data to the workflow.
    • Ensure the form fields match the expected inputs for CV (file), JD (file), and interview round (text).
  4. Configure "Google Drive" Nodes:
    • Specify how the CV and JD files are accessed from Google Drive (e.g., by ID or path, based on how the form provides the file information).
  5. Configure "Extract from File" Nodes:
    • Ensure these nodes are correctly configured to extract text from the binary data received from Google Drive.
  6. Configure "Edit Fields" (Set) Node:
    • Review and adjust the fields being set to ensure all necessary data (CV content, JD content, interview round) is correctly passed to the AI Agent.
  7. Configure "OpenAI Chat Model" and "AI Agent" Nodes:
    • Verify that your OpenAI credential is selected.
    • Review the prompt used in the "Basic LLM Chain" to ensure it aligns with your desired question generation style.
    • Check the "Structured Output Parser" to confirm the expected JSON structure for the generated questions.
  8. Configure "Google Sheets" Node:
    • Specify the Spreadsheet ID and Sheet Name where the interview questions should be stored.
    • Map the data fields from the AI output to the columns in your Google Sheet.
  9. Configure "Send Email" Node:
    • Set the recipient email address, subject, and body of the email. Use expressions to dynamically include the generated interview questions and other relevant details.
  10. Activate the Workflow: Once all configurations are complete, activate the workflow.

Now, whenever a form is submitted with the required CV, JD, and interview round information, the workflow will automatically generate and deliver tailored interview questions.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

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