# 19 Grok Bots ran AR/AP, QuickBooks vendor orders and quotes — author reports work of 10+ employees; recent platform limits broke key workflows

Grok · X (Twitter) · Amount undisclosed (operations workflow case, not a revenue case; author reports 19 bots doing work of 10+ employees; several workflows broke after recent platform updates and await restoration)

## Business summary

The operator of CasterHQ, a U.S. caster, wheel and material handling business, built 19 Grok Bot agents handling AR/AP, vendor purchase orders through QuickBooks, customer quotes, order tracking, follow-ups, emails and website updates. Author reports these agents perform thousands of tasks daily, equivalent to work previously requiring 10+ employees. The same post reports that several workflows stopped working in the past week after recent updates: vendor PO sending via QuickBooks is blocked, browser access is blocked when a connector exists even if the connector cannot do the task, and agents lose context sooner. Support escalated a ticket and the author is awaiting a human response. Readers can reuse the dedicated-agents-by-function pattern, but should note the post describes the pre-breakage setup and the current interruption; workflow and prompt are AgentFlow reconstructions, untested.

## Business value

The operator of CasterHQ, a U.S. caster, wheel and material handling business, built 19 Grok Bot agents handling AR/AP, vendor purchase orders through QuickBooks, customer quotes, order tracking, follow-ups, emails and website updates. Author reports these agents perform thousands of tasks daily, equivalent to work previously requiring 10+ employees. The same post reports that several workflows stopped working in the past week after recent updates: vendor PO sending via QuickBooks is blocked, browser access is blocked when a connector exists even if the connector cannot do the task, and agents lose context sooner. Support escalated a ticket and the author is awaiting a human response. Readers can reuse the dedicated-agents-by-function pattern, but should note the post describes the pre-breakage setup and the current interruption; workflow and prompt are AgentFlow reconstructions, untested.

## Workflow

Split operations into 19 dedicated bots and connect them to company systems

Bots run daily ops: vendor POs, quotes, tracking, follow-ups, emails, website updates (author-reported; PO sending broke after recent updates)

Humans take over broken flows and escalate to support; ticket filed, awaiting human response

Browser was the backup when no connector could do a task; recently restricted too (author's thread reply)

## Preparation and limitations

Results and numbers are as reported by the original post author (19 agents, 10+ employee equivalent, thousands of tasks/day, workflow breakage). Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. The post does not mention drafts or human confirmation; the freePrompt's confirmation gate is a stricter safety boundary added by AgentFlow. The post is a reply to @elonmusk asking the Grok team to investigate and restore broken workflows.

## Starter prompt

````text
You are a CasterHQ-style operations Grok Bot responsible for.

Input materials (user must supply):
- Company and systems: {{company_name}}, connected systems {{systems}} (e.g. QuickBooks, Gmail, website admin)
- Today’s tasks: {{today_tasks}} (e.g. “create 3 POs for supplier X”, “draft follow-up for customer Y quote”)
- Templates/rules: {{templates_or_rules}}
- Confirmation boundary: Any send email, submit order, modify website or payment-related action must output a draft clearly marked “requires human confirmation before execution”; never auto-send.

Task:
1. Read inputs and check for missing or conflicting information (e.g. missing supplier ID, price mismatch).
2. If information is insufficient, list specific missing items and stop; do not guess.
3. Generate executable drafts (POs, quotes, follow-up emails) according to rules.
4. Output format:
 - Summary (1-2 sentences)
 - Draft body (complete, copyable)
 - List of actions requiring confirmation
 - Missing/conflict notes (if any)

Missing handling: If any key field is missing or data conflicts, output only the issue list; do not produce final draft.
Confirmation boundary: Do not auto-send, pay, or modify external systems; prepare materials and wait for explicit user “confirm execute”.

Untested. Reconstructed from original post description.
````

## Costs and pitfalls

Results and numbers are as reported by the original post author (19 agents, 10+ employee equivalent, thousands of tasks/day, workflow breakage). Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. The post does not mention drafts or human confirmation; the freePrompt's confirmation gate is a stricter safety boundary added by AgentFlow. The post is a reply to @elonmusk asking the Grok team to investigate and restore broken workflows.

## Source and attribution

CasterHQ (@caster_hq)
https://x.com/caster_hq/status/2120023608118399074
2026-11-10
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
