Merge node
Gmail node
+6

Auto-label incoming Gmail messages with AI nodes

Published 7 months ago

Created by

workfloows
Oskar

Categories

Template description

This workflow uses AI to analyze the content of every new message in Gmail and then assigns specific labels, according to the context of the email.

Default configuration of the workflow includes 3 labels:

  • „Partnership” - email about sponsored content or cooperation,
  • „Inquiry” - email about products, services,
  • „Notification” - email that doesn't require response.

You can add or edit labels and descriptions according to your use case.

🎬 See this workflow in action in my YouTube video about automating Gmail.

How it works?

Gmail trigger performs polling every minute for new messages (you can change the trigger interval according to your needs). The email content is then downloaded and forwarded to an AI chain.

💡 The prompt in the AI chain node includes instructions for applying labels according to the email content - change label names and instructions to fit your use case.

Next, the workflow retrieves all labels from the Gmail account and compares them with the label names returned from the AI chain. Label IDs are aggregated and applied to processed email messages.

⚠️ Label names in the Gmail account and workflow (prompt, JSON schema) must be the same.

Set up steps

  1. Set credentials for Gmail and OpenAI.
  2. Add labels to your Gmail account (e.g. „Partnership”, „Inquiry” and „Notification”).
  3. Change prompt in AI chain node (update list of label names and instructions).
  4. Change list of available labels in JSON schema in parser node.
  5. Optionally: change polling interval in Gmail trigger (by default interval is 1 minute).

If you like this workflow, please subscribe to my YouTube channel and/or my newsletter.

Share Template

More AI workflow templates

OpenAI Chat Model node
SerpApi (Google Search) node

AI agent chat

This workflow employs OpenAI's language models and SerpAPI to create a responsive, intelligent conversational agent. It comes equipped with manual chat triggers and memory buffer capabilities to ensure seamless interactions. To use this template, you need to be on n8n version 1.50.0 or later.
n8n-team
n8n Team
HTTP Request node
Merge node
+7

Scrape and summarize webpages with AI

This workflow integrates both web scraping and NLP functionalities. It uses HTML parsing to extract links, HTTP requests to fetch essay content, and AI-based summarization using GPT-4o. It's an excellent example of an end-to-end automated task that is not only efficient but also provides real value by summarizing valuable content. Note that to use this template, you need to be on n8n version 1.50.0 or later.
n8n-team
n8n Team
HTTP Request node
Markdown node
+5

AI agent that can scrape webpages

⚙️🛠️🚀🤖🦾 This template is a PoC of a ReAct AI Agent capable of fetching random pages (not only Wikipedia or Google search results). On the top part there's a manual chat node connected to a LangChain ReAct Agent. The agent has access to a workflow tool for getting page content. The page content extraction starts with converting query parameters into a JSON object. There are 3 pre-defined parameters: url** – an address of the page to fetch method** = full / simplified maxlimit** - maximum length for the final page. For longer pages an error message is returned back to the agent Page content fetching is a multistep process: An HTTP Request mode tries to get the page content. If the page content was successfuly retrieved, a series of post-processing begin: Extract HTML BODY; content Remove all unnecessary tags to recude the page size Further eliminate external URLs and IMG scr values (based on the method query parameter) Remaining HTML is converted to Markdown, thus recuding the page lengh even more while preserving the basic page structure The remaining content is sent back to an Agent if it's not too long (maxlimit = 70000 by default, see CONFIG node). NB: You can isolate the HTTP Request part into a separate workflow. Check the Workflow Tool description, it guides the agent to provide a query string with several parameters instead of a JSON object. Please reach out to Eduard is you need further assistance with you n8n workflows and automations! Note that to use this template, you need to be on n8n version 1.19.4 or later.
eduard
Eduard

Implement complex processes faster with n8n

red icon yellow icon red icon yellow icon