a stripe bot that reads billing before money moves

what a bot can do in Stripe

the first seven only read. the last one makes a refund, so leave it off any bot that only reads.

composio, the connection service dusk bot uses for apps, lists 435 Stripe actions (catalog version 20261101_00, read 12 november 2026⁴). dusk bot treats 206 of them as reads, 64 as sends and the other 165 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like add lines to invoice: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Stripe

1. open Connected apps in the sidebar.
2. pick Stripe and sign in on Stripe's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Stripe.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

connect stripe under Connected apps and enable a billing bot with read-only access first. stripe handles the sign-in. for any later refund work, allow only the actions needed and keep the bot on Ask every time for sends. do not give it a daily amount to send on its own for these routines. and don't put a stripe bot on Full access: with no sending rule of its own, a full-access bot may send up to 25 a day without asking, and here a send moves money.²

routines to copy

these messages keep money movement out of scheduled work. they answer different billing questions and return evidence for a person to review.

every monday at 8, read stripe invoices that are open and past their due date. list the customer, invoice reference, amount, currency and due date. group by currency. do not send invoices, contact customers or change records.

every friday at 3, list stripe refunds created this week and read their related charges. show each refund reference, amount, currency and charge reference. flag anything you cannot match. do not create another refund or move money.

on the first weekday of each month at 10, inspect the stripe subscription records for the customers i named here. summarise their recorded status and billing dates. flag missing context before suggesting any next step. do not cancel, update or charge anything.

what it asks you first

most stripe actions that move money, like a refund, a charge, a transfer or paying an invoice, count as sends: with Ask every time they wait for your Allow. some don't: Confirm payment intent, Capture payment intent, Create Credit Note, Create subscription, Cancel subscription, Finalize an invoice and Void an invoice are ordinary changes that don't ask. keep every billing bot read only, and if one ever needs to refund, give it an exact action list with only Create Refund on it. check the customer, charge, currency and amount before choosing Allow.

a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so set Ask every time for it.²

what it cannot do

• create a refund or alter billing records with read-only access. that boundary is checked before the app call reaches stripe.
• add invoices up into a full accounting picture. the routines list what they find; keep currencies apart and check anything that doesn't match.
• complete a local billing check while the computer is asleep. if an early report needs to be ready before you start work, run that reader on dusk cloud or another always-on machine.

keep collection separate from review

an overdue list is a starting point for invoice follow-up, not an instruction to contact every customer. a payment may need context you have not given the bot. review the references and amounts before drafting a message or approving a money operation.

choose where billing summaries land

keep the first reports in dusk chat. if you later want a google sheets summary, connect it separately and define the destination range. do not turn a reporting job into a subscription-editing job. for a founder briefing, ask for the billing questions that need a decision rather than an unsupported revenue forecast.