QuickBooks Online
Accounting
Cloud accounting (invoices, bills, customers, payments). Ruby can answer questions across your books.
Ask Ruby
3 read tools
Ruby reads from QuickBooks Online and grounds her answers in your data. Every connection starts read-only: she surfaces, summarizes, and drafts, and your team takes the action.
Query
Run a QuickBooks Online SQL-like read query across any entity (Invoice, Customer, Bill, Payment, Vendor, Account, Item, JournalEntry, etc.). Supports SELECT with WHERE / ORDER BY / STARTPOSITION / MAXRESULTS, and COUNT(*). Example: SELECT * FROM Invoice WHERE TxnDate >= '2024-01-01' ORDER BY TxnDate DESC MAXRESULTS 50.
Read entity
Fetch a single QuickBooks Online object by id, e.g. an Invoice, Customer, Bill, Payment, Vendor, or Account. Use quickbooks_query first to find the id when you only have a name. (GET /v3/company/{realmId}/{entity}/{id}).
Company info
Get the connected QuickBooks Online company profile (legal name, address, fiscal year start, currency). Useful for grounding answers and confirming the connection. (GET /v3/company/{realmId}/companyinfo/{realmId}).
1 write tools, off by default
Let Ruby create and update records in QuickBooks, not just read them. This is your accounting system, so read the list below carefully.
An admin switches a connection to read-write in Settings > Integrations. From then on every write waits for a human’s approval before it leaves, by default, and every one lands in your audit log with what changed.
Upsert entity
Create or update a QuickBooks Online record. Omit `id` to create. To UPDATE, you must first read the record with quickbooks_read_entity and pass back its current `id` AND `sync_token`, plus EVERY field you want to keep: QuickBooks replaces the whole object, so any field you leave out is cleared. Supported entities: bill, customer, estimate, invoice, item, purchaseorder, salesreceipt, vendor. The chart of accounts, company preferences, tax settings, and payments are deliberately not writable here.
Built for restoration, not bolted on.
Grounded answers
Ruby reads QuickBooks Online live and cites what she found, so answers reflect your actual data, not a stale export.
Reads by default
Every connection starts read-only. Ruby surfaces and drafts while your team takes the action; writes are opt-in per connection, human-approved by default, and always logged.
Managed, secure auth
Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.
Knows restoration
Ruby understands jobs, claims, drying logs, and AR, so QuickBooks Online data lands in the right operational context.
Connect once, then just ask.
Connect QuickBooks Online once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.
Ruby
Ask in the Ruby app and get an answer grounded in QuickBooks Online and the rest of your connected stack.
Claude
Bring the same secure QuickBooks Online connection into Claude so it can answer with your live data.
ChatGPT
Use QuickBooks Online from ChatGPT with the same per-company, permissioned access Ruby uses.
Frequently asked questions
Do I need developer credentials to connect QuickBooks Online?
No. QuickBooks Online connects with a single click, Ruby handles the OAuth handshake and token refresh for you.
Can Ruby change anything in QuickBooks Online?
Not unless you turn it on. Every QuickBooks Online connection starts read-only. An admin can switch a connection to read-write in Settings > Integrations; from then on each write Ruby makes waits for a human's approval before it leaves (by default; the same admin can switch that off) and is recorded in your audit log either way.
Is my QuickBooks Online data secure?
Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.
Can I use QuickBooks Online alongside my other tools?
Yes. Ruby reasons across every tool you connect at once, so she can tie QuickBooks Online to your CRM, accounting, email, and documentation in a single answer.
