Check weekly for missed membership payments and cancellations and draft follow-up emails
Have Claude Code check Stripe and Thrivecart every Monday for missed payments and cancellations, send a report, and save missed-payment emails with each customer's Stripe payment link as Gmail drafts, with membership access changed only after the owner approves.
What the agent did
Source-reported example · as described by Ev Chapman (runs the paid community College of Knowledge; author of Knowledge Work: Rebooted)
The author, who runs a paid community called College of Knowledge, previously did a weekly payments check by hand: checking Thrivecart for cancellations, checking Stripe for missed payments, drafting emails for missed payments and updating Circle access for cancellations. She had Claude Code automate it.
Per the post, every Monday Claude checks for missed payments and cancellations and sends her a report; it drafts the missed-payment emails, finds the Stripe payment link, inserts it into each email and uploads the drafts to Gmail. She approves the cancellations, and Claude then changes those members' access in Circle.
Reported: the author says the weekly payments check now takes her "less than 5 minutes compared to over 30 minutes before." Reported: she says it "was not hard to setup at all. Claude did all the work." No figures on payments recovered, number of members or error rates are given.
Limitations
The post describes this workflow in a short list; it does not show the instructions given to Claude, the report itself, an example draft email or how the Monday run is scheduled. The author approves cancellations before Circle access is changed; the post doesn't say whether she reviews or sends the Gmail drafts herself, though they are uploaded as drafts.
How the report reaches her isn't stated. Membership size and payment volumes aren't stated. The time figure is the author's own estimate, and the post is promotional in part (it closes by promoting her paid AI course and workshop).
Try it in your business
What you'll need
Claude Code (the author uses the VS Code extension with a Claude Max subscription); access to the payment platform (Stripe), checkout platform (Thrivecart), email (Gmail) and community platform (Circle); a way to run the check each Monday; the author's approval step before membership access changes
Beyond connecting Stripe, Thrivecart, Gmail and Circle, the weekly Monday run is a workflow Claude Code built by writing scripts itself, per the author; that is custom code rather than an off-the-shelf app connection or written instructions alone.
The original is a custom-built system. The prompt below is a simpler starting point and won’t reproduce it.
Starting prompt
The author didn't publish their prompt (the post describes the workflow's steps but does not publish the instructions or scripts behind it; it quotes only the short request "check the payments", which relies on her stored CLAUDE.md context, and a general directory-setup example prompt, neither of which is the workflow's prompt; checked the full post and the publication's About page 2026-10-18), so this is our adaptation.
How ours differs from the original setup: Same Claude Code execution agent with the same connected tools. Written as a single on-request check rather than a scheduled script; keeps emails as unsent drafts and lists access changes for approval instead of making them, so nothing is sent, changed or deleted without the owner's OK.
Run my weekly membership payments check. Using the connected tools, look in [checkout platform, e.g. Thrivecart] for cancellations and in Stripe for missed or overdue payments since [last check date]. Give me a report listing each member affected, what happened, the amount and date. For each missed payment, find that customer's Stripe payment link and write a short, friendly email draft in Gmail that includes the link, using [my email tone notes]. Save these as drafts only; do not send anything. For each cancellation, list the change you would make to the member's access in [community platform, e.g. Circle] and wait for my approval before changing it. Don't cancel subscriptions, issue refunds, delete members or contact anyone yourself.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Create and send monthly client invoices and check last month's payments, with your checks before invoices are created and before they're marked paid
Have Claude Code run a skill that drafts your monthly client invoices from your time reports and calendar, creates them in Xero, emails them from Gmail and checks last month's payments, pausing for your check before invoices are created and before they are marked paid.
Author's original prompt
You'll need: Claude Code; a Claude skill describing your monthly invoicing steps; access from Claude Code to your time tracker (Toggl), accounting software (Xero), calendar (Google Calendar), email (Gmail) and a notes app for the task list (Obsidian); your client rates and invoicing rules; your own review at the skill's checkpoints (after the time reports, before invoices are created in Xero, and before invoices are marked paid); the post states no check right before invoices are emailed, so our suggested prompt adds one
Hey Claude, I'm a freelancer and I have to send invoices every month and also verify that my past month's invoices were paid. Could you help me make a skill to do this?
Draft late invoice reminder emails every Monday for your approval
Have Claude Cowork set up a Monday-night agent that drafts late-invoice reminder emails for you to review and send, as the author describes.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; access to your list of overdue invoices (the post does not say how); a Google Sheet of customer names and contact names; your own reminder email template; access to your mailbox so drafts can be saved; your own review before anything is sent.
Every Monday evening, open [my receivables or invoice system] and list invoices that are past due. Match each customer against my Google Sheet [name] (customer name, contact name). For each match, draft a late-invoice reminder from my template [paste template], using the contact name and each overdue invoice's number, amount and due date. Save the drafts in my Drafts folder. Do not send any email. Then give me a short report: customers included, amount owed per customer and the total, plus any overdue customer who is not in my Sheet and anything you could not read. Do not change or mark anything in the invoice system; I review and send the drafts myself.
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.

