HumationHuman + Automation
Back to Catalog

Personalize resumes & cover letters with AI, GitHub Pages and Google Drive

Michael A PutraMichael A Putra
4274 views
2/3/2026
File ManagementGoogle SheetsGoogle DriveData LoggingAutomation
Official Page

🧠 Automated Resume & Cover Letter Generator

This project is an automation workflow that generates a personalized resume and cover letter for each job listing.

🚀 Features

Automated Resume Crafting

  • Generates an HTML resume from your data.
  • Hosts it live on GitHub Pages.
  • Converts it to PDF using Gotenberg and saves it to Google Drive.

Automated Cover Letter Generation

  • Uses an LLM to create a tailored cover letter for each job listing.

Simple Input Database Agent

  • Stores your experience in an n8n Data Table with the following fields:
    role, summary, task, skills, tools, industry.
  • The main agent pulls this data using RAG (Retrieval-Augmented Generation) to personalize the outputs.

One-Time GitHub Setup

  • Initializes a blank GitHub repository to host HTML files online, allowing Gotenberg to access and convert them.

🧩 Tech Stack

  • Gotenberg – Converts HTML to PDF
  • GitHub Pages – Hosts live HTML files
  • n8n – Handles data tables and workflow automation
  • LLM (OpenAI / Cohere / etc.) – Generates cover letters
  • Google Drive – Stores the final PDFs

⚙️ Installation & Setup

1. Create a GitHub Repository

  • This repo will host your HTML resume through GitHub Pages.

2. Set the Webhook URL

  • In the notify-n8n.yml file, replace: role | summary | task | skills | tools | industry

3. Create the n8n Data Table

Add the following columns:

role | summary | task | skills | tools | industry

4. Create a Google Spreadsheet

  • Add these columns:
    company | cover_letter | resume

5. Install Gotenberg

6. Customize the HTML Template

  • Modify the HTML resume to your liking.
  • You can use an LLM to locate and edit specific sections.

7. Add Authentication and Link Your GitHub Repo

  • Ensure your workflow has permission to push updates to your GitHub Pages branch.

8. Run the Workflow

  • Once everything is connected, trigger the workflow to automatically generate and save personalized resumes and cover letters.

📝 How to Use

  1. Copy and paste the job listing description into the Telegram bot.
  2. Wait for the "Done" notification before submitting another job.
    • Do not use the bot again until the notification appears.
    • The process usually takes a few minutes to complete.

✅ Notes

This workflow is designed to save time and personalize your job applications efficiently.
By combining n8n automation, LLMs, and open-source tools like Gotenberg, you can maintain full control over your data while generating high-quality resumes and cover letters for every job opportunity.

AI-Powered Resume and Cover Letter Personalization with n8n

This n8n workflow automates the process of generating personalized resumes and cover letters using AI, leveraging GitHub Pages for hosting, and Google Drive for document management. It streamlines the job application process by dynamically tailoring application materials based on job descriptions.

What it does

This workflow orchestrates several services to create a seamless personalization pipeline:

  1. Triggers on Demand: The workflow can be manually triggered to initiate the personalization process.
  2. Receives Chat Messages: It can also be triggered by chat messages, suggesting a conversational interface for requesting personalized documents.
  3. Retrieves Data from Google Sheets: It fetches resume and cover letter templates, along with other relevant information, from Google Sheets.
  4. Retrieves Data from Google Drive: It accesses existing resume and cover letter documents stored in Google Drive.
  5. Processes with AI Agent: An AI agent, powered by an OpenAI Chat Model and Simple Memory, processes the input (likely a job description) and existing templates to generate personalized content.
  6. Parses AI Output: A Structured Output Parser extracts the relevant, formatted data from the AI agent's response.
  7. Transforms and Edits Data: The workflow uses "Edit Fields" and "Code" nodes to manipulate and prepare the data for further steps.
  8. Generates HTML: It constructs HTML content, likely for the personalized resume and cover letter, which can then be rendered.
  9. Interacts with GitHub: It interacts with GitHub, potentially to update or create new files on GitHub Pages for hosting the generated documents.
  10. Sends Telegram Notifications: It can send messages or notifications via Telegram, possibly to alert the user about the completion of the personalization process or to deliver the generated documents.
  11. Makes HTTP Requests: It can make generic HTTP requests to interact with other web services or APIs not explicitly listed.
  12. Manages Data with Data Table: A Data Table node is available for managing structured data within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: For the OpenAI Chat Model used by the AI Agent.
  • Google Sheets Account: With a spreadsheet containing your resume/cover letter templates and other relevant data.
  • Google Drive Account: To store and retrieve your base resume and cover letter documents.
  • GitHub Account: For deploying and hosting personalized documents on GitHub Pages.
  • Telegram Bot Token: If you wish to receive notifications or interact with the workflow via Telegram.
  • n8n LangChain Nodes: Ensure you have the LangChain nodes installed in your n8n instance.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up credentials for your OpenAI account.
    • Configure Google Sheets credentials.
    • Set up Google Drive credentials.
    • Configure GitHub credentials.
    • Set up Telegram credentials (for both the Telegram and Telegram Trigger nodes).
  3. Customize Nodes:
    • Google Sheets: Update the spreadsheet ID and range to point to your resume/cover letter templates and data.
    • Google Drive: Specify the file IDs or folder paths for your base resume and cover letter documents.
    • AI Agent: Configure the prompts and tools for the AI agent to effectively personalize the documents based on job descriptions.
    • Structured Output Parser: Adjust the schema to match the expected output format from your AI agent.
    • Edit Fields & Code: Customize these nodes to transform the AI-generated content into the desired structure for your documents.
    • HTML: Configure this node to correctly render the personalized content into an HTML resume/cover letter.
    • GitHub: Define the repository, file paths, and commit messages for updating your GitHub Pages.
    • Telegram: Specify the chat ID for sending notifications or the bot commands for triggering the workflow.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Trigger the Workflow:
    • Manually: Click "Execute workflow" in the n8n editor.
    • Via Chat Message: Send a message to your configured Telegram bot (if the "Chat Trigger" node is set up).
    • Via Webhook: Send an HTTP POST request to the Webhook URL (if the "Webhook" node is configured).

This workflow provides a powerful foundation for automating and personalizing your job application materials, significantly reducing manual effort and improving efficiency.

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