AI Job Application Auto-Reply from Gmail
Overview
This workflow automates the process of replying to job applications received via email. When a new email arrives in your Gmail inbox that contains "Job Application" in the subject line, the workflow extracts the candidate's details, uses OpenAI's GPT-4o to generate a professional, courteous reply, and sends it automatically from your company email address. It's ideal for HR teams, startups, or anyone who wants to provide instant acknowledgment to applicants without manual effort.
How It Works
Below is a step-by-step breakdown of every functional node in the workflow:
-
Gmail Trigger (OAuth2) — Monitors your Gmail inbox for new emails. It is configured to watch for emails with a specific label (e.g., "job-applications") and polls every minute. You must set up Gmail forwarding from your custom domain email (e.g., hello@yourcompany.com) to your Gmail address, and create a Gmail filter to apply the label and mark emails as unread.
-
If (No auth) — Checks whether the email subject contains the phrase "job application" (case-insensitive). Only emails that pass this condition proceed to the next steps; others are sent to a "No Operation" node and ignored.
-
Edit Fields (No auth) — Prepares the data for the AI agent by extracting three fields:
candidateEmail: taken from the email's reply-to addresssubject: the original email subjectcompanyEmail: taken from the email's "to" address (your receiving email)
-
AI Agent (No auth) — The core AI node. It receives the prepared data and uses a system prompt that instructs the model to act as an HR assistant for Luminar Technology. The prompt defines rules for generating a reply (address by name, mention position, thank, keep tone professional, output JSON with subject and body). The agent uses the connected OpenAI Chat Model and Structured Output Parser.
-
OpenAI Chat Model (API Key auth) — The language model that powers the AI Agent. It is set to use
gpt-4o(can be changed). You need a valid OpenAI API key stored in your n8n credentials. -
Structured Output Parser (No auth) — Ensures the AI returns a clean JSON object with
subjectandbodyfields. This prevents malformed responses and guarantees compatibility with the email sending node. -
Send an Email (SMTP credentials) — Sends the AI-generated reply. It uses the
toEmail(candidate's email),fromEmail(your company email), subject and body from the AI output. The email is sent as plain text. You must configure SMTP credentials (e.g., host, port, username, password) for your email provider (e.g., Titan Email, Gmail SMTP, etc.). -
No Operation, do nothing (No auth) — A placeholder node that receives emails that do not match the job application filter. It does nothing, effectively discarding those emails.
Setup Instructions
To use this workflow, you need the following accounts and credentials:
- Gmail account — For the Gmail Trigger. You must authorize n8n to access your Gmail inbox (OAuth2). Also, if you use a custom domain email (e.g., hello@yourcompany.com), set up forwarding from that domain to your Gmail address and create a Gmail filter to label incoming forwarded emails as "job-applications" and mark them as unread.
- OpenAI account — Obtain an API key from platform.openai.com. Store it as an n8n credential of type "OpenAI".
- SMTP credentials — For sending emails. If you use Gmail's SMTP, you can use an App Password. For other providers (e.g., Titan Email, Outlook), use the SMTP host, port, and login details. Store these as an n8n credential of type "SMTP".
Use Cases & Variations
- Customize the filter: Change the condition in the If node to match other keywords like "Application", "CV", "Resume", or use more complex logic (e.g., AND/OR conditions).
- Change the AI model: In the OpenAI Chat Model node, switch to
gpt-3.5-turbofor lower cost orgpt-4for higher quality. - Modify the reply tone: Edit the system prompt in the AI Agent node to match your company's voice (e.g., more formal, more friendly, include specific next steps).
- Add attachments or HTML formatting: In the Send an Email node, change the email format to HTML and include a rich signature or company logo.
- Log replies to a spreadsheet: Insert a Google Sheets node after the AI Agent to record each reply for tracking.
- Handle multiple email addresses: Adjust the Edit Fields node to extract the candidate email from the email body if forwarding changes the From field.
Workflow JSON
{
"id": "HApWnFS5OFYeT2mU",
"meta": {
"instanceId": "cd85e2ca4f76efc43b2440fb23c17eaa4937a3abf54776244bd0a689d171e1bd",
"templateCredsSetupCompleted": true
},
"name": "EmailAutoReply",
"tags": [],
"nodes": [
{
"id": "a5d6cb90-5aee-4269-b9f2-71e11e68d6df",
"name": "Gmail Trigger",
"type": "n8n-nodes-base.gmailTrigger",
"position": [
-96,
80
],
"parameters": {
"simple": false,
"filters": {
"labelIds": [
"Label_2862649459238172600"
]
},
"options": {},
"pollTimes": {
"item": [
{
"mode": "everyMinute"
}
]
}
},
"credentials": {
"gmailOAuth2": {
"id": "4VIIUTF24mDLFogT",
"name": "Gmail account"
}
},
"typeVersion": 1.3
},
{
"id": "0f62160f-d729-4f70-8a3b-783749fbf418",
"name": "OpenAI Chat Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
768,
240
],
"parameters": {
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
YouTube Video Summarizer with Telegram Notification
High-Level Summary This workflow automatically processes YouTube videos by fetching their transcripts, generating a structured AI-powered summary using OpenAI's GPT-4o-mini, and sending the summary along with video metadata to a Telegram chat. It is triggered via a webhook, making it easy to integrate with other tools or services (e.g., a browser extension, a form, or another automation). The workflow is ideal for content curators, researchers, or teams who want to quickly digest video content without watching the full video. Workflow Steps Webhook — Receives an incoming HTTP POST request containing a YouTube URL in the request body. This is the entry point of the workflow. (No auth) Get YouTube URL (Set node) — Extracts the field from the incoming webhook payload and stores it as a string variable for downstream use. (No auth) YouTube Video ID (Code node) — Runs a JavaScript function that parses the YouTube URL using a regex pattern to extract the 11-character video ID (supports both and formats). (No auth) Get YouTube Video (YouTube node) — Uses the extracted video ID to fetch video metadata (title, description, etc.) from the YouTube Data API v3. (OAuth2 — requires a Google Cloud project with YouTube Data API enabled) YouTube Transcript (Community node: ) — Fetches the transcript/captions for the video. This node requires the video ID (passed from the previous step). (No auth — uses public YouTube captions) Split Out (SplitOut node) — Splits the transcript array into individual items so each text segment can be processed separately. (No auth) Concatenate (Summarize node) — Concatenates all transcript text segments into a single string, separated by spaces, to prepare the full transcript for analysis. (No auth) gpt-4o-mini (OpenAI Chat Model node) — Configures the OpenAI language model (GPT-4o-mini) that will be used for summarization. (API Key auth — requires an OpenAI API key) Summarize & Analyze Transcript (LLM Chain node) — Sends the concatenated transcript to the GPT-4o-mini model with a detailed prompt asking for a structured summary with headers, bullet points, bold terms, and tables. The output is a markdown-formatted analysis. (No auth — uses the model configured in the previous node) Response Object (Set node) — Assembles the final output object containing: - : The AI-generated summary text - : An empty array (placeholder for future use) - : The video title from YouTube metadata - : The video description from YouTube metadata - : The YouTube video ID - : The original YouTube URL from the webhook (No auth) Respond to Webhook — Sends the assembled response object back to the original webhook caller (e.g., a browser extension or app). (No auth) Telegram — Sends a message to a specified Telegram chat containing the video title and the YouTube URL. (API Key auth — requires a Telegram Bot Token and chat ID) Setup Instructions To use this workflow, you will need the following accounts and credentials: OpenAI Account: Create an account at platform.openai.com and generate an API key. Add this as a credential in n8n under "OpenAI". Google Cloud Project: Enable the YouTube Data API v3 in your Google Cloud Console, create OAuth 2.0 credentials (Desktop app type), and add them in n8n under "YouTube OAuth2 API". Telegram Bot: Create a bot via @BotFather on Telegram to get a Bot Token. Find your chat ID (e.g., by messaging your bot and visiting ). Add the token as a credential in n8n under "Telegram API". Webhook URL: After activating the workflow, copy the production webhook URL (e.g., ). You will send POST requests to this URL with a JSON body like . Use Cases and Variations Content Curation: Automatically summarize long conference talks, tutorials, or webinars and share them with your team on Telegram. Research Assistant: Collect video transcripts and AI summaries for later reference or database storage. Browser Extension Integration: Pair this workflow with a browser extension that sends the current YouTube URL to the webhook when clicked. Variations: - Replace Telegram with Slack, Discord, or email notifications. - Store summaries in a Google Sheet or Airtable for a searchable archive. - Add a filter to skip videos shorter than a certain duration. - Use a different LLM (e.g., Claude, Gemini) by swapping the OpenAI node. - Add error handling to notify you if a video has no captions.
Telegram to Email Newsletter Automation using Dumpling AI
High-Level Summary This workflow transforms a simple keyword sent via Telegram into a polished, HTML-formatted email newsletter. It leverages Dumpling AI's APIs for search and scraping, OpenAI's language models for content generation, and Gmail for delivery. The automation is ideal for content creators, marketers, or anyone who wants to quickly curate and distribute news on a specific topic without manual research and formatting. Step-by-Step Node Breakdown Start: Receive Keyword from Telegram (Telegram Trigger) — No auth (uses Telegram bot token configured in n8n credentials). Listens for incoming Telegram messages. When a message is received, it passes the message text (the keyword) to the next node. AI Agent: Expand Keyword & Orchestrate Tools (LangChain Agent) — Uses the connected LLM and tools. The system prompt instructs the agent to first call to expand the keyword into popular search terms, then pass those terms to to fetch recent articles. The agent outputs a structured JSON array of articles. LLM: Language Model (OpenAI Chat Model) — API Key auth (OpenAI API key stored in n8n). Provides the language model (GPT-4o-mini) that powers the AI Agent's reasoning and tool selection. Simple Memory (Memory Buffer Window) — Stores conversation context for the AI Agent using the Telegram user's ID as the session key. Google_autocomplete (HTTP Request Tool) — Header Auth (Dumpling AI API key in header). Calls with a POST request containing the keyword. Returns autocomplete suggestions from Google. Search_news (HTTP Request Tool) — Header Auth (Dumpling AI API key in header). Calls with a POST request containing the autocomplete suggestion. Returns recent news articles. Parser: Format News JSON (Output Parser) — Defines a JSON schema that the AI Agent must follow when outputting the final list of articles (with fields: category, title, url, source, summary, published). Split Articles (Split Out) — Splits the array from the agent into individual items, one per article. Loop: Process Each Article (Split In Batches) — Iterates over each article one at a time. For each article, it triggers the Wait node and then the Scraper. Wait (Wait) — No auth. Adds a small delay (configurable) between scraping requests to avoid rate limiting. Scraper: Clean Article Content (HTTP Request) — Header Auth (Dumpling AI API key in header). Calls with the article URL and to get the article's main content in markdown format. Aggregate: Combine Article Content (Aggregate) — Collects the field from all scraped articles into a single array. Generate Newsletter (OpenAI) — API Key auth (OpenAI API key). Sends the aggregated content to GPT-4.1-mini with a system prompt that instructs it to generate a professional HTML newsletter and a subject line. Outputs JSON with (HTML) and fields. Send Newsletter via Email (Gmail) — OAuth2 (Google account connected via n8n Gmail node). Sends the generated HTML newsletter to a specified email address with the generated subject line. Setup Instructions To use this workflow, you will need accounts and API keys for the following services: Telegram: Create a bot via @BotFather and get the bot token. Configure the Telegram Trigger node with this token. Dumpling AI: Sign up at app.dumplingai.com and generate an API key. This key is used as a header () in the three HTTP Request nodes (Googleautocomplete, Searchnews, Scraper). OpenAI: Sign up at platform.openai.com and create an API key. Use this in the LLM node and the Generate Newsletter node. Gmail: Connect your Google account via OAuth2 in n8n's Gmail node. Ensure the email address you want to send to is authorized (or use your own address for testing). After configuring all credentials, activate the workflow and send a keyword (e.g., "AI in retail") to your Telegram bot. The workflow will run and deliver a newsletter to your inbox. Use Cases and Variations Content Curation for Newsletters: Replace the Telegram trigger with a Schedule trigger to run daily or weekly on predefined keywords (e.g., "tech news", "climate change"). Brand Monitoring: Use the workflow to monitor news about your brand or competitors and send alerts to your team via email or Slack. Personalized Digests: Modify the AI prompt to generate summaries in different languages or tones (e.g., executive brief, casual digest). Multi-Channel Delivery: Instead of Gmail, send the newsletter to Slack, Discord, or a Notion database by swapping the final node. Add Human Review: Insert a manual approval step (e.g., n8n's "Wait" node with webhook) before sending, so you can review and edit the newsletter.
AI-Powered Gmail Email Classifier & Labeler
Overview This workflow automatically monitors your Gmail inbox for new emails, retrieves the full email content, and uses an AI agent powered by Anthropic's Claude to classify each email into a predefined Gmail label. It also checks prior email history with the sender to improve classification accuracy. Finally, it applies the chosen label to the email, helping you organize your inbox without manual effort. How It Works Gmail Trigger — Polls Gmail every minute for new emails (OAuth2). Gmail — Fetches the full email details (headers, body, etc.) using the message ID from the trigger (OAuth2). AI Agent — Orchestrates the classification process. It uses the Anthropic Chat Model as its language model and the Structured Output Parser to extract the label ID. The agent also has access to two Gmail tools to check prior email history. Anthropic Chat Model — The LLM (Claude Sonnet 4) that analyzes the email content and history to decide the best label (API Key auth). Structured Output Parser — Ensures the AI's response is a valid JSON object containing the label ID (No auth). Get Email — A Gmail tool used by the AI agent to search for prior emails from the sender (OAuth2). Check Sent — A Gmail tool used by the AI agent to check if the user has previously sent emails to the sender (OAuth2). Gmail1 — Applies the chosen label to the original email (OAuth2). Node Details Gmail Trigger (OAuth2) — Polls Gmail every minute for new messages. No filters are set, so it watches the entire inbox. Gmail (OAuth2) — Uses the operation to retrieve the full email object by . The option is disabled to get the raw JSON. Anthropic Chat Model (API Key auth) — Configured to use the model with default options. AI Agent (No auth) — Contains a detailed system message that instructs the AI to classify emails into one of six labels (To Respond, FYI, Comment, Notification, Meeting Update, Marketing) based on content, headers, and prior email history. It uses the input "Run the task." and has an output parser attached. Structured Output Parser (No auth) — Expects a JSON schema with keys and . This forces the AI to output a clean JSON object. Get Email (OAuth2) — Gmail tool that searches for emails from the sender using the query. It returns all matching emails (no limit). Check Sent (OAuth2) — Gmail tool that searches for emails sent to the sender in the folder, using the query. Gmail1 (OAuth2) — Uses the operation to apply the label ID returned by the AI agent to the original email. Setup Instructions Gmail OAuth2 Credentials — You need a Google Cloud project with the Gmail API enabled. Create OAuth2 credentials (Desktop app or Web application) and add them in n8n under Credentials > Google. The workflow uses OAuth2 for all Gmail nodes. Anthropic API Key — Sign up at Anthropic and generate an API key. Add it in n8n under Credentials > Anthropic. Gmail Labels — The workflow expects specific label IDs (e.g., for "To Respond"). You must create these labels in your Gmail account and note their IDs. Alternatively, you can modify the system message in the AI Agent node to use your own label names/IDs. Activate the workflow — Once credentials are set and labels exist, activate the workflow. It will start polling Gmail and classifying new emails. Use Cases & Variations Personal Inbox Zero — Automatically sort newsletters, notifications, and actionable emails into separate folders. Sales Pipeline Management — Classify incoming leads as "To Respond" or "Marketing" based on prior contact. Support Ticket Triage — Route customer emails to appropriate labels based on content and history. Custom Labels — Modify the AI agent's system prompt to use your own set of labels (e.g., "Urgent", "Read Later", "Archive"). Integration with Other Tools — After labeling, you could add nodes to send Slack notifications, create tasks in Notion, or log to a spreadsheet.