Ai-powered Gmail email organization with auto-archiving and priority labels
Needs changesWhat this workflow does
This AI workflow has 12 nodes and runs on Telegram events (message) (plus 1 other trigger). Along the way it connects OpenRouter Chat Model, Telegram and Gmail.
How it runs
Trigger: On Telegram events (message) (plus 1 other trigger).
- Get mails in INBOX (Gmail): get many
- Filter: keeps only the items that match a condition
- Categoriser (AI Agent): runs an AI agent, with model: OpenRouter Chat Model; 2 tools (mail_archiver, mail_label_setter)
- Aggregate: combines items into one
- Reporter (AI Agent): runs an AI agent, with model: OpenRouter Chat Model
- Telegram: uses Telegram
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in Reporter (v1.8), Categoriser (v1.7): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) Reporter (v1.8), Categoriser (v1.7) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (9)
- Manual Trigger
n8n-nodes-base.manualTrigger - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - Telegram Trigger
n8n-nodes-base.telegramTrigger - Gmail Tool
n8n-nodes-base.gmailTool - Aggregate
n8n-nodes-base.aggregate - Telegram
n8n-nodes-base.telegram - AI Agent
@n8n/n8n-nodes-langchain.agent - Gmail
n8n-nodes-base.gmail - Filter
n8n-nodes-base.filter
From the author
Who is this for? This workflow is perfect for busy professionals, students, or anyone who struggles to keep their Gmail inbox organized and clutter-free. What problem is this workflow solving? It helps you avoid email overload by automating the process of…