Grok Bot + QuickBooks Online

How a Bot connects

OAuth via connector, authorised once from a trusted device as the Bot's Intuit user. No browser logins (2FA loop). See the 2FA fix.

The Bot's identity

An additional QuickBooks user with a limited role: AP-only for invoice routines, reports-only for reporting routines. Don't reuse a human's login. If you did, see shared computer cleanup.

Routines we've run

• Daily 06:00 — read the invoices@ inbox, extract vendor, amount, due date, match to open POs or recent bills, create draft bills for approval
• Weekly — aged receivables: list overdue invoices, draft reminder emails per customer tone rules, queue for approval
• Monthly — close checklist: uncategorised transactions, missing receipts, duplicate vendors, into a review doc

Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.

The thing to gate

Paying anything. A Bot never has payment rights. Bill creation is a draft; payment is a human in QuickBooks.

Verdict

The best-value finance integration for a small company. AP triage alone typically saves 3–5 hours a week and the risk is contained if the Bot can't pay.

Setup notes

• Test every routine supervised until it's produced the right output three times.
• Add the routine's completion line to your heartbeat log so silent failures show up.
• Put the QuickBooks Online token in the Bot's connector settings or knowledge file, never in a chat message.