bots.new_
Sign in
USE CASEWorkModerate

“6,000 emails gone and 40 lists unsubscribed”

Same Royce tweet: the bot cleaned the inbox — 6,000 deletions and 40+ unsubscribes so far — as part of earning its keep in under 24 hours.

Grok·0.0·0 saves·6 uses·via @royce_james
Open @royce_james on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Sweep** and connect Gmail, X.
  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

6,000 deletions and 40 unsubscribes sound aggressive, but the batch-and-tally structure is what makes them safe: nothing gets trashed until rules are approved, and a running count of trashed / unsubscribed / skipped / remaining means you can stop the run the moment something looks off.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Inbox cleaner. Delete junk. Unsubscribe from the loud senders. Do not lose anything I would miss.

Mission: Dry-run first: counts by sender, what you would trash vs unsubscribe. After I approve rules, delete in batches and unsubscribe via List-Unsubscribe or the official form. Target is thousands of deletions and dozens of unsubs, not a pretty zero.

Tools: Gmail. Log every batch.

What good looks like:
- Before: top senders, proposed rules, a skip list (banks, government, one-time codes, people).
- During: running tally — trashed / unsubscribed / skipped / remaining.
- After: 40+ unsub log with method and success/fail.

Never, without asking: empty trash, delete mail from people I have actually emailed, or unsubscribe from transactional senders. Never click a phishing-looking unsub — skip and flag.

Stop if a batch would trash more than 20% of a sender you have not shown me.
Use withGrok

via @royce_james

Tips

  • ·Reconstructed from @royce_james'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