PERSONAL PRODUCTIVITY

Inbox-Zero Triage: Auto-Label and Draft Routine Replies

Classifies every new Gmail message into action categories, applies the matching label.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email received in Gmail inboxGmailGmail
  • ActionClassify intent and extract gist with OpenAIOpenAI
  • LogicBranch on category: reply / FYI / ignore
  • ActionDraft reply in your voice with OpenAIOpenAI
  • ActionApply matching Gmail label to threadGmailGmail
  • OutputSave draft reply to Gmail thread, unsentGmailGmail

What it does

Watches your Gmail inbox and turns each incoming message into a triaged, labeled item. An LLM reads the email, decides whether it needs a reply, an FYI label, or no action, and for the routine stuff (scheduling, intro requests, status pings) it writes a draft reply in your voice. Drafts land in Gmail so nothing sends without your final click.

When to use it

Use it when your inbox fills with predictable, low-stakes messages that each cost a few minutes of context-switching. It is built for an operator who wants to open the inbox once a day and find everything sorted and pre-drafted instead of starting every reply from a blank screen.

How it works

  1. 1A new email arrives in the connected Gmail inbox and fires the trigger.
  2. 2OpenAI classifies the message into one of: reply-needed, FYI, or ignore, and extracts the gist.
  3. 3A branch routes on that category.
  4. 4For reply-needed routine mail, OpenAI drafts a reply matching prior tone.
  5. 5The Gmail label for the category is applied to the thread.
  6. 6The draft is saved to the Gmail thread, left unsent for human review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.