Check-Email Workflow: Inbox Zero Automated
The check-email ClawFlows workflow triages your inbox, flags what matters, archives the noise, and drafts replies to the obvious ones.
Inbox zero was never really about zero. It was about the state of your attention — a sense that you'd dealt with the inbox and could put it down. The problem isn't that email is hard. It's that it's constant. Every time you glance at the inbox, you're making micro-decisions: reply, archive, defer, ignore. Each decision is cheap. Doing them 80 times a day is not.
The fix is batching. Process email in defined blocks, make all the decisions at once, then close the inbox for hours. Everyone who's tried this knows it works. Almost nobody sustains it because ad-hoc batching requires willpower. The check-email workflow from ClawFlows removes the willpower requirement by turning batch processing into a named routine.
Key Takeaways
- check-email is a ClawFlows workflow that triages your inbox in a structured batch pass.
- It categorizes messages into reply-now, defer, archive, and ignore buckets.
- It drafts replies for obvious cases (acknowledgements, simple questions, confirmations).
- It's part of the Work & Meetings category in nikilster/clawflows.
- Running it twice a day replaces checking email 20+ times with no loss of responsiveness.
What the Workflow Does
When you invoke check-email, the workflow runs through:
- Fetches unread messages from your configured inbox
- Applies rules you've defined for routing (newsletters to reader, notifications to archive, etc.)
- Categorizes remaining messages by apparent priority and action type
- Drafts replies for obvious cases using a language model
- Presents a summary with counts per category and the list of actions
- Waits for your approval before executing any destructive actions (deleting, replying)
The whole pass takes about 90 seconds for a typical inbox. The output is a short list of decisions you need to make — usually 5 to 15 messages out of 100+ — plus a set of pre-drafted replies you can approve or edit.
Why Not Full Automation?
Because email is high-stakes. Sending a wrong reply is worse than not sending a reply. The workflow assists — it drafts, categorizes, and filters — but you approve anything outgoing. This is the right tradeoff between speed and safety.
The Batching Model
The whole point is that you don't check email between batches. You run check-email twice a day (maybe three times), and in between, the inbox doesn't exist for you. This is the discipline the workflow enables.
My routine:
- 10:30am — first check-email run after the morning deep work block
- 3:30pm — second check-email run after the afternoon block
- 5pm — optional third run at end of workday if waiting on something
Three runs, maybe five total minutes of actual email attention. The rest of the day is email-free. Nothing urgent slips because urgent things come through other channels (Slack, phone, calendar).
Categorization Defaults
The default categorization buckets:
- Reply now — direct questions, blocking asks, time-sensitive
- Draft and review — replies the workflow has drafted for you
- Defer — needs thought, scheduled for later
- Archive — informational, no action needed
- Ignore — newsletters, notifications, marketing
You can add custom categories. A common addition is "customer support" for people who run a business from their inbox.
The Drafted Replies
The workflow uses a language model to draft replies for messages that fit obvious patterns:
- "Thanks, got it" acknowledgements
- Confirmations of meeting times
- Simple yes/no responses to clear questions
- Standard replies to common requests
These drafts are suggestions. You approve, edit, or reject. For anything nuanced, the workflow just flags it and you write the reply yourself.
The drafting quality is good enough that I accept maybe 40% of drafts without editing, edit another 30% slightly, and write the remaining 30% myself. That's a massive time saving compared to writing everything from scratch.
Integration With Other Workflows
check-email pairs well with:
- morning-briefing — the briefing includes an email count so you see volume early (see Morning Briefing Workflow: Start Your Day Right)
- activate-focus-mode — which closes the email client entirely during deep work (see Focus Mode: The Workflow That Saved My Week)
- end-workday — final email check before shutting down
- build-standup — which reads email for yesterday's context (see Automating Standups With Build-Standup)
The combination creates a workday where email is handled in defined batches rather than as constant background noise.
Customization Examples
How people have customized check-email:
- A consultant added a "client-VIP" category that gets fast-tracked
- A founder added a step to file investor updates into a specific folder
- A remote worker added time-zone-aware deferral (don't reply until recipient's working hours)
- A privacy-focused user added a step to strip tracking pixels before previewing
- A minimalist added aggressive auto-archive rules to reduce manual review
We cover authoring customizations in Writing Your First Custom ClawFlow.
What About Urgent Messages?
The concern people raise: "What if something urgent comes in between batches?"
Two things. First, "urgent" is rarer than you think — most people's actual urgent stuff comes through other channels. Second, the workflow can be configured to surface genuinely urgent messages (based on sender, keywords, or explicit flagging) outside the batch — as a notification rather than a full inbox interruption.
The goal isn't to ignore urgency. It's to stop treating every message as urgent by default.
Privacy and Security
Email is sensitive. check-email runs locally by default — messages don't leave your machine unless you configure a cloud destination. The drafting step does call a language model, which is the one network operation; you can configure which provider and with what data controls.
For people with strict privacy needs, there's a local-only mode that disables drafting. You lose the reply drafts but keep the categorization, which is still valuable.
FAQ
Does it work with Gmail and Outlook?
Yes. Both are supported via the corresponding email skill. Some advanced features (labels, categories, etc.) are provider-specific and covered in the README.
How does it handle replies to threads?
It reads the thread history before drafting, so replies are context-aware. This matters — a reply to an 8-message thread needs to reference the thread, not just the latest message.
Can I use it without drafting?
Yes. Disable the drafting step in the workflow definition and you get pure categorization. Some people prefer this — they want the triage but want to write replies themselves.
Is my email content sent to an AI model?
Only if drafting is enabled. And only the specific messages being drafted, not your whole inbox. You can configure which provider and disable the step entirely.
How long until I trust the categorization?
Usually about a week. You'll see the workflow make mistakes, you'll add rules to catch them, and by the end of the week the categorization matches your judgment for 90%+ of messages.
Stop Living In Your Inbox
If you check email more than three times a day, check-email will recover hours of your week. Install ClawFlows (see How to Install ClawFlows in One Command), configure the workflow, and commit to batch processing for a week. You won't go back.
Explore all 113 workflows at aiskill.market/workflows or submit your own.