The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 3, 2026 8:00am

PR Summary

Medium Risk
Read-only report calls reuse existing OAuth and caps, but the change expands financial-reporting surface area and report filter handling; incorrect matrix wiring could send wrong parameters to live QuickBooks companies.

Overview
Adds Run Financial Report to the QuickBooks block: 14 fixed reports (balance sheet, P&L, trial balance, cash flow, aging, customer/vendor balance, sales, expenses) with native header, columns, and nested rows in the response. Report-specific advanced controls (dates, cash/accrual basis, summarize-by, entity filters, aging) only appear when QuickBooks supports them for that report type.

Read Master Data now includes Class and Department record types (with SubClass / SubDepartment on outputs) so workflows can discover IDs for report filters.

Block wiring maps UI sub-blocks to tool params via a per-report control matrix; unsupported combinations are omitted before the API call. Docs, integrations.json, block skills, and example workflow prompts are updated toward financial reporting and aging workflows instead of some prior purchase/expense-focused examples.

^{Reviewed by Cursor Bugbot for commit fc1bfdc. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

The PR adds a bounded QuickBooks financial-report operation covering 14 report types and extends master-data discovery with Class and Department.

• Defines a fixed report endpoint and supported-control matrix with date, accounting-basis, summarization, entity-filter, and aging validation.
• Preserves native QuickBooks report headers, columns, nested rows, IDs, and links in workflow outputs.
• Registers the new tool across the QuickBooks block, tool registry, generated metadata, documentation, and tests.
• Adds Class and Department list/by-ID reads so workflows can discover report-filter identifiers.

Confidence Score: 5/5

The PR appears safe to merge after its stated parent branch, with no concrete changed-code failure identified.

The report operation is consistently wired through the block, registry, request builder, response contract, generated metadata, documentation, and tests, while unsupported controls are rejected or discarded before the outbound request.

sequenceDiagram
  participant Workflow
  participant Block as QuickBooks Block
  participant Tool as Financial Report Tool
  participant QBO as QuickBooks Online
  Workflow->>Block: report type and supported controls
  Block->>Block: resolve values, coerce aging days, discard stale controls
  Block->>Tool: normalized report parameters and OAuth credential
  Tool->>Tool: validate support matrix and construct fixed URL
  Tool->>QBO: bounded GET, retries disabled
  QBO-->>Tool: native Header, Columns, Rows
  Tool->>Tool: validate report wrapper
  Tool-->>Workflow: preserved native report output

_{Reviews (1): Last reviewed commit: "feat(quickbooks): expose reports in bloc..." | Re-trigger Greptile}