19 Grok Bots ran AR/AP, QuickBooks vendor orders and quotes — author reports work of 10+ employees; recent platform limits broke key workflows
CasterHQX (Twitter) · 2026-11-10
Read original@elonmusk I built 19 Grokbot agents to handle work that would otherwise take roughly 10+ employees at CasterHQ, my U.S. caster, wheel and material handling business. It changed how I run my company. Over the past week, several workflows we relied on have stopped working. These agents handle AR/AP, vendor orders through QuickBooks, customer quotes, order tracking, follow-ups, emails, and website updates. This is real business automation being used every day for one of the largest businesses in our field. After recent updates, Grokbot says it can no longer send vendor purchase orders through QuickBooks. Browser access now all of the sudden gets blocked when a connector exists, even when that connector doesn't support the task. Other website workflows have become more restrictive, and the agents seem to lose context sooner and stop troubleshooting much earlier. Your AI support rep, Sammy, reviewed my conversation ID, attributed the issues to platform restrictions on the grok bot side, and escalated a ticket. I'm still waiting for a human response... I made staffing and operating decisions around what these agents could reliably do just a couple of weeks ago. When those capabilities disappear, it affects actual orders, customers, and daily operations. I want to keep building with Grokbot. I'd be happy to show your team all 19 agents, what they accomplished, how many thousands of tasks are performed daily, and exactly where things are now breaking. CasterHQ could be a strong real-world case study for what this technology can do for American small businesses. Can you get this in front of someone who can investigate what changed and help restore these previous working workflows? I have the conversation ID and specific examples ready. I have been so optimistic about continuing to automate my business and workflows and now it feels very discouraging due to the recent hiccups and restrictions on its capabilities.
Business model
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)
Adaptation plan
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.
Prompt
AgentFlow draft · Untested.
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.Running 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. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.