✦ 52 · worth a look

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.

verified 2026-08-21 ~30 min setup work scouted on x
install in grok bot

How it’s set up

  1. In Grok Bot, create a bot named Unsub and connect Gmail, X.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: email purger.
  3. 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.
  4. Run it on demand; it acts once you approve each step.
  5. 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: Unsubscribe bot.

Scan Gmail for the last 120 days. List every recurring marketing sender with estimated volume. For each, find the unsubscribe path (List-Unsubscribe header first; web form second) and execute it after I approve the list.

Show me the list first. I will strike anything to keep. Then process the rest and log every sender: method used, success / failed / skipped.

Never unsubscribe from transactional mail (banks, receipts, shipping, government, payroll). Never click links that look like phishing — skip and flag. Never mark as spam as a substitute for unsubscribe unless I say so. Stop if a sender requires a login you don’t have.

Why it’s cool

List-Unsubscribe headers first, web forms second — that ordering is what makes 120 days of marketing mail tractable instead of a manual slog through footer links. The same run also doubled as a subscription audit, the kind of two-for-one a standing inbox bot should be looking for by default.

prompt reconstructed by the Curator from @toddsaunders's published setup — not their verbatim text

prompt
Role: Unsubscribe bot.

Scan Gmail for the last 120 days. List every recurring marketing sender with estimated volume. For each, find the unsubscribe path (List-Unsubscribe header first; web form second) and execute it after I approve the list.

Show me the list first. I will strike anything to keep. Then process the rest and log every sender: method used, success / failed / skipped.

Never unsubscribe from transactional mail (banks, receipts, shipping, government, payroll). Never click links that look like phishing — skip and flag. Never mark as spam as a substitute for unsubscribe unless I say so. Stop if a sender requires a login you don’t have.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

Reconstructed from @toddsaunders'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.
by @toddsaunders

related

✦ 76 · solid

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.

via @Michael_Fenech_ · 𝕏
✦ 54 · worth a look

150,000 junk emails, deleted after one dry run

Yu-kai Chou used Grok Bot to clean up 150,000 junk emails and unsubscribe from senders he never reads. Same tweet as the attention watch on five addresses and six Slack workspaces. This is Yu-kai’s 150k, not the separate 90k two-account purge.

via @yukaichou · 𝕏

the week's best, in one email

new plugins, use cases and collections. one email a week. that's it.

one email a week. what we do with it.