A Family Budget Run by a Team of Single-Job Grok Bots: Bank Downloads, Store Order Matching, Categories and Only One Bot Allowed to Write to YNAB
- Level Advanced
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What they did
A user split their family's budgeting into separate Grok Bots that each do one job. One pulls card and bank transactions through read-only Plaid connections and stages them as JSON. Others keep 30-day order histories from Walmart, Amazon and other stores and match refunds and split shipments. Another assigns categories and splits the confident ones, and once a week posts cards in Slack for the family to settle the unclear ones. Only one bot can write to YNAB, through a small CLI. The bots are defined in a private GitHub repo, re-save themselves when it changes and back up their data to Google Drive. They say it saves their family many hours of manual work a week.
How it went
X post by the builder (Oct 30, 2026 UTC, small account): read-only Plaid download bot, per-store 30-day order history bots, categorize-and-split bot with weekly Slack reaction cards, single write bot via a Python CLI for YNAB; bots defined in a private GitHub repo, re-save on new commits, scheduled backups to Google Drive; 'many hours of manual work per week' saved (their estimate, no exact number)
Worth knowing
- X post by the builder (Oct 30, 2026 UTC, small account): read-only Plaid download bot, per-store 30-day order history bots, categorize-and-split bot with weekly Slack reaction cards, single write bot via a Python CLI for YNAB; bots defined in a private GitHub repo, re-save on new commits, scheduled backups to Google Drive; 'many hours of manual work per week' saved (their estimate, no exact number).
Prompt
Cleaned version rewritten from the source — not a direct quote.
Help me design a small team of bots to categorize my family's transactions in [budget app]. Give each bot one job: (1) download card and bank transactions read-only from [source] into a fixed JSON format, (2) keep 30 days of order history from [stores] and match orders, split shipments and refunds to transactions, (3) categorize and split the transactions it's confident about, and once a week post the unclear ones to [Slack channel] for us to decide, (4) the only bot allowed to write to [budget app]. No other bot gets write access or credentials. Back up each bot's data to [storage] on a schedule. Start by showing me the JSON format and the rules for 'confident' before building anything.
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (Google Drive, Slack, GitHub) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in Claude, ChatGPT Agent, OpenClaw.
Set it up
Tools: Google Drive, Slack, GitHub · Stack: Grok Bot
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
X post by the builder (Oct 30, 2026 UTC, small account): read-only Plaid download bot, per-store 30-day order history bots, categorize-and-split bot with weekly Slack reaction cards, single write bot via a Python CLI for YNAB; bots defined in a private GitHub repo, re-save on new commits, scheduled backups to Google Drive; 'many hours of manual work per week' saved (their estimate, no exact number)
Source: X · 2026-10-30 · Verified by us: not yet · Report broken or outdated