Free for 30 days on Scale.Start free
Run10 steps3-5 days build, 1 week shadow run before live

Automate your inbox triage with an agent

An agent triaging your inbox daily: labels every incoming email by your taxonomy, drafts replies on the routine ones, surfaces the 5 that need human attention in a morning digest, never auto-sends without a human click.

Open in DockSee every step →

An agent triaging your inbox daily: labels every incoming email by your taxonomy

An agent triaging your inbox daily: labels every incoming email by your taxonomy, drafts replies on the routine ones, surfaces the 5 that need human attention in a morning digest, never auto-sends without a human click.

Spin up an agent for the heavy lifting

Drafting agent (yours): drafts the labels + classification system prompt from your real inbox patterns. Drafts replies on routine emails (never sends).

10 steps, 16 official links, 4 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

6Surfaces
10Steps
4Agent prompts
16Official links
5Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docInbox triage agent plan
  • tableTriage log
  • docDaily digest
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/automate-your-inbox-with-an-agent and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

Is it safe to let an AI agent read my email?
Safer than letting it send. The pattern in this template is read-only API access (gmail.readonly + gmail.modify) for labels and drafts; no gmail.send scope ever. The agent never auto-sends; humans click Send on every reply. Your email content goes to the model API (Anthropic / OpenAI) for classification, both have enterprise data agreements that don't train on your data; verify those terms apply to your account tier.
Won't the agent miss something important?
It will. The mitigation is the morning digest + flag-when-in-doubt rule. The agent labels emails it's confident about and flags everything else for human review. After 1 week of shadow running, you'll know your classification accuracy on each label; tune the confidence threshold so 'flag for review' captures the edge cases. A 95% accurate agent on a 200-email/day inbox flags ~10 emails for human attention, exactly the volume you can review in 5 min.
How much does this cost in API tokens?
For a 200-email/day inbox using Claude Sonnet: ~$10-20/month in token cost (each email is ~500-1000 input tokens for classification + a 50-200 token output). Switch to Haiku for ~$2-4/month if you don't need draft quality. Heavy drafters (5+ replies/day) push toward $30-50/mo. Cron + hosting is $0-10/mo on free tiers. Total: $15-60/mo on top of your existing inbox subscription.
Why not use Gmail's built-in filters and Smart Reply?
Filters are pattern-matching (sender, subject keyword); they can't reason about content. Smart Reply suggests 3 short replies but doesn't classify or take batch action. An agent reads each email, applies your custom taxonomy, drafts contextual replies, and produces a daily digest. Use filters for the truly mechanical cases (auto-archive a specific newsletter), use the agent for everything that requires reading the email.
What's the worst-case failure?
An agent that auto-archives a customer email by misclassifying it as a newsletter, and you don't see it for a week. Mitigations: (1) shadow mode for week 1, no actions, (2) auto-archive only on labels with > 99% accuracy in shadow review, (3) the Triage log surface preserves every email's classification + content forever, so misses are recoverable, (4) a kill switch you can flip if anything looks off.
Can my AI agents help build the agent?
Yes. The template ships agent prompts for the slow parts: the 30-day inbox audit, the label taxonomy, the classification prompt with few-shot examples, the morning digest format, and the weekly override-pattern analysis. The Triage log surface is the canonical record the agent reads to learn what it's doing well and where it's drifting.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →
Used by these teams · 1

Teams that run this template, with their full setup.

Customer supportUse case

A queue that triages itself.

Inbound tickets, KB articles, response patterns: one workspace. Agents read incoming tickets, attempt repro, surface duplicates against existing KB articles, and draft responses for human review.

Open the use case

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.