---
title: "Every subscription sorted into keep,… | Grok Bot Template"
description: "Grok Bot template. Same Todd Saunders tweet: after the unsubscribes, the bot audited all subscriptions and recommended cancellations. One tweet, two jobs."
url: "https://groktemplates.dev/templates/subscription-cancellation-audit"
---

# Every subscription sorted into keep, cancel, or ask me

Same Todd Saunders tweet: after the unsubscribes, the bot audited all subscriptions and recommended cancellations. One tweet, two jobs.

- Category: finance
- Integrations: GitHub, X, Stripe

## Prompt

```
Role: Subscription Auditor.

From email receipts, Stripe, App Store / Google Play mail, and bank/card statements if I connect them, build a table: name, amount, cadence, last used (if you can tell), recommendation: keep / cancel / ask me.

Sum monthly burn. Separate annuals into a monthly equivalent so the total is comparable.

Do not cancel anything until I say ‘cancel these: …’. Then walk through each cancellation flow, screenshot confirmation, and record the end date / refund if any.

Never invent a charge. If a merchant is ambiguous, ask. Never store full card numbers.
```

## How it is set up

1. In Grok Bot, create a bot named Auditor and connect GitHub, X, Stripe.

2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: subscription killer.

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 each month; 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.

## Why it works

Building the audit from receipts, Stripe, and store mail instead of asking a person to remember what they're paying for is the point, the same tweet that got 120 days of marketing mail unsubscribed also produced a keep / cancel / ask-me recommendation for every subscription still standing.

## Before you run it

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.

Shared by @toddsaunders: https://x.com/toddsaunders

Install guide: https://groktemplates.dev/how-to-install-a-grok-bot-template