Categorise card spend without the month-end scramble
A categorised transaction list plus a short list of the entries that genuinely need a human. Built for a finance lead reconciling a month of transactions from memory.
Stripe
Google Sheets
5 steps2 integrationsRuns monthly
Descriptions mean nothing a month later. What it costs while the work is still done by hand.
- 01Descriptions are cryptic and mean nothing a month later.
- 02The same vendor gets filed three different ways.
- 03Categorisation happens once a month, badly.
- Pull charges214 · last 30 days
- Group vendors38 vendors · category each
- Flag unknown9 rows · no known pattern
- Review214 categorised · 9 flagged
- Write to sheetadd_worksheet · 214 written
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull recent transactions.Stripe
- 02Group them by vendor and propose a category for each.ModuleX
- 03Flag the ones that do not match a known pattern.ModuleX
- 04Review the proposed categories and the flagged rows.ModuleX
- 05Write the categorised rows to your sheet.Google Sheets
The workflow is an editable graph. Reading runs freely; review the proposed categories and the flagged rows waits for your opt-in approval until you loosen it. The graph is the receipt.
Categorised as you go. Paste this into ModuleX chat, or hit Use this workflow.
categorise card spend without the month-end scramble: pull recent transactions; group them by vendor and propose a category for each; flag the ones that do not match a known pattern; review the proposed categories and the flagged rows. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Categorise card spend without the month-end scramble. A categorised transaction list plus a short list of the entries that genuinely need a human.
- stripe · list_charges
- google sheets · add_rows
A categorised transaction list plus a short list of the entries that genuinely need a human.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Assemble the month-end close digestA month-end digest in a consistent shape, assembled from the systems of record. Built for a finance team that rebuilds the same summary every month by hand.- Reconcile payouts against your ledgerA reconciliation summary that names the specific rows to look at, not just a total that is off. Built for whoever matches the payment processor to the accounting sheet each week.
Route a purchase request to the right approverA request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.
About this use case.
No. It reads transactions and writes to a sheet.