Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

The Inbox Autopilot: What 60 Days of Letting an n8n Workflow Triage My Email Taught Me

Description and use

Automated email triage and draft generation with n8n and LLM saves 35 minutes daily, employing a confidence gate and tone templates.

Problem

Daily email triage consumed 45 minutes each morning, requiring manual decisions on urgency, reply necessity, and noise.

Outcome

The workflow reduced triage time by ~35 minutes daily, introduced a confidence gate to handle uncertainty, and used per-bucket tone templates to improve draft appropriateness. Over 60 days, no incidents occurred.

Workflow

  • Trigger on new Gmail messages
  • Strip signatures, disclaimers, and quoted history via Code node
  • Classify email into buckets (urgent, needs-reply, waiting-on-me, newsletter, noise) using LLM
  • Apply confidence gate; emails below 0.75 go to unsure bucket
  • For needs-reply, generate draft reply in author’s voice via second LLM call
  • Store drafts in Gmail drafts folder
  • Send urgent pings via Slack/Telegram
  • Auto-archive newsletters
  • Morning review: search Gmail drafts newer_than:1d, approve or edit

Evidence

Every morning I did the same thing: open Gmail, scan 60–80 new emails, decide what needed a reply, what could wait, and what was noise. It took 45 minutes on a good day.

Source

It now saves me about 35 minutes every morning.

Source

The workflow never sends email. Draft-only.

Source

The confidence gate (the part I'd copy anywhere) ... Below 0.75, the email goes into a sixth bucket: unsure – always shown to the human, never auto-filed.

Source

  • Record date: 2026-10-16T10:40:59.613Z