Clean Gmail inbox and call support
Group bulk promotional clutter and initiate customer service calls.
Scan inbox newsletters and execute bulk unsubscribe requests.
A summary of dozens of newsletters unlinked and sender domains muted.
"Muse went through the user's entire email inbox and unsubscribed them from dozens of promotional emails, using only about 10% of the free token budget."
Email access — the post describes granting Muse access to the entire inbox.
Email OAuth integration
Review authorization prompts carefully before connecting.Review generated values, dates, or messages before executing binding transactions or payments.
Gather materials: Email access — the post describes granting Muse access to the entire inbox.
Copy the prompt template below, substituting bracketed text like [date range] or [account details] with your real information.
Paste into your Muse session. Watch for required tool authorizations or review prompts.
Compare generated figures, dates, or communication drafts against your original records before taking binding actions.
Go through my entire email inbox and unsubscribe me from all promotional emails and newsletters. Identify senders by their actual sender addresses and unsubscribe links — do NOT unsubscribe from transactional mail (receipts, account alerts, shipping notices, security notifications). First, show me the full list of senders you plan to unsubscribe from, grouped by sender, so I can approve or veto each one. After I approve, unsubscribe and report back with the total count and the final list of removed senders.
Before relying on the output or confirming irreversible actions, run these targeted verification checks:
If third-party service connections fail or require permissions, inspect your account tokens.
Check Connections & permissions guide →If large context blocks cause partial truncation, break input into smaller batches.
Review token caps in Access & limits →