Automate CV screening & candidate validation with AI & email parsing
This workflow contains community nodes that are only compatible with the self-hosted version of n8n.
This automated n8n workflow streamlines the process of screening CVs and validating candidate information using AI and email parsing. The system listens for new emails with CV attachments, extracts and processes the data, and either saves valid CVs to a target directory or notifies HR of invalid submissions.
Good to Know
- The workflow improves efficiency by automating CV screening and validation.
- Ensures only CVs with essential fields (e.g., name, email, skills) are processed further.
- Email notifications alert HR to incomplete or invalid CVs for timely follow-up.
- The system pauses until all CV data is fully loaded to avoid processing errors.
How It Works
- Trigger on New CV Email - Detects new emails with CV attachments.
- Extract Text from PDF CV - Parses content from attached PDF files.
- Ensure All CV Data Loaded - Waits until all data is ready for processing.
- Parse & Structure CV Information - Extracts structured details like name, skills, and experience using AI or custom logic.
- Check CV for Required Fields - Verifies the presence of essential fields (e.g., name, email, skills).
- Save Valid CV to Folder - Stores successfully validated CVs into a target directory.
- Notify HR of Invalid CV - Sends an email alert for incomplete or invalid CVs.
Data Sources
The workflow processes data from email attachments:
- CV PDF Files - Contains candidate information in PDF format.
How to Use
- Import the workflow into n8n.
- Configure email account credentials for monitoring new CV emails.
- Set up a target directory for storing validated CVs.
- Test with sample CV PDFs to verify extraction and validation.
- Adjust AI or custom logic based on specific required fields.
- Monitor email notifications for invalid CVs and refine the process as needed.
Requirements
- Email account access with IMAP/POP3 support.
- PDF parsing capabilities (e.g., OCR or text extraction tools).
- AI or custom logic for data extraction and validation.
- A target directory for storing validated CVs.
Customizing This Workflow
- Modify the "Check CV for Required Fields" node to include additional required fields (e.g., education, certifications).
- Adjust the email notification format to include more details about invalid CVs.
- Integrate with HR software for seamless candidate tracking.
Details
- The workflow ensures efficient CV screening by automating repetitive tasks.
- Notifications help maintain a high-quality candidate pool by addressing issues early.
n8n Automated Email Processing and Command Execution
This n8n workflow automates the processing of incoming emails, extracts content from attachments, executes a command based on the email, and sends a follow-up email. It's designed to create a loop where email interactions can trigger system actions and provide feedback.
What it does
This workflow streamlines a process that involves email communication, file extraction, conditional logic, command execution, and email responses. Here's a step-by-step breakdown:
- Monitors Incoming Emails: The workflow starts by continuously checking an IMAP inbox for new emails.
- Extracts Content from Attachments: If an email contains a file attachment, it attempts to extract content from that file. This could be useful for processing resumes, reports, or other documents.
- Executes a Command: It then executes a shell command on the n8n server. The specific command is determined by the workflow's logic, likely based on the extracted email content or attachment data.
- Waits for a Duration: After executing the command, the workflow pauses for a specified amount of time. This could be to allow the command to complete, or to introduce a delay before the next step.
- Applies Conditional Logic: An "If" node evaluates a condition, likely based on the outcome of the command execution or the extracted email data.
- Sends Follow-up Email:
- If the condition is TRUE: It sends an email, potentially confirming the action, providing results, or requesting further information.
- If the condition is FALSE: It also sends an email, likely indicating that the condition was not met or that an alternative path was taken.
- Processes Data with Code: A "Code" node allows for custom JavaScript logic to further process data at some point in the workflow, offering flexibility for complex transformations or decision-making.
Prerequisites/Requirements
To use this workflow, you will need:
- IMAP Email Account: Access to an IMAP email server for the "Email Trigger (IMAP)" node to monitor incoming emails. You'll need the host, port, username, and password.
- SMTP Email Account: Access to an SMTP server for the "Send Email" node to send outgoing emails. You'll need the host, port, username, and password.
- n8n Instance with
Execute CommandAccess: The "Execute Command" node runs commands directly on the server where n8n is hosted. Ensure your n8n instance has the necessary permissions and environment to run the desired commands. - Understanding of JavaScript (Optional but Recommended): For customizing the "Code" node's logic.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- Email Trigger (IMAP): Click on the "Email Trigger (IMAP)" node. Configure your IMAP credentials (Host, Port, User, Password) to connect to the inbox you want to monitor.
- Send Email (SMTP): Click on the "Send Email" node. Configure your SMTP credentials (Host, Port, User, Password) to connect to the email server you'll use for sending responses.
- Customize Nodes:
- Email Trigger (IMAP): Adjust the "Folder" and "Check Interval" settings as needed.
- Extract from File: Configure this node based on the expected file types and content you anticipate in email attachments.
- Execute Command: Crucially, configure the specific command you want to run. Be mindful of security implications when running commands on your server.
- Wait: Adjust the "Delay" duration as required.
- If: Define the conditions for the "If" node based on your specific logic (e.g., check for keywords in the email body, results of the executed command, or extracted file content).
- Send Email: Customize the recipient, subject, and body of the emails sent on both the TRUE and FALSE branches of the "If" node.
- Code: Modify the JavaScript code within this node to perform any custom data manipulation or logic.
- Activate the Workflow: Once all configurations are complete, save the workflow and activate it by toggling the "Active" switch in the top right corner.
The workflow will now automatically process emails according to your defined logic.
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.
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte