QuickBooks Query (QBO QL): QuickBooks action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Company ID (Realm ID) realm_id	string	Required	Company ID (Realm ID). Example: 123456789
Query query	string	Required	QuickBooks query language (similar to SQL)

Sample request

{
  "realm_id": "e.g. 123456789",
  "query": "e.g. SELECT * FROM Customer WHERE DisplayName LIKE '%Acme%' MAXRESULTS 25"
}

Returns

{
  "QueryResponse": {
    "Customer": [
      {
        "Id": "1",
        "DisplayName": "Acme Inc",
        "PrimaryEmailAddr": {
          "Address": "billing@acme.com"
        }
      }
    ],
    "totalCount": 1
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about QuickBooks Query (QBO QL).

What does the QuickBooks Query (QBO QL) action do in QuickBooks?

Power-user escape hatch — full QBO Query Language against any entity. For complex reports that don't have a typed action (aging summaries, P&L line pulls, custom filtering).

What inputs does QuickBooks Query (QBO QL) require?

Required: Company ID (Realm ID), Query. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if QuickBooks returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does QuickBooks Query (QBO QL) support batch operations?

Yes. Run QuickBooks Query (QBO QL) inside a Loop node to process arrays. Tiny Command handles QuickBooks's rate limits automatically so you don't have to throttle manually.

More actions