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.
plug your Grok Bot in
closeinstall this
6,000 emails gone and 40 lists unsubscribed
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.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Sweep and connect Gmail, X.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: inbox cleaner.
- Give 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.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
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.Why it’s cool
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 reconstructed by the Curator from @royce_james's published setup — not their verbatim text
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.Copy the prompt and paste it into Grok.
what you need
related
One prompt that gives your Grok Bot its own email inbox and identity
Adi Singh's AgentMail guide, turned into a single prompt you paste into your Grok Bot. The bot explains why it shouldn't use your personal Gmail, walks you step by step through installing the AgentMail plugin and tells you exactly what to do on your end, then creates its own inbox and proves it works by emailing you.
Give the bot its own email, act from a CC
Michael Fenech gave his Grok Bot its own email address (via AgentMail), with a webhook that wakes it on each message. He CCs the bot and puts the instruction on the last line — 'Book Tuesday at 3pm and get back to them' — and it reads the thread, books the calendar, and replies to everyone from its own address.
120 days of marketing mail, unsubscribed in one run
Todd had Grok Bot unsubscribe him from 120 days of marketing mail. Same tweet also audited paid subscriptions. 2.1K likes / 422K views.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list