Connect Claude to QuickBooks Online

Return the company this connection is pointed at: its legal and trading name, address, country, fiscal year start, industry and the currencies it is set up for. Intuit's route repeats the realm id inside the path, which is its own shape rather than a mistake here. This is the connection test - it needs nothing, costs nothing, names no customer, and it is the one call that proves the sign-in and the realm id resolve to a company file this grant can read.

Return the chart of accounts: every account with its name, number, type, sub-type, classification and current balance. This is the company's accounting structure rather than anybody's data, so its response is kept in the audit log - an agent reasoning about where a figure came from needs the account list in front of it. The statement behind this is fixed and returns the first 100 accounts; for a filtered or paged version, use run_query with your own SELECT.

Return the first 100 invoices in the company, with the customer each one is for, its amount, its balance still due and its line items. QuickBooks has no REST listing route, so this is the query endpoint with a statement this connector fixed - the caller cannot change it, which is what keeps this a read while run_query is a write. For a date range, a status filter, ordering or paging past the first 100, use run_query with your own SELECT. Its response is kept out of the audit log because an invoice names a real customer and what they were charged.

Fetch one invoice by its QuickBooks id, with its full line items, the customer reference, the terms, the due date and the balance outstanding. Ids come from list_invoices or from run_query. Its response is kept out of the audit log - it names a customer and the amounts between you.

Return the first 100 bills - what suppliers have invoiced this company - with the vendor, the amount, the due date, the balance outstanding and the expense lines. Like the other listings here this is the query endpoint with a fixed statement; use run_query for a filtered, ordered or paged version. Kept out of the audit log because a bill names a real supplier and what is owed to them.

Return the first 100 vendors - the suppliers this company buys from - with their display names, contact details, addresses, terms and open balances. Use it to turn a supplier name into the vendor id a bill references. Fixed statement, as with the other listings; use run_query to filter or page. Kept out of the audit log because it is a list of real counterparties and their contact details.

Fetch one customer by their QuickBooks id, with their display name, contact details, billing and shipping addresses, payment terms, tax settings and current balance. Ids come from an invoice's CustomerRef, or from run_query with a SELECT over Customer. Its response is kept out of the audit log - it is one named person or company and their details.

Run a QuickBooks query statement and return the matching records. This is the general read for anything the fixed listings above do not cover: filters, date ranges, ordering, paging past the first 100, and every entity this connector exposes no operation for. IT REACHES FURTHER THAN THE OTHER READS. One free-text statement gets at every entity in the company file, employees, payroll items and time activities included, so a workspace that wants an agent held to the named listings should exclude this action by name with a selected-action grant rather than rely on the read/write line. It is classified a read because that is what it is: the query language is SELECT only, this is a GET, and creating or editing a record goes through routes this connector does not expose at all. The statement is masked before the call is logged, because a WHERE clause routinely carries a customer's name or email. Syntax notes, because it is not SQL: no JOIN, no GROUP BY, no OR, no column projections - SELECT * or SELECT COUNT(*) only. Paging is STARTPOSITION then MAXRESULTS, in that order, at the end of the statement; MAXRESULTS defaults to 100 and caps at 1000.

Run the Profit and Loss report and return QuickBooks' report structure of columns and rows. Every parameter is optional. Give start_date and end_date as YYYY-MM-DD for an explicit range, or date_macro for a named period such as "Last Fiscal Year" or "This Month-to-date" - if the dates are left out, the macro is what QuickBooks uses. summarize_column_by breaks the report into columns by Month, Quarter, Year, Customers, Vendors, Classes or Departments. accounting_method switches between Cash and Accrual. The response is aggregate figures with no customer or supplier named in it, which is why, unlike the invoice and customer reads here, it is kept in the audit log: a number an agent reported should be checkable afterwards.

Run the Balance Sheet report and return QuickBooks' report structure of columns and rows. Every parameter is optional, and the same date rule applies as on the Profit and Loss: give start_date and end_date, or a date_macro that stands in when they are omitted. A balance sheet is a position rather than a flow, so summarize_column_by is usually left alone or set to a period to compare positions over time. Aggregate figures, no counterparties, so the response is kept in the audit log.