PERSONAL PRODUCTIVITY

Gmail Resolved-Thread Auto-Archiver

Scans your inbox on a schedule, detects email threads that are effectively resolved (last reply was a thanks, confirmation, or you closing the loop).

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly archive sweep fires
  • ActionFetch stale inbox threadsGmailGmail
  • LogicClassify resolved vs. awaiting actionOpenAI
  • LogicGuard: skip open questions and VIP senders
  • OutputLabel and archive resolved threadsGmailGmail

What it does

This workflow clears notification debt in Gmail by archiving threads that are done but still sitting in your inbox. It reads each open thread, judges whether it is resolved — a closing thank-you, a delivery confirmation, or your own final reply with no open question — and archives those, applying a 'Auto-resolved' label so nothing is silently lost.

When to use it

Use it when your inbox stays cluttered with finished conversations you never got around to archiving, making it hard to see what actually needs a reply. Best for people who treat the inbox as a to-do list and want it to reflect only live threads.

How it works

  1. 1A scheduled trigger runs the sweep (for example every evening).
  2. 2The flow fetches inbox threads untouched for a configurable window (for example 2+ days).
  3. 3For each thread, a classifier reads the last few messages and decides resolved vs. awaiting-action.
  4. 4A guard skips threads containing open questions, due dates, or VIP senders to avoid false archives.
  5. 5Resolved threads get the 'Auto-resolved' label applied and are archived out of the inbox.

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.