AI Gmail Triage: Auto-Label Emails and Slack Urgent Alerts

Overview

This workflow automatically triages incoming Gmail emails by classifying them into one of four categories (Urgent, Customer, Invoice, Newsletter) using OpenAI's GPT model. It then applies the corresponding Gmail label to keep your inbox organized. If an email is classified as urgent, it sends a real-time alert to a Slack channel with the sender and subject line. The workflow runs every 5 minutes via the Gmail trigger, ensuring you never miss an important message.

Perfect for professionals who receive a high volume of email and want to reduce manual sorting time. With AI-powered classification, you can customize the categories to match your business needs—such as support tickets, partner inquiries, or internal notifications.

Nodes and Their Roles

Below is a complete list of nodes in the workflow, their types, authentication methods, and what they do.

  • New Email (n8n-nodes-base.gmailTrigger) — OAuth2 (Gmail). Polls your Gmail inbox every 5 minutes for new emails. It fetches only new messages since the last run and passes them to the next node.
  • Classify (@n8n/n8n-nodes-langchain.openAi) — API Key (OpenAI). Sends the email's from, subject, and body (first 2000 characters) to the GPT model with a prompt instructing it to return exactly one category word: URGENT, CUSTOMER, INVOICE, or NEWSLETTER. The node is configured to retry up to 3 times with a 5-second delay to handle transient API errors.
  • Map to Label (n8n-nodes-base.code) — No auth. A JavaScript code node that takes the category from the OpenAI response, looks up the corresponding Gmail label ID (using placeholder values you must replace), and outputs a JSON object containing messageId, category, labelId, from, and subject.
  • Apply Gmail Label (n8n-nodes-base.gmail) — OAuth2 (Gmail). Uses the messageId and labelId from the previous node to add the specified label to the email in Gmail.
  • Urgent? (n8n-nodes-base.if) — No auth. A conditional node that checks if the category field equals URGENT. If true, the workflow proceeds to the Slack alert; otherwise, it ends.
  • Slack Alert (n8n-nodes-base.slack) — OAuth2 (Slack). Sends a formatted message to a specified Slack channel containing the sender and subject of the urgent email, with a rotating light emoji as a visual alert.

Setup Instructions

Before running the workflow, you need to configure the following credentials and placeholder values:

  1. Gmail (OAuth): Connect your Gmail account in n8n credentials. This is required for both the trigger and the label node. Ensure the account has access to the labels you'll create.
  2. Create Labels in Gmail: Manually create four labels in your Gmail account: AI/Urgent, AI/Customer, AI/Invoice, AI/Newsletter. To get their IDs, use the n8n Gmail node's label dropdown (or inspect the Gmail API). Copy each label ID and paste it into the corresponding placeholder in the Map to Label code node (REPLACE_WITH_URGENT_LABEL_ID, etc.).
  3. OpenAI API Key: Add your OpenAI API key as an n8n credential. The node uses the gpt-5.6-luna model (you may change to a different model). Adjust the four category definitions in the prompt if your business uses different terms.
  4. Slack (OAuth): Connect your Slack workspace. Create a Slack channel (e.g., #urgent-emails) and replace REPLACE_WITH_CHANNEL in the Slack Alert node with the channel ID (or name).
  5. Activate the workflow: After replacing all placeholders, activate the workflow and send test emails to verify classification and alerting.

Use Cases and Variations

  • Customer Support: Adapt the categories to classify support tickets, billing issues, and feature requests. Urgent alerts could notify your support team in Slack instantly.
  • Sales Pipeline: Use categories like Lead, Follow-up, Closed Won, Meeting Request. Route high-priority leads to a sales channel.
  • Personal Inbox: Filter newsletters, receipts, and personal messages. Send urgent family or work emails to your phone via Slack.
  • Multi-account: Duplicate the workflow for multiple Gmail accounts by using different credentials and channels.
  • Other Actions: Instead of Slack alerts, you could create a Trello card, send an SMS via Twilio, or log the email to a Google Sheet for later analysis.

This template is a solid foundation for AI-powered email automation. Customize the prompt, categories, and downstream actions to fit your workflow perfectly.

9 nodesmanual triggerProductivity
Sticky NoteOpen AICodeGmailIFSlack

Workflow JSON

{
  "name": "AI Gmail Triage",
  "nodes": [
    {
      "parameters": {
        "content": "## AI Email Triage: Auto-Label Gmail + Urgent Alerts\n\nOpen your inbox to find everything pre-sorted: customer emails labeled, invoices filed, newsletters out of the way - and anything urgent already waiting in Slack.\n\n**Setup time:** 15 minutes  ·  **Level:** Intermediate\n\n**You'll need accounts/credentials for:** Gmail, OpenAI, Slack\n\n**Replace these before running:**\n- `REPLACE_WITH_URGENT_LABEL_ID`\n- `REPLACE_WITH_CUSTOMER_LABEL_ID`\n- `REPLACE_WITH_INVOICE_LABEL_ID`\n- `REPLACE_WITH_NEWSLETTER_LABEL_ID`\n- `REPLACE_WITH_CHANNEL`\n\n**Setup steps:**\n1. Connect Gmail (OAuth) in the trigger and the label node.\n2. In Gmail, create labels: AI/Urgent, AI/Customer, AI/Invoice, AI/Newsletter. Get their IDs from the n8n Gmail node's label dropdown and paste them into the Code node mapping.\n3. Add your OpenAI API key, and adjust the four category definitions in the prompt to your business.\n4. Connect Slack for urgent alerts. Activate and send yourself test emails.\n\nFree templates and updates: navkhan103.github.io",
        "height": 684,
        "width": 400,
        "color": 4
      },
      "id": "sticky-setup",
      "name": "Setup — read me first",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        -440,
        -120
      ]
    },
    {
      "parameters": {
        "content": "### How it runs\n\nStarts from **New Email**.\n\n1. A Gmail Trigger polls for new inbox messages every few minutes.\n2. An OpenAI node classifies the email into one of four categories, replying with a single word.\n3. A Code node maps the category to your Gmail label ID.\n4. A Gmail node applies the label.\n5. An IF node routes Urgent emails to a Slack alert with sender and subject.",
        "height": 374,
        "width": 400,
        "color": 7
      },
      "id": "sticky-how",
      "name": "How it runs",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        -440,
        604
      ]
    },
    {
      "parameters": {
        "content": "### If something breaks\n\nThe read and AI nodes here **retry 3× automatically** (5s apart), which absorbs rate limits and brief timeouts.\n\nNodes that **send or write deliberately do not retry** — a send that reached the far end but lost its response would otherwise fire twice, so you'd get duplicate messages or duplicate rows.\n\nTo be told when one of those fails, build a workflow starting with an **Error Trigger** node that posts to Slack or email, then set it under **three-dot menu > Settings > Error Workflow**. Do it once and point every workflow at it.",
        "height": 400,
        "width": 400,
        "color": 3
      },
      "id": "sticky-fail",
      "name": "If something breaks",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        -440,
        1018
      ]
// ... truncated (copy to see full JSON)

How to Import This Workflow

  1. 1Copy the workflow JSON above using the Copy Workflow JSON button.
  2. 2Open your n8n instance and go to Workflows.
  3. 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.

12 nodes

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.

16 nodes

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.

8 nodes

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.