Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

QuickBooks Online (Sandbox)

QuickBooks Online (Sandbox) integration for Flows360 workflows.

CategoryOther
AuthenticationOAuth 2.0
Version0.2.0
Published scopes1 published scope
Last updatedSeptember 23, 2026

Overview

Connect QuickBooks Online (Sandbox) with Flows360

QuickBooks Online (Sandbox) integration for Flows360 workflows.

Use the QuickBooks Online (Sandbox) connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 13 actions and 8 triggers.

Available actions

  • Find Invoice
  • Find Customer
  • Find Payment
  • Create Invoice
  • Create Expense
  • Create Bill
  • Create Vendor
  • Find Vendor
  • Plus 5 additional declared actions.

Available triggers

  • New Invoice
  • New Expense (Purchase)
  • New Customer
  • New Deposit
  • New Transfer
  • New or Updated Invoice
  • Plus 2 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: QuickBooks Online (Sandbox)
  • Package: @activepieces/piece-quickbooks-sandbox@0.2.0
  • Exact artifact digest: sha256:9505b3067591ac0da4e2db119b33f3f18a5a125f511ce5d73325e3d1bf7d9cda
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Find Invoice (find_invoice), Search for an invoice by its number in QuickBooks. Classification: read.
  • Find Customer (find_customer), Search for a customer by display name in QuickBooks. Classification: read.
  • Find Payment (find_payment), Finds an existing payment in QuickBooks. Classification: read.
  • Create Invoice (create_invoice), Creates an invoice in QuickBooks. Classification: read.
  • Create Expense (create_expense), Creates an expense transaction (purchase) in QuickBooks. Classification: read.
  • Create Bill (create_bill), Creates a bill (accounts payable) in QuickBooks. Classification: read.
  • Create Vendor (create_vendor), Creates a vendor in QuickBooks. Classification: read.
  • Find Vendor (find_vendor), Search for a vendor in QuickBooks by display name, email address, or account number. Classification: read.
  • Find Account (find_account), List or search the chart of accounts to get an account Id (e.g. an expense account for a bill). Classification: read.
  • Record Payment (record_payment), Records a customer payment in QuickBooks, optionally applying it to invoices. Classification: read.
  • Record Bill Payment (AP) (record_bill_payment), Pays one or more vendor bills in QuickBooks, in full or in part, by check or credit card. Classification: read.
  • Read AR/AP Aging (read_aging_report), Reads an accounts receivable or accounts payable aging report from QuickBooks. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Invoice, polling.
  • New Expense (Purchase), polling.
  • New Customer, polling.
  • New Deposit, polling.
  • New Transfer, polling.
  • New or Updated Invoice, polling.
  • Payment Received, polling.
  • New Bill, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects21
Supported actionsNot published
Triggers8

Authentication

Authentication method: OAuth 2.0

Required scopes

com.intuit.quickbooks.accounting

Authentication profiles

connection · oauth2

OAuth scopes: com.intuit.quickbooks.accounting

Supported objects

ObjectReadWriteNotes
Find Invoice Yes No Search for an invoice by its number in QuickBooks.
Find Customer Yes No Search for a customer by display name in QuickBooks.
Find Payment Yes No Finds an existing payment in QuickBooks.
Create Invoice Yes No Creates an invoice in QuickBooks.
Create Expense Yes No Creates an expense transaction (purchase) in QuickBooks.
Create Bill Yes No Creates a bill (accounts payable) in QuickBooks.
Create Vendor Yes No Creates a vendor in QuickBooks.
Find Vendor Yes No Search for a vendor in QuickBooks by display name, email address, or account number.
Find Account Yes No List or search the chart of accounts to get an account Id (e.g. an expense account for a bill).
Record Payment Yes No Records a customer payment in QuickBooks, optionally applying it to invoices.
Record Bill Payment (AP) Yes No Pays one or more vendor bills in QuickBooks, in full or in part, by check or credit card.
Read AR/AP Aging Yes No Reads an accounts receivable or accounts payable aging report from QuickBooks.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Invoice Yes No polling trigger declared by the pinned package.
New Expense (Purchase) Yes No polling trigger declared by the pinned package.
New Customer Yes No polling trigger declared by the pinned package.
New Deposit Yes No polling trigger declared by the pinned package.
New Transfer Yes No polling trigger declared by the pinned package.
New or Updated Invoice Yes No polling trigger declared by the pinned package.
Payment Received Yes No polling trigger declared by the pinned package.
New Bill Yes No polling trigger declared by the pinned package.

Triggers

New Invoice · Poll

Triggers when an invoice is created .

New Expense (Purchase) · Poll

Triggers when an Expense (Purchase) is created.

New Customer · Poll

Triggers when a new customer is created.

New Deposit · Poll

Triggers when a Deposit is created.

New Transfer · Poll

Triggers when a Transfer is created.

New or Updated Invoice · Poll

Triggers when an invoice is created or updated in QuickBooks.

Payment Received · Poll

Triggers when a new customer payment is recorded in QuickBooks.

New Bill · Poll

Triggers when a new bill (accounts payable) is created in QuickBooks.

Setup

Setup

  1. Add the QuickBooks Online (Sandbox) connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Company ID (companyId), required.

OAuth scopes

  • com.intuit.quickbooks.accounting
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-quickbooks-sandbox@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 13 actions and 8 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required QuickBooks Online (Sandbox) connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-quickbooks-sandbox@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com