Back to Catalog

Optimize Resumes & Generate Cover Letters with Gemini AI and PDF.co

Paul AbrahamPaul Abraham
50 views
2/3/2026
Official Page

ATS-Optimized Resume and Cover Letter Generator

This n8n template automates the process of creating ATS-friendly resumes and personalized cover letters from uploaded pdf resume.

Use cases

  • Instantly generate ATS-optimized resumes for specific job descriptions.
  • Create customized cover letters tailored to each role.
  • Automate resume enhancement for career portals or HR tools.
  • Build a resume improvement backend for job platforms or AI career assistants.

Good to know

This workflow connects to few basic external services so you’ll need to configure credentials for them before running the template. It works on both cloud and self-hosted n8n instances, and setup typically takes 5–10 minutes.

Requirements

  • n8n Cloud or self-hosted instance
  • Google Gemini API key for AI text generation
  • PDF.co API key for document conversion
  • Gmail account (OAuth connected) for delivery

Customising this workflow

  • Replace Gmail with Slack, Notion, or Drive for flexible document delivery.
  • Integrate other LLMs (like OpenAI GPT or Claude) for different writing styles.
  • Add additional formatting, branding, or multilingual support for global users.
  • Use it as the base for a career assistant automation or HR application backend.

Optimize Resumes & Generate Cover Letters with Gemini AI and PDF.co

This n8n workflow automates the process of optimizing resumes and generating personalized cover letters using Google Gemini AI and PDF.co, triggered by a form submission. It intelligently processes uploaded resumes, extracts key information, and then crafts tailored cover letters based on a job description.

What it does:

  1. Triggers on Form Submission: The workflow starts when a user submits a form, typically containing a resume file and a job description.
  2. Extracts Resume Text: It extracts the text content from the uploaded resume file (e.g., PDF, DOCX).
  3. Optimizes Resume with Gemini AI:
    • It sends the extracted resume text and the job description to the Google Gemini Chat Model.
    • Gemini AI is prompted to optimize the resume by suggesting improvements and tailoring it to the specific job description.
    • The AI also extracts key information from the resume, such as the applicant's name, contact details, and relevant skills.
  4. Generates Cover Letter with Gemini AI:
    • Using the optimized resume data and the job description, Gemini AI generates a personalized cover letter.
    • The cover letter is designed to highlight the applicant's suitability for the role based on the provided job description.
  5. Creates PDF Cover Letter (Placeholder): A placeholder HTTP Request node is included, indicating where an integration with a PDF generation service (like PDF.co, as hinted by the directory name) would be used to convert the generated cover letter text into a professional PDF document.
  6. Saves to Google Drive (Placeholder): A Google Drive node acts as a placeholder for saving the generated documents (optimized resume, cover letter PDF) to a specified Google Drive folder.
  7. Sends Email Notification (Placeholder): A Gmail node is included to demonstrate sending an email notification with the generated documents to the applicant or a recruiter.
  8. Conditional Processing: An If node and a Switch node are present, suggesting potential conditional logic within the workflow, such as checking for specific keywords, file types, or processing different types of submissions.
  9. Data Manipulation: Edit Fields (Set) and Code nodes are used for transforming and manipulating data throughout the workflow, ensuring the correct format for AI prompts and subsequent actions.
  10. Merges Data: A Merge node is used to combine data streams, ensuring all necessary information is available for later steps.

Prerequisites/Requirements:

  • n8n Instance: A running instance of n8n.
  • Google Gemini API Key: Access to the Google Gemini AI model via an API key.
  • Google Drive Account: For saving generated documents.
  • Gmail Account: For sending email notifications.
  • PDF Generation Service (e.g., PDF.co): While a direct node for PDF.co is not in the provided JSON, the HTTP Request node and the directory name suggest its intended use. You would need an account and API key for your chosen PDF service.
  • n8n Form Trigger: The workflow is initiated by an n8n form submission.

Setup/Usage:

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Google Gemini Chat Model: Configure your Google Gemini API credentials.
    • Google Drive: Set up your Google Drive OAuth credentials.
    • Gmail: Set up your Gmail OAuth credentials.
    • (Optional) PDF Generation Service: If using PDF.co or a similar service, configure the HTTP Request node with the appropriate API endpoint and credentials for PDF generation.
  3. Configure the On form submission Trigger:
    • Define the fields for your form, including an input for the resume file and a text area for the job description.
    • Copy the webhook URL provided by the trigger node to embed in your application or share with users.
  4. Customize AI Prompts: Adjust the prompts in the Google Gemini Chat Model nodes to fine-tune resume optimization and cover letter generation according to your specific requirements.
  5. Configure File Operations:
    • In the Google Drive node, specify the target folder where the generated documents should be saved.
    • In the placeholder HTTP Request node, configure the API call to your PDF generation service, passing the generated cover letter text.
  6. Configure Email Notifications: In the Gmail node, set the recipient, subject, and body of the email, attaching the generated resume and cover letter.
  7. Activate the Workflow: Once configured, activate the workflow to start processing form submissions.

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 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

Wessel BulteBy Wessel Bulte
247