Grok BotPlaybooksPlan a workflow
← All playbooks
Bills & subscriptions / User-supplied report

Build a subscription review before canceling anything

Find recurring charges and create a decision list with renewal dates and consequences.

Grok BotBeginnerOriginal editorial guide

What you’ll produce

An inventory of possible subscriptions with evidence, renewal details, and an owner decision column.

Inputs & connections

  • Redacted recent statements or approved billing exports
  • Known subscriptions and services you want to keep

Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.

Your starting prompt

Replace the bracketed fields. This is our suggested prompt, not a quote from the source.

Review [billing exports] for possible subscriptions. Group repeated merchants, preserve source rows, and distinguish confirmed recurring charges from guesses. List amount, frequency, latest charge, known renewal date, and what needs checking. Create keep, investigate, and possible-cancel columns without making the decision for me. Do not log in, send cancellation requests, or change services without separate approval.
Open Grok Bot ↗

How to run it

  1. 01

    Use a small set of redacted statements and retain unchanged originals.

  2. 02

    Match recurring merchant patterns to actual service accounts.

  3. 03

    Check renewal, cancellation, refund, and business-dependency details.

  4. 04

    Decide service by service and verify any later cancellation confirmation.

KEEP A PERSON IN THE LOOP

Review before you act

Confirm the service owner, renewal terms, shared users, and whether cancellation removes data or access.

Limitations & success checks

  • Merchant names do not always identify the service correctly.
  • A recurring charge can be necessary or shared; low usage is not proof it should be canceled.

Measure: Subscriptions correctly identified, uncertain charges resolved, and confirmed decisions.

Sources & attribution

The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.

User-supplied reportWeekend bot wins supplied by the site owner

The pasted report mentions bill, shopping, subscription, expense, and travel tasks. Original author, date, and post URL are unverified; no savings are treated as established results.

Official documentationGrok Bot overview ↗

Official overview of the bot environment, browser, files, connectors, and approvals. It does not validate the reported savings in the supplied anecdote.

Creator / publisher: xAI

Editorial review: 2026-10-11. How we label evidence.

FROM A USE CASE TO A WORKING SYSTEM

Have a workflow worth building?

Ferociter plans and builds AI workflows for hospitality and commercial real estate teams.

Talk through your project ↗