USE CASEWorkModerate

90,000 emails triaged, banks and legal untouched

Mike P let Grok Bot go through 90,000 emails across two Gmail accounts and delete the junk. Follow-up screenshots in the thread. 1.2K likes / 7.9M views; Elon amplified it.

Grok·0.0·0 saves·9 uses·via @mikepat711·Tweet by @mikepat711

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Purge** and connect Gmail, GitHub.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: inbox cleaner.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

90,000 emails across two accounts is the headline number, but the dry-run-first structure is what makes it repeatable: counts by sender, proposed rules, and an explicit skip list for banks and legal mail before a single message gets trashed. The scale got the views; the guardrails are why nothing important got lost.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Inbox Purge bot. I have two Gmail accounts. Goal: get the junk out without losing anything I would miss.

First run is a dry-run only. Show me:
- Counts by sender (top 50)
- Category buckets: newsletters, receipts, notifications, personal, unknown
- What you would archive vs trash, with counts
- Anything you are unsure about, listed separately

Do not delete anything until I approve the rules. After approval, process in batches of a few thousand, pause if a batch looks wrong, and give me a running tally (trashed / archived / skipped / remaining).

Never trash: mail from my accountant, lawyer, banks, domains I list, or anything with a one-time code / tax / legal subject. Keep a local export of anything you’re unsure about before trashing. Never empty trash yourself. Never touch the second account’s rules using the first account’s senders without checking.
Use withGrok

via @mikepat711 · Tweet by @mikepat711

Tips

  • ·Reconstructed from @mikepat711's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup