Tame Your Inbox with Muse

Email is where Muse earns its keep first, for a simple reason: triage is a judgment task repeated daily, which is exactly what delegation is for. I ran this workflow for two weeks. Here's the version that stuck — including the failure that taught me the most.

Phase 1: Connect email (and only email)

Ask Muse to "connect my Gmail" (or your provider), or go to Settings → Connectors. Read the access description. That's the whole phase — one connector, ten minutes. Resist adding the calendar until triage works; combined workflows come later.

Phase 2: Write the triage brief

The brief is the product. Mine, after two weeks of refinement:

Three things to notice: the outcome (three buckets, one-line reasons), the boundaries (no sending, no deleting), and the check-in (show me, then stop). Every delegated workflow you'll ever build has these three parts.

Phase 3: Review the first runs like an editor

The first summary will be roughly right and specifically wrong somewhere. Mine filed a client email under newsletters because the sender used a marketing template — which produced the "treat anything from someone I've emailed before as personal" rule. That one sentence was the entire difference between a demo and a workflow.

Grade on the decisions, not the prose. You're not evaluating writing quality; you're checking whether anything important got misfiled and whether the "why" lines match your judgment.

Phase 4: Make it a goal

Once two consecutive runs need no corrections, promote it: "do this every weekday at 8am." It lands in the Goals tab; Upcoming shows the schedule. Muse works it in the background and the summary is waiting when you start your day.

Keep the approval posture conservative even now: drafts for your approval, never auto-send. The five seconds it takes to approve a reply is the cheapest insurance in the whole system.

Phase 5: Level it up (later)

Only after the daily triage is boring and reliable:

• Draft replies for bucket 1, in your voice, awaiting your approval.
• Calendar awareness — connect the calendar so "needs reply today" factors in what's on your schedule.
• Follow-up tracking — "flag anything I said I'd reply to but haven't within 48 hours."
• Weekly digest — a Friday summary of what the inbox week looked like: volume, themes, what got handled.

Each level is its own two-run review cycle. Don't stack them.

What can go wrong

• Template misreads. Marketing-formatted personal email (and vice versa) is the classic failure. The "emailed before = personal" rule fixes most of it.
• Overconfidence in bucket 3. Skim the junk bucket yourself for the first week. One misfiled invoice teaches this lesson permanently.
• Approval creep. It's tempting to "always allow" drafting after a good week. Don't — the approval tap is also your daily glance at what's happening.
• Scope drift. "While you're in there, also…" is how a working routine becomes an unreviewable one. New jobs get their own briefs.

The payoff

Two weeks in, my morning email went from a 30-minute archaeological dig to a 5-minute review of a summary I trust — with the interesting side effect that I'm more responsive, not less, because the important stuff surfaces instead of drowning. That's the delegation pattern working: not doing less, but spending attention where it counts.

Quick answers