# Quickbooks Your Toolhouse AI Worker can connect to Quickbooks using 105 specialized tools. ## Auth Connection This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=quickbooks). ## Tools (105) ### `Quickbooks Capture Charge` Integration name: **QUICKBOOKS\_CAPTURE\_CHARGE** Tool to capture funds for an existing charge that was authorized but not captured. Use when you need to complete a previously authorized payment transaction in QuickBooks Payments API. This action finalizes the charge and transfers the funds from the customer's payment method. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `amount` | string | | `"10.00"` | The amount to capture. If not provided, captures the full authorized amount. For partial captures, specify the amount as a decimal string (e.g., '10.55', '25.00'). The amount must not exceed the authorized amount. | | `context` | object | | — | Additional context information for the capture. This is an optional field that can contain merchant-specific metadata or transaction context. | | `charge_id` | string | ✅ | `"EMU123456789"` | The ID of the charge to capture. This is the unique identifier for the authorized charge in QuickBooks Payments (e.g., 'EMU123456789', 'ECH123456789'). Use this to capture funds from a charge that was previously authorized but not captured. | *** ### `Quickbooks Create Account` Integration name: **QUICKBOOKS\_CREATE\_ACCOUNT** Create a new account in QuickBooks with the given parameters. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | — | User recognizable name for the Account. Account.Name attribute must not contain double quotes (") or colon (:). | | `active` | boolean | | — | Whether or not the account is active. Inactive accounts may be hidden from display and cannot be posted to. Default is true if not specified. | | `parent_ref` | object | | — | Reference to another entity. | | `description` | string | | — | User-entered description for the account. May include information to guide bookkeepers in deciding what to post to the account. Maximum length is 100 characters for QuickBooks Online, 200 characters for QuickBooks Desktop. | | `sub_account` | boolean | | — | Specifies whether this is a subaccount. Set to true to create a subaccount. Must also provide parent\_ref when true. | | `account_type` | string | ✅ | — | Type of the account to be created. Required field. Valid values: 'Bank', 'Other Current Asset', 'Fixed Asset', 'Other Asset', 'Accounts Receivable', 'Equity', 'Expense', 'Other Expense', 'Cost of Goods Sold', 'Accounts Payable', 'Credit Card', 'Long Term Liability', 'Other Current Liability', 'Income', 'Other Income'. | | `currency_ref` | object | | — | Reference to another entity. | | `account_number` | string | | — | User-defined account number to help the user in identifying the account within the chart-of-accounts and in deciding what should be posted to the account. must not contain colon (:). For France locales: | | `opening_balance` | number | | — | Opening balance amount when creating a new Balance Sheet account. Used only at account creation for accounts like Bank, Credit Card, etc. | | `account_sub_type` | — | | `"AdvertisingPromotional"` | Sub-type of the account. Must use exact enum values (no spaces/slashes). Examples: 'AdvertisingPromotional' (NOT 'Advertising/Promotional'), 'Checking', 'Inventory', 'OtherCurrentAssets', 'Vehicles', 'RetainedEarnings', 'Insurance', 'InterestEarned'. See QuickBooks API docs for complete list. | | `opening_balance_date` | string | | — | Date of the opening balance. Format: YYYY-MM-DD. Required if opening\_balance is provided. | *** ### `Quickbooks Create Bank Account` Integration name: **QUICKBOOKS\_CREATE\_BANK\_ACCOUNT** Create a new bank account on file for a customer in QuickBooks Payments API. Use this when you need to add ACH/eCheck payment capabilities for a customer. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------ | :------: | -------------------- | ---------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"John Doe"` | Account holder name (full name of the person or business). | | `phone` | string | | `"555-123-4567"` | Phone number associated with the bank account holder. | | `customer_id` | string | ✅ | `"test-customer-id"` | The customer ID for whom to create the bank account. | | `account_type` | string | ✅ | — | Type of bank account. Must be one of: PERSONAL\_CHECKING, PERSONAL\_SAVINGS, BUSINESS\_CHECKING, or BUSINESS\_SAVINGS. | | `account_number` | string | ✅ | `"1234567890"` | Bank account number. | | `routing_number` | string | ✅ | `"021000021"` | Bank routing number (must be valid and pass checksum validation). Use a valid 9-digit ABA routing number. | *** ### `Quickbooks Create Bill` Integration name: **QUICKBOOKS\_CREATE\_BILL** Create a new bill in QuickBooks Online. A Bill is an AP transaction representing a request-for-payment from a third party for goods or services. Use this action when recording vendor bills for purchases, expenses, or services received. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | `Line` | array | ✅ | — | List of line items for the bill. At least one line item is required. Each line must specify DetailType, Amount, and the appropriate detail object. | | `DueDate` | string | | — | Date when payment for the bill is due in YYYY-MM-DD format. | | `TxnDate` | string | | — | Date of the transaction in YYYY-MM-DD format. Defaults to the current date if not provided. | | `DocNumber` | string | | — | Reference number for the bill (e.g., vendor invoice number). | | `VendorRef` | object | ✅ | — | Reference to the vendor from whom the bill is received. Required field. | | `CurrencyRef` | object | | — | Reference to the currency. Format: {'value': 'USD'}. | | `PrivateNote` | string | | — | User-entered private note about the bill. | | `APAccountRef` | object | | — | Reference to the Accounts Payable account. Format: {'value': 'account\_id'}. If not specified, uses the default AP account. | | `ExchangeRate` | number | | — | Currency exchange rate for multi-currency transactions. | | `SalesTermRef` | object | | — | Reference to the payment terms. Format: {'value': 'term\_id'}. Defines when payment is due. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default version. | | `DepartmentRef` | object | | — | Reference to the department. Format: {'value': 'department\_id'}. | | `GlobalTaxCalculation` | string | | — | Method in which tax is applied. Valid values: TaxExcluded, TaxInclusive, NotApplicable. | *** ### `Quickbooks Create Bill Payment` Integration name: **QUICKBOOKS\_CREATE\_BILL\_PAYMENT** Create a bill payment in QuickBooks to record payment against one or more bills. Use when paying vendor bills via check or credit card. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------- | | `Line` | array | ✅ | — | List of line items indicating which bills are being paid and the amounts applied to each. | | `PayType` | string | ✅ | — | Payment method type. Must be either 'Check' or 'CreditCard'. | | `TxnDate` | string | | — | Date of the transaction in YYYY-MM-DD format. Defaults to current date if not specified. | | `TotalAmt` | number | ✅ | — | Total amount of the bill payment. Must be positive and match the sum of all line amounts. | | `VendorRef` | object | ✅ | — | Reference to the vendor receiving the payment. | | `PrivateNote` | string | | — | Private note for internal use, not visible to the vendor. Maximum 4000 characters. | | `CheckPayment` | object | | — | Check payment details for bill payment. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default from headers. | | `DepartmentRef` | object | | — | Reference to the department for location/department tracking. Must be a dict with 'value' key. | | `CreditCardPayment` | object | | — | Credit card payment details for bill payment. | *** ### `Quickbooks Create Class` Integration name: **QUICKBOOKS\_CREATE\_CLASS** Create a new class in QuickBooks Online. Use when you need to categorize transactions by department, location, or other business segments. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------- | :------: | -------------------- | -------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"Department Sales"` | The name of the class. Must be unique and cannot contain a colon (:). | | `Active` | boolean | | — | Whether the class is active. Inactive classes are hidden from most display areas. Default is true. | | `SubClass` | boolean | | — | Whether this is a subclass. If true, ParentRef must be provided. | | `ParentRef` | object | | — | Reference to another entity. | *** ### `Quickbooks Create Credit Memo` Integration name: **QUICKBOOKS\_CREATE\_CREDIT\_MEMO** Tool to create a new credit memo in QuickBooks Online. Use when issuing credit to a customer for returns, refunds, or adjustments. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------- | ------- | :------: | --------------- | ---------------------------------------------------------------------------------------------------------------- | | `line` | array | ✅ | — | Array of line items for the credit memo. At least one line item is required. | | `txn_date` | string | | `"2024-01-15"` | Transaction date in YYYY-MM-DD format. Defaults to current date if not provided. | | `bill_addr` | object | | — | Physical address structure. | | `class_ref` | object | | — | Reference to the class for categorization. Format: {'value': 'class\_id'}. | | `ship_addr` | object | | — | Physical address structure. | | `ship_date` | string | | `"2024-01-15"` | Shipping date in YYYY-MM-DD format. | | `bill_email` | string | | — | Email address to send the credit memo to. Must be a valid email format. | | `doc_number` | string | | — | Reference number for the credit memo (maximum 21 characters). | | `currency_ref` | object | | — | Reference to currency. | | `custom_field` | array | | — | Array of custom fields for the credit memo. | | `customer_ref` | object | ✅ | — | Reference to the customer receiving the credit memo. Required field. | | `email_status` | string | | `"NotSet"` | Email status of the credit memo. Valid values: 'NotSet', 'NeedToSend', 'EmailSent'. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default version from headers. | | `print_status` | string | | `"NotSet"` | Print status of the credit memo. Valid values: 'NotSet', 'NeedToPrint', 'PrintComplete'. | | `private_note` | string | | — | Private note about the credit memo, not visible to the customer. | | `customer_memo` | string | | — | Message to the customer that appears on the credit memo. Maximum 1000 characters. | | `exchange_rate` | number | | — | Exchange rate for currency conversion. | | `department_ref` | object | | — | Reference to the department associated with the credit memo. Format: {'value': 'department\_id'}. | | `sales_term_ref` | object | | — | Reference to the sales term. Format: {'value': 'term\_id'}. | | `ship_method_ref` | object | | — | Reference to the shipping method. Format: {'value': 'ship\_method\_id'}. | | `global_tax_calculation` | string | | `"TaxExcluded"` | Method in which tax is applied. Valid values: 'TaxExcluded', 'TaxInclusive', 'NotApplicable'. | | `apply_tax_after_discount` | boolean | | — | Whether to apply tax after discount. Defaults to false. | *** ### `Quickbooks Create Customer` Integration name: **QUICKBOOKS\_CREATE\_CUSTOMER** Create a new customer in QuickBooks with the given parameters. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Fax` | object | | — | Fax number of the customer. | | `Job` | boolean | | — | Whether this customer record represents a job. Default is false. | | `Notes` | string | | — | Free-form notes or comments about the customer. | | `title` | string | | `"Mr."` | Title of the person (max 16 characters - keep it short like 'Mr.', 'Dr.', 'CEO'). This tag supports i18n, all locales. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes are required during create. | | `Active` | boolean | | — | Whether the customer is currently active. Default is true. | | `Mobile` | object | | — | Mobile phone number of the customer. | | `suffix` | string | | — | Suffix of the name. For example, Jr. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `Balance` | number | | — | Opening balance amount for this customer at the OpenBalanceDate. | | `Taxable` | boolean | | — | Whether the customer is taxable. Default is true. | | `WebAddr` | object | | — | Website address (URI) of the customer. | | `BillAddr` | object | | — | Billing address of the customer. | | `ShipAddr` | object | | — | Shipping address of the customer. | | `ParentRef` | object | | — | Reference to the immediate parent customer for sub-customers. | | `ResaleNum` | string | | — | Resale number or tax-exempt number for the customer. | | `given_name` | string | | — | Given name or first name of a person. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `CompanyName` | string | | — | Company name associated with the customer. | | `CurrencyRef` | object | | — | Reference to the currency used for transactions with this customer (e.g., {'value': 'USD'}). | | `family_name` | string | | — | Family name or the last name of the person. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `middle_name` | string | | — | Middle name of the person. The person can have zero or more middle names. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `PrimaryPhone` | object | | — | Primary phone number of the customer. | | `display_name` | string | | — | The name as displayed. Must be unique across all Customer, Vendor, and Employee objects. Cannot be removed with sparse update. If not supplied, the system generates DisplayName by concatenating customer name components supplied in the request from the following list: Title, GivenName, MiddleName, FamilyName, and Suffix. | | `AlternatePhone` | object | | — | Alternate phone number of the customer. | | `BillWithParent` | boolean | | — | Whether this sub-customer should be billed with its parent customer. Default is false. | | `OpenBalanceDate` | string | | — | Date of the opening balance for the customer in YYYY-MM-DD format. | | `PrimaryEmailAddr` | object | | — | Primary email address of the customer. | | `PrintOnCheckName` | string | | — | Name to be printed on checks issued to this customer. If not provided, DisplayName is used. | | `PreferredDeliveryMethod` | string | | — | Preferred delivery method for invoices and communications. | *** ### `Quickbooks Create Deposit` Integration name: **QUICKBOOKS\_CREATE\_DEPOSIT** Creates a new deposit in QuickBooks Online. A deposit represents funds received and deposited to an asset account (typically a bank account). Use this action to record deposits of customer payments, refunds, or other funds into your bank accounts. Each deposit must specify the destination account and at least one line item showing the source and amount of funds. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------ | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `line` | array | ✅ | — | List of deposit line items. Each line item represents funds being deposited. At least one line is required. Each line must include: (1) 'Amount' as a positive number, (2) 'DetailType' set to 'DepositLineDetail', (3) 'DepositLineDetail' with 'AccountRef' containing the source account ID. Example: \[{'Amount': 100.00, 'DetailType': 'DepositLineDetail', 'DepositLineDetail': {'AccountRef': {'value': '87'}}}] | | `txn_date` | string | | — | Transaction date for the deposit in YYYY-MM-DD format (e.g., '2026-02-23'). If not provided, the current date will be used. | | `currency_ref` | object | | — | Reference to a currency. | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). If not specified, uses the default API version. | | `private_note` | string | | — | Private note about the deposit (internal use only). | | `exchange_rate` | — | | — | Exchange rate for multi-currency transactions. Default is 1 for home currency. | | `department_ref` | object | | — | Reference to a department. | | `deposit_to_account_ref` | object | ✅ | — | Reference to the asset account (bank account) where the deposit will be made. Must be a valid bank account ID. Example: {'value': '35'} for account ID 35. Use QUICKBOOKS\_QUERY\_ACCOUNT or QUICKBOOKS\_READ\_ACCOUNT to get valid account IDs. | *** ### `Quickbooks Create Echeck Payment` Integration name: **QUICKBOOKS\_CREATE\_ECHECK\_PAYMENT** Tool to create an eCheck payment using ACH bank transfer in QuickBooks Payments API. Use when processing payments from customer bank accounts via electronic check. The payment is debited directly from the customer's bank account using the provided routing and account numbers. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | `amount` | string | ✅ | — | Payment amount as a string (e.g., '10.55', '100.00'). Must be a positive number with up to 2 decimal places. | | `context` | object | | — | Transaction context information. | | `currency` | string | ✅ | — | Currency code for the payment (e.g., 'USD'). Currently only USD is supported by QuickBooks Payments. | | `bankAccount` | object | ✅ | — | Bank account details from which the eCheck payment will be debited. Includes account number, routing number, account type, name, and phone. | *** ### `Quickbooks Create Employee` Integration name: **QUICKBOOKS\_CREATE\_EMPLOYEE** Create a new employee in QuickBooks. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `fax` | object | | — | Fax number of the employee. | | `ssn` | string | | — | Social Security Number. Maximum 15 characters for QuickBooks Online, 1024 characters for QuickBooks Desktop. | | `title` | string | | — | Title or honorific of the employee. | | `active` | boolean | | — | Indicates whether the entity is enabled. Default is true. Employees are deactivated (active=false) rather than deleted. | | `gender` | string | | — | Gender of the employee. | | `mobile` | object | | — | Mobile phone number of the employee. | | `suffix` | string | | — | Name suffix of the employee. QuickBooks Online only. Maximum 15 characters. | | `web_addr` | object | | — | Website address or URI associated with the employee. | | `bill_rate` | number | | — | Hourly billing rate for the employee. QuickBooks Online only. | | `cost_rate` | number | | — | Cost rate associated with the employee. | | `birth_date` | string | | — | Birth date of the employee, in YYYY-MM-DD format. | | `given_name` | string | ✅ | — | Given name (first name) of the employee. Required field. Maximum 100 characters. | | `hired_date` | string | | — | Date the employee was hired, in YYYY-MM-DD format. | | `other_addr` | object | | — | Other physical address(es) of the employee. | | `family_name` | string | ✅ | — | Family name (last name) of the employee. Required field. Maximum 100 characters. | | `middle_name` | string | | — | Middle name(s) of the employee. Maximum 5-15 characters depending on product. | | `company_name` | string | | — | Company name associated with the employee. | | `custom_field` | array | | — | Array of custom fields associated with the employee. | | `display_name` | string | | — | Display name of the employee. Must be unique across all customer, employee, and vendor objects. Populated from FullName if not provided. Must not contain colon, tab, or newline characters. | | `organization` | boolean | | — | Internal flag for organizational structure. | | `primary_addr` | object | | — | Physical street address for this employee. If QuickBooks Payroll is enabled for the company, the following address fields are required: city, country\_sub\_division\_code, and postal\_code. | | `billable_time` | boolean | | — | Indicates whether employee time is billable. QuickBooks Online only. | | `employee_type` | string | | — | Employee type classification. | | `primary_phone` | object | | — | Primary phone number of the employee. | | `released_date` | string | | — | Date the employee left the company, in YYYY-MM-DD format. | | `use_time_entry` | boolean | | — | Indicates whether time sheets create paychecks for this employee. | | `alternate_phone` | object | | — | Alternate phone number of the employee. | | `employee_number` | string | | — | Employee directory number. Maximum 15 for QuickBooks Online, 99 for QuickBooks Desktop. | | `other_contact_info` | array | | — | List of additional contact information entities. | | `primary_email_addr` | object | | — | Primary email address of the employee. | | `print_on_check_name` | string | | — | Name as it should appear on printed checks. | | `default_tax_code_ref` | object | | — | Reference to the default tax code associated with the employee. | *** ### `Quickbooks Create Estimate` Integration name: **QUICKBOOKS\_CREATE\_ESTIMATE** Creates a new estimate in QuickBooks Online. An estimate represents a proposal for goods or services that a customer may purchase. Use this to provide pricing quotes to customers before they commit to a purchase. This action requires a valid customer ID and at least one line item with item details and amount. The created estimate can later be converted to an invoice when the customer accepts the proposal. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `lines` | array | ✅ | — | List of estimate line items. Each line item must include DetailType, Amount, and appropriate detail object (e.g., SalesItemLineDetail for item-based lines). | | `txn_date` | string | | — | Date of the estimate transaction in YYYY-MM-DD format (e.g., '2024-01-15'). If not specified, the current date is used. | | `bill_addr` | object | | — | Physical address structure. | | `class_ref` | object | | — | Reference to a class for categorization. | | `ship_addr` | object | | — | Physical address structure. | | `ship_date` | string | | — | Date for delivery of goods or services in YYYY-MM-DD format (e.g., '2024-03-15'). | | `bill_email` | string | | — | Email address where the estimate should be sent. | | `doc_number` | string | | — | Reference number for the estimate. If not specified, QuickBooks generates one automatically. | | `customer_id` | string | ✅ | — | ID of the customer for whom the estimate is created. This is the unique identifier for the customer in QuickBooks (e.g., '1', '3'). Use QUICKBOOKS\_READ\_CUSTOMER or QUICKBOOKS\_CREATE\_CUSTOMER to get valid customer IDs. | | `currency_ref` | object | | — | Reference to a currency. | | `custom_field` | array | | — | Custom fields for the estimate. QuickBooks Online supports up to 3 custom fields. The custom fields must already exist in QuickBooks. | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). If not specified, uses the default API version from headers. | | `private_note` | string | | — | User-entered private note about the estimate, not visible to the customer. Maximum 4000 characters. | | `tracking_num` | string | | — | Shipping provider's tracking number for the delivery of goods. Maximum 31 characters. | | `customer_memo` | string | | — | Message to the customer that appears on the estimate. | | `exchange_rate` | number | | — | The exchange rate for the transaction. Applicable if multi-currency is enabled. Defaults to 1. | | `department_ref` | object | | — | Reference to a department. | | `sales_term_ref` | object | | — | Reference to sales terms. | | `expiration_date` | string | | — | Date by which the estimate must be accepted in YYYY-MM-DD format (e.g., '2024-02-28'). | | `ship_method_ref` | object | | — | Reference to a shipping method. | | `global_tax_calculation` | string | | — | Method in which tax is applied. Valid values: TaxExcluded, TaxInclusive, NotApplicable. Default is TaxExcluded. | | `apply_tax_after_discount` | boolean | | — | If true, tax is applied after discount. If false or null, calculate sales tax first then apply discount. US QuickBooks companies only. Defaults to false. | *** ### `Quickbooks Create Invoice` Integration name: **QUICKBOOKS\_CREATE\_INVOICE** Creates a new invoice in QuickBooks for a customer. An invoice represents a sales transaction where goods or services are sold to a customer on credit or for immediate payment. This action requires: - A valid customer ID (obtain from QUICKBOOKS\_CREATE\_CUSTOMER or QUICKBOOKS\_READ\_CUSTOMER) - At least one line item with a valid item/service ID and amount The created invoice will have a unique ID, document number, due date, total amount, and balance. Use this to bill customers for products or services rendered. To update the invoice later, re-read it first to obtain the current SyncToken; stale tokens cause update rejections. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------------------- | ------- | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `fob` | string | | — | Free On Board (FOB) designation for shipping terms. Defines when ownership and liability transfer from seller to buyer. | | `lines` | array | ✅ | — | List of invoice line items. Each line item must be a dictionary with: (1) 'DetailType' set to 'SalesItemLineDetail', (2) 'Amount' as a number representing the line total, (3) 'SalesItemLineDetail' as a dictionary containing 'ItemRef' with a 'value' key for the item ID (e.g., {'ItemRef': {'value': '1'}}). Optional fields include 'Description' (text), 'Qty' (quantity as number), and 'UnitPrice' (price per unit as number). Example: \[{'DetailType': 'SalesItemLineDetail', 'Amount': 100.00, 'SalesItemLineDetail': {'ItemRef': {'value': '1'}, 'Qty': 2, 'UnitPrice': 50.00}}] | | `due_date` | string | | — | Date when payment for the invoice is due in YYYY-MM-DD format (e.g., '2026-03-25'). Calculated from TxnDate and SalesTermRef if not explicitly provided. | | `txn_date` | string | | — | Date when the transaction occurred in YYYY-MM-DD format (e.g., '2026-02-25'). This is the posting date that affects financial statements. If not supplied, the current server date is used. | | `bill_addr` | object | | — | Bill-to address of the invoice. Provide as a dictionary with keys like 'Line1', 'City', 'CountrySubDivisionCode', 'PostalCode'. If not provided, defaults to the customer's billing address. | | `class_ref` | object | | — | Reference to the class associated with the transaction for categorization and reporting. Provide as a dictionary with 'value' key for the class ID (e.g., {'value': '5'}). | | `po_number` | string | | — | Purchase order number provided by the customer. Maximum 25 characters (QuickBooks Windows) or 15 characters (QuickBooks Online). | | `requestid` | string | | — | Optional idempotency key (maximum 50 characters) to prevent duplicate writes on retries. If provided, QuickBooks will not create a duplicate invoice if the same requestid is used again. | | `ship_addr` | object | | — | Shipping address for the invoice. Provide as a dictionary with keys like 'Line1', 'City', 'CountrySubDivisionCode', 'PostalCode'. If not provided, defaults to the customer's shipping address. | | `ship_date` | string | | — | Date when the product was shipped or service was performed in YYYY-MM-DD format (e.g., '2026-02-25'). | | `bill_email` | object | | — | Email address where the invoice should be sent. Provide as a dictionary with 'Address' key (e.g., {'Address': ''}). | | `doc_number` | string | | — | Reference number for the transaction. Maximum 21 characters for QuickBooks Online. If not provided, QuickBooks auto-generates this by incrementing the last number. | | `customer_id` | string | ✅ | — | ID of the customer to invoice. This is the unique identifier for the customer in QuickBooks (e.g., '1', '92'). Use QUICKBOOKS\_CREATE\_CUSTOMER or QUICKBOOKS\_READ\_CUSTOMER to get valid customer IDs. Customer must be active; inactive customer IDs will cause invoice creation to fail. Similarly, all ItemRef values in `lines` must reference active items/services. | | `project_ref` | object | | — | Reference to the project associated with the invoice. Provide as a dictionary with 'value' key for the project ID (e.g., {'value': '10'}). | | `currency_ref` | object | | — | Reference to the currency in which all amounts on the invoice are expressed. Provide as a dictionary with 'value' key for the currency code (e.g., {'value': 'USD'}). | | `custom_field` | array | | — | Array of custom fields for the invoice. QuickBooks Online supports up to 3 custom fields. Each field should be a dictionary with 'DefinitionId', 'Name', 'Type', and value keys (e.g., \[{'DefinitionId': '1', 'Name': 'Field1', 'Type': 'StringType', 'StringValue': 'Value1'}]). | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). Allows access to version-specific features. If not specified, uses the default API version. | | `private_note` | string | | — | User-entered, organization-private note about the transaction that will not appear on customer-facing records. Maximum 4000 characters. | | `template_ref` | object | | — | Reference to the template used for formatting the invoice. Provide as a dictionary with 'value' key for the template ID (e.g., {'value': '5'}). | | `tracking_num` | string | | — | Shipping provider's tracking number for the delivery. Maximum 31 characters. | | `bill_email_cc` | object | | — | CC email address for the invoice. Provide as a dictionary with 'Address' key (e.g., {'Address': ''}). | | `customer_memo` | object | | — | User-entered message to the customer that appears on the invoice. Provide as a dictionary with 'value' key (e.g., {'value': 'Thank you for your business'}). Maximum 1000 characters. | | `exchange_rate` | number | | — | Currency exchange rate for multi-currency environments. Exchange rates are always recorded as the number of home currency units per one foreign currency unit. | | `bill_email_bcc` | object | | — | BCC email address for the invoice. Provide as a dictionary with 'Address' key (e.g., {'Address': ''}). | | `department_ref` | object | | — | Reference to the department for location tracking (QuickBooks Online). Provide as a dictionary with 'value' key for the department ID (e.g., {'value': '1'}). | | `sales_term_ref` | object | | — | Reference to the sales terms (payment terms) that determine the invoice due date. Provide as a dictionary with 'value' key for the term ID (e.g., {'value': '3'}). | | `ship_from_addr` | object | | — | Ship-from address for the invoice. Provide as a dictionary with keys like 'Line1', 'City', 'CountrySubDivisionCode', 'PostalCode'. | | `txn_tax_detail` | object | | — | Details of taxes charged on the transaction as a whole. Provide as a dictionary with 'TxnTaxCodeRef' and/or 'TaxLine' keys. QuickBooks automatically calculates this based on tax codes if not provided. | | `ship_method_ref` | object | | — | Reference to the shipping method. Provide as a dictionary with 'value' key for the shipping method ID (e.g., {'value': '2'}). | | `allow_ipn_payment` | boolean | | — | Specifies whether customer is allowed to use IPN (Instant Payment Notification) to pay the invoice. | | `allow_online_payment` | boolean | | — | Specifies whether customer is allowed to use eInvoicing (online payment) to pay the invoice. | | `deposit_to_account_ref` | object | | — | Reference to the asset account where payment deposits are recorded. Provide as a dictionary with 'value' key for the account ID (e.g., {'value': '35'}). | | `global_tax_calculation` | string | | — | Method used to apply taxes. Valid values: 'TaxExcluded', 'TaxInclusive', 'NotApplicable'. Default is 'TaxExcluded'. | | `allow_online_ach_payment` | boolean | | — | Permits customers to pay via electronic bank transfers (ACH) through eInvoicing. | | `apply_tax_after_discount` | boolean | | — | If false or null, calculate sales tax first then apply discount. If true, apply discount first then calculate tax. US QuickBooks companies only. | | `allow_online_credit_card_payment` | boolean | | — | Permits customers to pay via credit cards through eInvoicing. | *** ### `Quickbooks Create Item` Integration name: **QUICKBOOKS\_CREATE\_ITEM** Create a new item in QuickBooks Online. Items represent the products or services that a company buys, sells, or resells. Use when adding new inventory items, services, or non-inventory products to the QuickBooks catalog. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------- | :------: | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"Composio Test Service"` | User-recognizable name for the item. This is the name displayed in lists and forms in QuickBooks. | | `type` | string | ✅ | — | Classification specifying the use of this item. Valid values: 'Service' (services offered for sale), 'Inventory' (products bought and sold with quantity tracking - requires QuickBooks Online Plus or Advanced), 'NonInventory' (products bought and sold without quantity tracking), 'Category' (used to group items together), 'Bundle' (combination of products/services sold together). Different types have different required fields. | | `active` | boolean | | — | Whether the item is active and available for use. Default is true. | | `taxable` | boolean | | — | Whether sales of this item are subject to sales tax. Default is false. | | `parent_ref` | object | | — | Reference to another entity. | | `unit_price` | number | | — | Unit price of the item for sales. This is the default selling price per unit. | | `description` | string | | — | Description of the item that appears on sales forms such as invoices. This helps customers understand what they are purchasing. | | `qty_on_hand` | number | | `10` | Current quantity on hand for this inventory item. REQUIRED if TrackQtyOnHand is true. Must be a non-negative number. | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). Allows access to version-specific features. If not specified, uses the default API version. | | `purchase_cost` | number | | — | Cost to purchase this item from vendors. This is the default purchase cost per unit. | | `purchase_desc` | string | | — | Description of the item for purchase forms. This is the description used when purchasing the item from vendors. | | `inv_start_date` | string | | `"2026-01-01"` | Date when inventory tracking begins for this item. Format: YYYY-MM-DD. REQUIRED if TrackQtyOnHand is true. | | `asset_account_ref` | object | | `{"name":"Inventory Asset","value":"81"}` | Reference to another entity. | | `track_qty_on_hand` | boolean | | — | Whether quantity on hand is tracked for this item. If true, you must provide QtyOnHand and InvStartDate. Applicable for Inventory items. | | `income_account_ref` | object | | `{"name":"Sales of Product Income","value":"9"}` | Reference to another entity. | | `expense_account_ref` | object | | `{"name":"Cost of Goods Sold","value":"80"}` | Reference to another entity. | *** ### `Quickbooks Create Journal Entry` Integration name: **QUICKBOOKS\_CREATE\_JOURNAL\_ENTRY** Tool to create a new journal entry in QuickBooks Online. Use when you need to make adjusting or correcting entries that directly affect account balances. Journal entries require at least two lines with total debits equaling total credits. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Line` | array | ✅ | — | List of journal entry lines. Each journal entry must have at least two lines, and the total debits must equal the total credits. Typically includes at least one debit line and one credit line with matching amounts. | | `TxnDate` | string | | — | Transaction date for the journal entry in YYYY-MM-DD format. If not provided, the current date is used. | | `DocNumber` | string | | — | Reference number for the journal entry. Maximum 21 characters. | | `Adjustment` | boolean | | — | Indicates if this is an adjustment journal entry. Set to true for adjusting entries. | | `CurrencyRef` | object | | — | Reference to an entity. | | `PrivateNote` | string | | — | Private note about the journal entry. Maximum 4000 characters. | | `ExchangeRate` | number | | — | Exchange rate for multi-currency journal entries. | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). Allows access to version-specific features. If not specified, uses the default API version. | *** ### `Quickbooks Create Payment` Integration name: **QUICKBOOKS\_CREATE\_PAYMENT** Creates a payment record in QuickBooks Online. The Payment entity records payment from customers against single or multiple invoices and credit memos. Use this action when recording customer payments, whether full payment of an invoice or partial payment across multiple invoices. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `lines` | array | ✅ | — | List of payment line items specifying which invoices or credit memos the payment is applied to. Each line item must contain Amount and LinkedTxn fields. Example: \[{'Amount': 50.0, 'LinkedTxn': \[{'TxnId': '11', 'TxnType': 'Invoice'}]}] | | `txn_date` | string | | — | Date of the payment transaction in YYYY-MM-DD format (e.g., '2024-01-15'). If not specified, the current date is used. | | `total_amt` | number | ✅ | — | Total amount of the payment. This should equal the sum of all Line item amounts. Must be a positive number (e.g., 50.0, 100.0). | | `customer_id` | string | ✅ | — | ID of the customer making the payment. This is the unique identifier for the customer in QuickBooks (e.g., '3', '58'). Use QUICKBOOKS\_CREATE\_CUSTOMER or QUICKBOOKS\_READ\_CUSTOMER to get valid customer IDs. | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). Allows access to version-specific features. If not specified, uses the default API version. | | `private_note` | string | | — | Private note about the payment. Not visible to the customer. Maximum 4000 characters. | | `customer_name` | string | | — | Name of the customer. Optional field that helps with readability but not required by the API. | | `exchange_rate` | number | | — | Exchange rate for the transaction when using multi-currency. Applicable only if multi-currency is enabled. Optional field. | | `payment_ref_num` | string | | — | Reference number for the payment, such as a check number or transaction ID. Optional field. | | `process_payment` | boolean | | — | Indicates whether the payment should be processed through QuickBooks Payments. Set to true to process the payment, false otherwise. Optional field. | | `ar_account_ref_id` | string | | — | ID of the accounts receivable account. Optional field. Use QuickBooks query API to get valid AR account IDs. | | `currency_ref_value` | string | | — | Currency code for multi-currency environments (e.g., 'USD', 'CAD', 'EUR'). Required if the company file uses multi-currency. Optional otherwise. | | `credit_card_payment` | object | | — | Credit card payment details when payment method is credit card. | | `payment_method_ref_id` | string | | — | ID of the payment method used (e.g., '1' for Cash, '2' for Check). Optional field. Use QuickBooks query API to get valid payment method IDs. | | `deposit_to_account_ref_id` | string | | — | ID of the asset account where this payment should be deposited. Optional field. If not provided, uses the default Undeposited Funds account. | *** ### `Quickbooks Create Purchase` Integration name: **QUICKBOOKS\_CREATE\_PURCHASE** Tool to create a new purchase transaction in QuickBooks Online. A purchase represents an expense such as a cash payment, check, or credit card purchase. Use when recording business expenses or making payments to vendors. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Line` | array | ✅ | — | List of line items for the purchase. At least one line item is required. Each line must have an Amount and DetailType with corresponding detail object. | | `TxnDate` | string | | — | Date of the transaction in YYYY-MM-DD format (e.g., '2024-08-23'). If not provided, uses the current date. | | `TotalAmt` | number | | — | Total amount of the purchase including all line items. If not provided, QuickBooks will calculate it from the line items. Should match the sum of all line amounts. | | `DocNumber` | string | | — | Reference number for the purchase (e.g., check number). Maximum 21 characters. | | `EntityRef` | object | | — | Reference to an entity (vendor, customer, employee). | | `AccountRef` | object | ✅ | — | Reference to the account from which the payment is made (e.g., {'value': '19'} for a checking account or {'value': '42'} for a credit card account). | | `CurrencyRef` | object | | — | Reference to a currency. | | `PaymentType` | string | ✅ | — | Payment method used for this purchase. Choose 'Cash', 'Check', or 'CreditCard'. | | `PrivateNote` | string | | — | Private note about the purchase, visible only to company users. Maximum 4000 characters. | | `ExchangeRate` | number | | — | Exchange rate for multi-currency transactions. Required if CurrencyRef is different from home currency. | | `minorversion` | integer | | — | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). If not specified, uses the default API version from headers. | | `DepartmentRef` | object | | — | Reference to an account. | | `PaymentMethodRef` | object | | — | Reference to an entity (vendor, customer, employee). | | `GlobalTaxCalculation` | string | | — | Method used to apply tax on the transaction. Valid values: 'TaxExcluded', 'TaxInclusive', 'NotApplicable'. | | `TransactionLocationType` | string | | — | The location type of the transaction. Used for international tax calculations. | *** ### `Quickbooks Create Purchase Order` Integration name: **QUICKBOOKS\_CREATE\_PURCHASE\_ORDER** Create a new purchase order in QuickBooks. Use when you need to send a request to a vendor to deliver goods or services. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------ | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `fob` | string | | — | Free On Board shipping terms indicating point of transfer of ownership. | | `memo` | string | | — | Memo or note about the purchase order visible on reports and to the vendor. | | `lines` | array | ✅ | — | List of line items for the purchase order. Each line must have an 'amount' (number), 'detail\_type' ('ItemBasedExpenseLineDetail' or 'AccountBasedExpenseLineDetail'), and corresponding detail object. For item-based lines, include 'item\_based\_expense\_line\_detail' with an 'item\_ref'. For account-based lines, include 'account\_based\_expense\_line\_detail' with an 'account\_ref'. | | `due_date` | string | | — | Date when payment for the purchase order is due in YYYY-MM-DD format. | | `po_email` | object | | — | Email address structure. | | `txn_date` | string | | — | Transaction date of the purchase order in YYYY-MM-DD format. Defaults to the current date if not provided. | | `class_ref` | object | | — | Reference to another entity. | | `ship_addr` | object | | — | Physical address structure. | | `total_amt` | number | ✅ | — | Total amount of the purchase order. Should equal the sum of all line amounts. | | `vendor_id` | string | ✅ | — | ID of the vendor for this purchase order. Use QUICKBOOKS\_CREATE\_VENDOR or QUICKBOOKS\_READ\_VENDOR to get valid vendor IDs. | | `doc_number` | string | | — | Reference number for the purchase order. If not provided, QuickBooks will auto-generate it. | | `vendor_addr` | object | | — | Physical address structure. | | `currency_ref` | object | | — | Reference to another entity. | | `custom_field` | array | | — | Custom fields for the purchase order. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default API version. | | `private_note` | string | | — | Private note about the purchase order, not visible to the vendor. | | `template_ref` | object | | — | Reference to another entity. | | `ap_account_id` | string | ✅ | — | ID of the Accounts Payable account to use for this purchase order. This is typically the main AP account in your chart of accounts. | | `exchange_rate` | number | | — | Currency exchange rate for multi-currency transactions. | | `expected_date` | string | | — | Expected delivery date for products in YYYY-MM-DD format. | | `department_ref` | object | | — | Reference to another entity. | | `sales_term_ref` | object | | — | Reference to another entity. | | `txn_tax_detail` | object | | — | Transaction tax detail information including TxnTaxCodeRef and TaxLine. | | `ship_method_ref` | object | | — | Reference to another entity. | | `global_tax_calculation` | string | | — | Method in which tax is applied. Valid values: 'TaxExcluded', 'TaxInclusive', 'NotApplicable'. | *** ### `Quickbooks Create Refund Receipt` Integration name: **QUICKBOOKS\_CREATE\_REFUND\_RECEIPT** Tool to create a new refund receipt in QuickBooks Online. Use when a customer receives a refund for returned goods or services. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Line` | array | ✅ | — | List of line items for the refund receipt. At least one line item is required. Each line must specify Amount, DetailType, and relevant detail information. | | `TxnDate` | string | | — | Transaction date in YYYY-MM-DD format. If not provided, the current date is used. | | `DocNumber` | string | | — | Reference number for the refund receipt. Maximum 21 characters. | | `CurrencyRef` | object | | — | Reference to the currency. | | `CustomField` | array | | — | List of custom fields for the refund receipt. | | `CustomerRef` | object | ✅ | — | Reference to the customer receiving the refund. Required. | | `PrivateNote` | string | | — | Internal note about the refund receipt, not visible to customer. | | `ExchangeRate` | number | | — | Exchange rate for multi-currency transactions. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default API version. | | `PaymentRefNum` | string | | — | Reference number for the payment (e.g., check number, transaction ID). | | `DepositToAccountRef` | object | ✅ | — | Reference to the asset account where the refund is deposited. Required for the refund receipt. | *** ### `Quickbooks Create Sales Receipt` Integration name: **QUICKBOOKS\_CREATE\_SALES\_RECEIPT** Tool to create a new sales receipt in QuickBooks Online. Use when recording a sale where the customer pays immediately (cash, check, credit card). #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------- | ------- | :------: | --------------- | ------------------------------------------------------------------------------------------------------- | | `line` | array | ✅ | — | Array of line items for the sales receipt. At least one line item is required. | | `txn_date` | string | | `"2024-01-15"` | Transaction date in YYYY-MM-DD format. Defaults to current date if not provided. | | `bill_addr` | object | | — | Physical address structure. | | `class_ref` | object | | — | Generic reference type for various entities. | | `ship_addr` | object | | — | Physical address structure. | | `ship_date` | string | | `"2024-01-20"` | Date when goods or services are scheduled for delivery in YYYY-MM-DD format. | | `bill_email` | object | | — | Email address structure. | | `doc_number` | string | | — | Reference number for the sales receipt (maximum 21 characters). | | `currency_ref` | object | | — | Reference to currency. | | `custom_field` | array | | — | Array of custom fields for the sales receipt. | | `customer_ref` | object | ✅ | — | Reference to the customer receiving the sales receipt. Required field. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default API version. | | `private_note` | string | | — | Private note about the sales receipt, not visible to the customer. | | `tracking_num` | string | | — | Shipping tracking number provided by the shipping provider. | | `bill_email_cc` | object | | — | Email address structure. | | `customer_memo` | object | | — | Customer memo for the sales receipt. | | `exchange_rate` | number | | — | Exchange rate for currency conversion. | | `bill_email_bcc` | object | | — | Email address structure. | | `department_ref` | object | | — | Generic reference type for various entities. | | `sales_term_ref` | object | | — | Generic reference type for various entities. | | `payment_ref_num` | string | | — | Reference number for the payment (e.g., check number, transaction ID). | | `ship_method_ref` | object | | — | Generic reference type for various entities. | | `payment_method_ref` | object | | — | Reference to the payment method (e.g., {'value': '1'}). Use to specify how the customer paid. | | `deposit_to_account_ref` | object | | — | Reference to the deposit account. | | `global_tax_calculation` | string | | `"TaxExcluded"` | Method in which tax is applied. Allowed values: TaxExcluded, TaxInclusive, NotApplicable. | | `apply_tax_after_discount` | boolean | | — | Whether to apply tax after discount. Defaults to false. | *** ### `Quickbooks Create Tax Agency` Integration name: **QUICKBOOKS\_CREATE\_TAX\_AGENCY** Create a new tax agency in QuickBooks Online. Use when you need to set up a new tax authority or agency for tax reporting purposes. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ------------------------------- | ---------------------------------------------------------------------- | | `DisplayName` | string | ✅ | `"California State Tax Agency"` | The name of the tax agency as displayed in QuickBooks. Must be unique. | *** ### `Quickbooks Create Taxservice Taxcode` Integration name: **QUICKBOOKS\_CREATE\_TAXSERVICE\_TAXCODE** Create a new tax code with associated tax rates using the TaxService endpoint. Use when you need to set up new tax codes for sales or purchase transactions with specific tax rates. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------ | :------: | --------------- | --------------------------------------------------------------------------------------------------- | | `TaxCode` | string | ✅ | `"SALES_TAX_8"` | The unique identifier for the tax code being created. Must be unique within the QuickBooks company. | | `TaxRateDetails` | array | ✅ | — | List of tax rate details to associate with this tax code. At least one tax rate detail is required. | *** ### `Quickbooks Create Time Activity` Integration name: **QUICKBOOKS\_CREATE\_TIME\_ACTIVITY** Create a new time activity record in QuickBooks Online. TimeActivity tracks employee or vendor time worked on jobs or projects. Use when recording billable or non-billable hours for employees or vendors. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `hours` | integer | | — | Number of hours worked. Alternative to using start\_time and end\_time. Use with minutes field to specify duration. | | `minutes` | integer | | — | Number of minutes worked (0-59). Use with hours field to specify duration as an alternative to start\_time and end\_time. | | `name_of` | string | ✅ | `"Employee"` | Specifies the type of entity: 'Employee' for employee time tracking, or 'Vendor' for vendor/contractor time tracking. | | `taxable` | boolean | | — | Whether the time activity is taxable. Set to true if subject to sales tax. | | `end_time` | string | | `"2026-02-23T17:00:00+00:00"` | End time of the time activity in ISO 8601 format with timezone (e.g., '2026-02-23T17:00:00+00:00'). Required unless using hours and minutes fields. | | `item_ref` | object | | — | Reference to another entity. | | `txn_date` | string | | `"2026-02-23"` | Transaction date for the time activity in YYYY-MM-DD format (e.g., '2026-02-23'). If not provided, current date is used. | | `class_ref` | object | | — | Reference to another entity. | | `start_time` | string | | `"2026-02-23T09:00:00+00:00"` | Start time of the time activity in ISO 8601 format with timezone (e.g., '2026-02-23T09:00:00+00:00'). Required unless using hours and minutes fields. | | `vendor_ref` | object | | — | Reference to another entity. | | `break_hours` | integer | | — | Number of break hours to subtract from the time activity duration. | | `description` | string | | — | Description of work completed during this time activity. | | `hourly_rate` | number | | `50` | Hourly billing rate for this time activity. If not provided, uses the default rate from the employee/vendor record. | | `customer_ref` | object | | — | Reference to another entity. | | `employee_ref` | object | | — | Reference to another entity. | | `break_minutes` | integer | | — | Number of break minutes (0-59) to subtract from the time activity duration. | | `department_ref` | object | | — | Reference to another entity. | | `billable_status` | string | | — | Billable status of the time activity. | | `payroll_item_ref` | object | | — | Reference to another entity. | *** ### `Quickbooks Create Vendor` Integration name: **QUICKBOOKS\_CREATE\_VENDOR** Create a new vendor in QuickBooks with the given details. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------ | ------- | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `fax` | object | | — | Phone number input for vendor creation. | | `gstin` | string | | — | GST Identification Number (applicable for Indian vendors). | | `notes` | string | | — | Additional notes or comments about the vendor. | | `title` | string | | `"Mr."` | Title of the person (max 16 characters - keep it short like 'Mr.', 'Dr.', 'CEO'). This tag supports i18n, all locales. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, Suffix, or FullyQualifiedName attributes are required during create. | | `active` | boolean | | — | Indicates whether the vendor is currently active. Set to False to make inactive. | | `mobile` | object | | — | Phone number input for vendor creation. | | `suffix` | string | | — | Suffix of the name. For example, Jr. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `balance` | number | | — | Opening balance amount for this vendor. Use with open\_balance\_date. | | `acct_num` | string | | — | Account number assigned to this vendor for tracking purposes. | | `term_ref` | object | | — | Reference type input for entity references. | | `web_addr` | object | | — | Website address input for vendor creation. | | `bill_addr` | object | | — | Physical address input for vendor creation. | | `bill_rate` | number | | — | Standard billing rate for the vendor (per hour or unit). | | `ship_addr` | object | | — | Physical address input for vendor creation. | | `given_name` | string | | — | Given name or first name of a person. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `parent_ref` | object | | — | Reference type input for entity references. | | `family_name` | string | | — | Family name or the last name of the person. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `middle_name` | string | | — | Middle name of the person. The person can have zero or more middle names. The DisplayName attribute or at least one of Title, GivenName, MiddleName, FamilyName, or Suffix attributes is required for object create. | | `tax_country` | string | | — | Country for tax purposes (e.g., 'US', 'CA', 'IN'). | | `tds_enabled` | boolean | | — | Indicates if Tax Deducted at Source (TDS) is enabled (India). | | `vendor_1099` | boolean | | — | Indicates whether the vendor is eligible for 1099 tax reporting (US tax purposes). | | `company_name` | string | | — | The name of the company associated with the vendor. Useful when creating organizational vendors. | | `contact_name` | string | | — | Primary contact person's name at the vendor. | | `credit_limit` | number | | — | Maximum credit amount extended to the vendor. | | `currency_ref` | object | | — | Reference type input for entity references. | | `display_name` | string | | — | The name as displayed. Must be unique across all Customer, Vendor, and Employee objects. Cannot be removed with sparse update. If not supplied, the system generates DisplayName by concatenating customer name components supplied in the request from the following list: Title, GivenName, MiddleName, FamilyName, and Suffix. | | `t4a_eligible` | boolean | | — | Canadian T4A tax form eligibility status. | | `primary_phone` | object | | — | Phone number input for vendor creation. | | `ap_account_ref` | object | | — | Reference type input for entity references. | | `t5018_eligible` | boolean | | — | Canadian T5018 tax form eligibility status. | | `tax_identifier` | string | | — | Tax identification number for the vendor (EIN or SSN). | | `alternate_phone` | object | | — | Phone number input for vendor creation. | | `business_number` | string | | — | Business registration number or tax identification number. | | `alt_contact_name` | string | | — | Alternate contact person's name at the vendor. | | `open_balance_date` | string | | — | Date of the opening balance in YYYY-MM-DD format. | | `primary_email_addr` | object | | — | Email address input for vendor creation. | | `tds_entity_type_id` | integer | | — | TDS entity type classification identifier (India). | | `print_on_check_name` | string | | — | The name of the vendor as it should be printed on checks. If not provided, uses DisplayName. | | `tax_reporting_basis` | string | | — | Tax reporting methodology (e.g., 'Cash', 'Accrual'). | | `tds_section_type_id` | integer | | — | TDS section type categorization identifier (India). | | `default_tax_code_ref` | object | | — | Reference type input for entity references. | | `gst_registration_type` | string | | — | GST registration type (applicable for Indian vendors, e.g., 'Regular', 'Composition'). | | `tax_id_effective_date` | string | | — | Effective date for the tax identification number in YYYY-MM-DD format. | | `tds_override_threshold` | boolean | | — | Whether to override the standard TDS threshold limits (India). | *** ### `Quickbooks Create Vendor Credit` Integration name: **QUICKBOOKS\_CREATE\_VENDOR\_CREDIT** Tool to create a new vendor credit in QuickBooks Online. Use when recording a credit from a vendor that reduces what you owe. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Line` | array | ✅ | — | List of line items for the vendor credit. At least one line item is required. Each line must specify DetailType, Amount, and AccountBasedExpenseLineDetail. | | `Memo` | string | | — | Memo for the vendor credit that appears on reports. | | `TxnDate` | string | | — | Date of the transaction in YYYY-MM-DD format. Defaults to the current date if not provided. | | `DocNumber` | string | | — | Reference number for the vendor credit (e.g., credit memo number from vendor). | | `VendorRef` | object | ✅ | — | Reference to the vendor from whom the credit is received. Required field. | | `CurrencyRef` | object | | — | Reference to the currency. Format: {'value': 'USD'}. | | `PrivateNote` | string | | — | User-entered private note about the vendor credit. | | `APAccountRef` | object | | — | Reference to the Accounts Payable account. Format: {'value': 'account\_id'}. If not specified, uses the default AP account. | | `ExchangeRate` | number | | — | Currency exchange rate for multi-currency transactions. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default version. | | `DepartmentRef` | object | | — | Reference to the department. Format: {'value': 'department\_id'}. | | `GlobalTaxCalculation` | string | | — | Method in which tax is applied. Valid values: TaxExcluded, TaxInclusive, NotApplicable. | *** ### `Quickbooks Customer Balance Detail` Integration name: **QUICKBOOKS\_CUSTOMER\_BALANCE\_DETAIL** Generate a balance detail report for a customer in QuickBooks with the given customer ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `arpaid` | string | | — | Status of the balance. | | `columns` | string | | — | Column types to be shown in the report. Supported Values: bill\_addr, create\_by, create\_date, cust\_bill\_email, cust\_comp\_name, cust\_msg, cust\_phone\_other, cust\_tel, cust\_name, deliv\_addr, doc\_num\*, due\_date\*, last\_mod\_by, last\_mod\_date, memo\*, sale\_sent\_state, ship\_addr, ship\_date, ship\_via, term\_name, tracking\_num, tx\_date\*, txn\_type\*. Additional columns with custom fields enabled: sales\_cust1, sales\_cust2, sales\_cust3. Additional columns with location tracking enabled: dept\_name\* | | `custom1` | string | | — | Filter by the specified custom field as defined by the CustomField attribute in transaction entities where supported. Supported Values: Name of custom field. | | `shipvia` | string | | — | Filter by the shipping method as stored in Invoice.ShipMethodRef.Name. | | `sort_by` | string | | — | The column type used in sorting report rows. Specify a column type as defined with the columns query parameter. | | `term_ids` | array | | — | One or more comma separated term IDs. Filters report contents based on term or terms supplied. | | `sort_order` | string | | — | The sort order. | | `end_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `aging_method` | string | | — | The date upon which aging is determined. | | `customer_ids` | array | | — | One or more comma separated customer IDs. Filters report contents to include information for specified customers. | | `start_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | *** ### `Quickbooks Customer Balance Report` Integration name: **QUICKBOOKS\_CUSTOMER\_BALANCE\_REPORT** Generate a customer balance report in QuickBooks showing outstanding balances for customers. Can filter by specific customers, date ranges, payment status, and accounting method. Returns a hierarchical report with customer names, IDs, and their current balance amounts. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `qzurl` | string | | — | Specifies whether Quick Zoom URL information should be generated for rows in the report. | | `arpaid` | string | | — | Filter by payment status. 'All' includes all balances, 'Paid' shows only paid invoices, 'Unpaid' shows only outstanding balances. If not specified, defaults to showing all. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value from the Customer object (e.g., \['1', '2', '10']). | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Delete Bank Account` Integration name: **QUICKBOOKS\_DELETE\_BANK\_ACCOUNT** Tool to delete a bank account on file for a customer in QuickBooks Payments API. Use when removing a customer's payment method. Returns 204 No Content on success with an empty response body from the API. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ---------------------------------------- | --------------------------------------------------------------------------------------------------------- | | `request_id` | string | | `"550e8400-e29b-41d4-a716-446655440005"` | UUID for idempotency to prevent duplicate requests. If not provided, one will be generated automatically. | | `customer_id` | string | ✅ | `"test-customer-id"` | The customer ID for whom the bank account is being deleted (can be a test ID like 'test-customer-id') | | `bank_account_id` | string | ✅ | `"200153232587278746893210"` | The bank account ID to delete | *** ### `Quickbooks Execute Batch Operation` Integration name: **QUICKBOOKS\_EXECUTE\_BATCH\_OPERATION** Execute multiple QuickBooks operations in a single request. Operations are performed serially. Supports create, update, delete, and query operations on QuickBooks entities. Use this action to reduce network latency when performing multiple operations. Each operation is executed in order, and each response is correlated to its request via the bId field. Maximum 30 operations per batch. Ideal for bulk data operations or related entity updates. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `minorversion` | integer | | `65` | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). Allows access to version-specific features. If not specified, uses the default API version from metadata. | | `BatchItemRequest` | array | ✅ | — | List of batch item requests to execute. Each item can be a create, update, delete, or query operation. Operations are performed serially in the order provided. Maximum 30 items per batch request. | *** ### `Quickbooks Get Aged Receivables Report` Integration name: **QUICKBOOKS\_GET\_AGED\_RECEIVABLES\_REPORT** Generate an aged receivables report showing outstanding customer balances by age. Use when tracking overdue invoices and managing accounts receivable aging. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `arpaid` | string | | — | Filters customers by payment status. Use 'All' for all customers, 'Paid' for customers with fully paid balances, or 'Unpaid' for customers with outstanding balances. Default is 'Unpaid'. | | `date_macro` | string | | — | Predefined date macro like 'Today', 'This Month', etc. Alternative to report\_date for specifying the report date using a macro. | | `num_periods` | integer | | — | Number of aging periods to display in the report. Must be between 1 and 10. Defaults to 4 if not specified. Each period shows receivables within that age range. | | `report_date` | string | | — | Date for the aged receivables report in YYYY-MM-DD format. Defaults to today if not provided. This is the as-of date for calculating aging. | | `aging_method` | string | | — | Method for calculating aging. 'Report\_Date' calculates aging from the report date, 'Current' calculates aging from the current date. Defaults to 'Report\_Date' if not specified. | | `aging_period` | integer | | — | Number of days per aging period. Must be at least 1. Defaults to 30 days if not specified. For example, with 30 days you get periods like 0-30, 31-60, etc. | | `customer_ids` | array | | — | One or more comma-separated customer IDs to filter the report. Filters report contents to include information for specified customers only. Provide customer IDs as returned in the Customer.Id attribute. | | `minorversion` | string | | — | API minor version number. Optional - defaults to x-minor-version header if not provided. Use this to access features from specific minor versions of the QuickBooks API. | *** ### `Quickbooks Get Attachable` Integration name: **QUICKBOOKS\_GET\_ATTACHABLE** Tool to read details of a specific attachable by ID in QuickBooks Online. Attachables represent file attachments linked to entities like invoices, customers, or bills. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------- | :------: | ------------ | -------------------------------------------------------------------------------------------------- | | `minorversion` | integer | | `75` | API minor version to use for the request. If not provided, uses the version from metadata headers. | | `attachable_id` | string | ✅ | `"68120641"` | ID of the attachable (file attachment) to retrieve | *** ### `Quickbooks Get Balance Sheet Report` Integration name: **QUICKBOOKS\_GET\_BALANCE\_SHEET\_REPORT** Generate a Balance Sheet report showing company assets, liabilities, and equity at a point in time. Use when you need to understand the financial position with what the company owns versus what it owes. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Bank Account` Integration name: **QUICKBOOKS\_GET\_BANK\_ACCOUNT** Tool to retrieve a specific bank account by ID from QuickBooks Payments API. Use when you need to get details about a specific payment method for a customer. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------ | :------: | ---------------------------- | ----------------------------------------------------- | | `customer_id` | string | ✅ | `"123456789012345678901234"` | The customer ID who owns the bank account | | `bank_account_id` | string | ✅ | `"200180091307278738147890"` | The unique identifier of the bank account to retrieve | *** ### `Quickbooks Get Bill` Integration name: **QUICKBOOKS\_GET\_BILL** Tool to fetch a QuickBooks bill by ID. Use when needing to retrieve bill details including vendor reference, line items, amounts, and payment status. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------- | | `bill_id` | string | ✅ | `"13"` | ID of the bill to retrieve from QuickBooks | | `minorversion` | integer | | `65` | API minor version to use for the request (e.g., 65, 70, 75). If not specified, uses the default from headers. | *** ### `Quickbooks Get Bill Payment` Integration name: **QUICKBOOKS\_GET\_BILL\_PAYMENT** Tool to retrieve details of a specific bill payment by ID in QuickBooks Online. Use when you need to view information about an existing bill payment. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------- | | `minorversion` | integer | | `75` | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default from headers. | | `bill_payment_id` | string | ✅ | `"10"` | ID of the bill payment to retrieve. | *** ### `Quickbooks Get Changed Entities` Integration name: **QUICKBOOKS\_GET\_CHANGED\_ENTITIES** Tool to retrieve entities that changed since a specified timestamp using QuickBooks Change Data Capture (CDC) API. Use when you need to sync or refresh local data periodically by fetching only entities modified within the last 30 days. Returns full entity payloads (not just changed attributes) grouped by entity type with up to 1000 entities per response. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `entities` | string | ✅ | `"Customer,Invoice"` | Comma-separated list of entity types to query for changes. Valid entity types include: Account, Bill, BillPayment, Budget, Class, CreditMemo, Customer, Department, Deposit, Employee, Estimate, Invoice, Item, JournalEntry, Payment, PaymentMethod, Purchase, PurchaseOrder, RefundReceipt, SalesReceipt, TaxCode, TaxRate, Term, TimeActivity, Transfer, Vendor, VendorCredit. Example: 'Customer,Invoice' or 'Bill,Payment,Vendor'. | | `changedSince` | string | ✅ | `"2026-02-16T00:00:00Z"` | ISO 8601 timestamp indicating the starting point for change tracking. Returns entities modified after this timestamp. Maximum lookback period is 30 days. Format: YYYY-MM-DDTHH:MM:SSZ (UTC timezone recommended). Example: '2026-02-16T00:00:00Z' | *** ### `Quickbooks Get Company Info` Integration name: **QUICKBOOKS\_GET\_COMPANY\_INFO** Tool to read company information from QuickBooks Online. Returns basic company info including name, addresses, fiscal year settings, and subscription status. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------- | | `minorversion` | integer | | `75` | API minor version to use for the request. If not provided, uses the version from metadata headers. | *** ### `Quickbooks Get Credit Memo` Integration name: **QUICKBOOKS\_GET\_CREDIT\_MEMO** Tool to fetch a QuickBooks credit memo by ID. Use when needing full credit memo details including metadata, customer info, line items, and remaining credit amount. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------- | :------: | ------- | ---------------------------------------- | | `minorversion` | integer | | `70` | API minor version to use for the request | | `credit_memo_id` | string | ✅ | `"14"` | ID of the credit memo to read | *** ### `Quickbooks Get Credit Memo Pdf` Integration name: **QUICKBOOKS\_GET\_CREDIT\_MEMO\_PDF** Tool to download a QuickBooks credit memo as a PDF file. Use when you need to retrieve the printable PDF version of a credit memo. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `minorversion` | string | | `"70"` | API minor version to use for the request (e.g., '70', '75'). If not specified, uses the default API version. | | `credit_memo_id` | string | ✅ | `"14"` | The ID of the credit memo to retrieve as PDF (e.g., '14', '123'). | *** ### `Quickbooks Get Department` Integration name: **QUICKBOOKS\_GET\_DEPARTMENT** Read details of a specific department by ID in QuickBooks Online. Use when you need to retrieve information about a department. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ------- | ------------------------------------- | | `department_id` | string | ✅ | — | The ID of the department to retrieve. | *** ### `Quickbooks Get Deposit` Integration name: **QUICKBOOKS\_GET\_DEPOSIT** Tool to read details of a specific deposit by ID in QuickBooks Online. Use when you need complete deposit information including line items, amounts, and metadata. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | `deposit_id` | string | ✅ | `"4"` | ID of the deposit to retrieve. Use QUICKBOOKS\_QUERY\_DEPOSIT to find deposit IDs. | | `minorversion` | integer | | `65` | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). If not specified, uses the default API version from headers. | *** ### `Quickbooks Get Estimate` Integration name: **QUICKBOOKS\_GET\_ESTIMATE** Tool to fetch a QuickBooks estimate by ID. Use when needing full estimate details including metadata, line items, and sync token. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ------------------------------------------ | | `estimate_id` | string | ✅ | `"19"` | ID of the estimate to read from QuickBooks | | `minorversion` | integer | | `65` | API minor version to use for the request | *** ### `Quickbooks Get Estimate Pdf` Integration name: **QUICKBOOKS\_GET\_ESTIMATE\_PDF** Tool to download a QuickBooks estimate as a PDF file. Use when you need to retrieve the printable PDF version of an estimate. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `estimate_id` | string | ✅ | `"19"` | The ID of the estimate to retrieve as PDF (e.g., '19', '123'). | | `minorversion` | string | | `"65"` | API minor version to use for the request (e.g., '65', '75'). If not specified, uses the default API version. | *** ### `Quickbooks Get Exchange Rate` Integration name: **QUICKBOOKS\_GET\_EXCHANGE\_RATE** Tool to get exchange rate for a specific currency code and date in QuickBooks Online. Use when needing to retrieve the current or historical exchange rate between a foreign currency and the company's home currency. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------- | ------- | :------: | -------------- | -------------------------------------------------------------------------------------------------- | | `asofdate` | string | ✅ | `"2024-01-15"` | The date for which to get the exchange rate, in YYYY-MM-DD format (e.g., 2024-01-15). | | `minorversion` | integer | | `73` | API minor version to use for the request. If not provided, uses the version from metadata headers. | | `sourcecurrencycode` | string | ✅ | `"EUR"` | The source currency code for which to get the exchange rate (e.g., EUR, GBP, JPY). | *** ### `Quickbooks Get General Ledger Report` Integration name: **QUICKBOOKS\_GET\_GENERAL\_LEDGER\_REPORT** Generate a General Ledger report showing all transactions with debits, credits, and running balances. Use when you need a detailed view of all accounting transactions posted to each account. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `columns` | string | | — | Column types to show in the report. Comma-separated list of column names (e.g., 'tx\_date,txn\_type,doc\_num,name,memo,account,debit,credit,balance'). | | `sort_by` | string | | — | The column type on which to base sorting (e.g., 'tx\_date', 'account', 'txn\_type'). Default is 'txn\_type' if not specified. | | `end_date` | string | | — | End date for the report period in YYYY-MM-DD format. | | `class_ids` | array | | — | List of class IDs to filter the report. If not provided, the report includes all classes. Each ID should be the Class.Id value (e.g., \['1', '2']). | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order for rows (ascending or descending). Default is ascending. | | `start_date` | string | | — | Start date for the report period in YYYY-MM-DD format. | | `vendor_ids` | array | | — | List of vendor IDs to filter the report. If not provided, the report includes all vendors. Each ID should be the Vendor.Id value (e.g., \['1', '3']). | | `account_ids` | array | | — | List of account IDs to filter the report. If not provided, the report includes all accounts. Each ID should be the Account.Id value from the Account object (e.g., \['1', '35', '82']). | | `account_type` | string | | — | Account type from which to include transactions (e.g., 'Bank', 'Expense', 'Income'). | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value (e.g., \['1', '5']). | | `department_ids` | array | | — | List of department IDs to filter the report. If not provided, the report includes all departments. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report (Cash or Accrual). | | `source_account_ids` | array | | — | List of source account IDs to filter the report. Each ID should be the Account.Id value for the source account. | | `source_account_type` | string | | — | Source account type for transaction filtering. | *** ### `Quickbooks Get Inventory Valuation Summary` Integration name: **QUICKBOOKS\_GET\_INVENTORY\_VALUATION\_SUMMARY** Generate an Inventory Valuation Summary report showing inventory quantities and their current values. Use when you need to understand inventory asset values, track stock levels, or analyze inventory costs by item. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Invoice Pdf` Integration name: **QUICKBOOKS\_GET\_INVOICE\_PDF** Tool to download a QuickBooks invoice as a PDF file. Use when you need to retrieve the printable PDF version of an invoice. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `invoice_id` | string | ✅ | `"17"` | The ID of the invoice to retrieve as PDF (e.g., '17', '123'). | | `minorversion` | string | | `"70"` | API minor version to use for the request (e.g., '70', '75'). If not specified, uses the default API version. | *** ### `Quickbooks Get Item` Integration name: **QUICKBOOKS\_GET\_ITEM** Tool to retrieve a specific item by its ID from QuickBooks Online. Use when you need full details of a product or service item. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `item_id` | string | ✅ | `"12421341"` | Unique identifier of the item to retrieve from QuickBooks. | | `minorversion` | integer | | `65` | QuickBooks API minor version number to use for this request (e.g., 65, 70, 75). Allows access to version-specific features. If not specified, uses the default API version. | *** ### `Quickbooks Get Journal Entry` Integration name: **QUICKBOOKS\_GET\_JOURNAL\_ENTRY** Tool to read details of a specific QuickBooks journal entry by ID. Use when you need complete journal entry information including transaction date, line items, posting types, and account references. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ------- | --------------------------------------- | | `minorversion` | integer | | `75` | API minor version number (e.g., 75) | | `journal_entry_id` | string | ✅ | `"1"` | The ID of the journal entry to retrieve | *** ### `Quickbooks Get Payment` Integration name: **QUICKBOOKS\_GET\_PAYMENT** Tool to fetch details of a specific payment by ID in QuickBooks Online. Use when needing payment information including customer, amounts, and linked transactions. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ---------------------------------------- | | `payment_id` | string | ✅ | `"18"` | ID of the payment to retrieve | | `minorversion` | integer | | `65` | API minor version to use for the request | *** ### `Quickbooks Get Payment Method` Integration name: **QUICKBOOKS\_GET\_PAYMENT\_METHOD** Read details of a specific payment method by ID in QuickBooks Online. Use when you need to retrieve information about a payment method entity. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------ | :------: | ------- | ----------------------------------- | | `payment_method_id` | string | ✅ | — | ID of the payment method to be read | *** ### `Quickbooks Get Payment Pdf` Integration name: **QUICKBOOKS\_GET\_PAYMENT\_PDF** Tool to download a QuickBooks payment record as a PDF file. Use when you need to retrieve the printable PDF version of a payment. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `payment_id` | string | ✅ | `"18"` | The ID of the payment record to retrieve as PDF (e.g., '18', '123'). | | `minorversion` | string | | `"70"` | API minor version to use for the request (e.g., '70', '75'). If not specified, uses the default API version. | *** ### `Quickbooks Get Preferences` Integration name: **QUICKBOOKS\_GET\_PREFERENCES** Tool to read company preferences that control application behavior in QuickBooks Online. Use when needing to retrieve accounting settings, sales form configurations, tax preferences, time tracking settings, or other company-wide preference data. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------- | | `minorversion` | integer | | `75` | API minor version to use for the request. If not provided, uses the version from metadata headers. | *** ### `Quickbooks Get Profit And Loss Detail Report` Integration name: **QUICKBOOKS\_GET\_PROFIT\_AND\_LOSS\_DETAIL\_REPORT** Generate a detailed Profit and Loss report showing company income and expenses with transaction-level details. Use when you need to analyze profitability with individual transaction details, customer/vendor breakdowns, and account-level activity. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `end_date` | string | | — | Report end date in YYYY-MM-DD format. If not provided, defaults to today's date. | | `class_ids` | array | | — | List of class IDs to filter the report. If not provided, the report includes all classes. Each ID should be the Class.Id value from the Class object (e.g., \['1', '3']). | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `start_date` | string | | — | Report start date in YYYY-MM-DD format. If not provided, defaults to the start of the current fiscal year. | | `vendor_ids` | array | | — | List of vendor IDs to filter the report. If not provided, the report includes all vendors. Each ID should be the Vendor.Id value from the Vendor object (e.g., \['1', '5', '20']). | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value from the Customer object (e.g., \['1', '2', '10']). | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Profit And Loss Report` Integration name: **QUICKBOOKS\_GET\_PROFIT\_AND\_LOSS\_REPORT** Generate a Profit and Loss report showing company income and expenses over a period. Use when you need to analyze profitability, revenue, costs, and net income for a specific date range. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `end_date` | string | | — | Report end date in YYYY-MM-DD format. If not provided, defaults to today's date. | | `class_ids` | array | | — | List of class IDs to filter the report. If not provided, the report includes all classes. Each ID should be the Class.Id value from the Class object (e.g., \['1', '3']). | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `start_date` | string | | — | Report start date in YYYY-MM-DD format. If not provided, defaults to the start of the current fiscal year. | | `vendor_ids` | array | | — | List of vendor IDs to filter the report. If not provided, the report includes all vendors. Each ID should be the Vendor.Id value from the Vendor object (e.g., \['1', '5', '20']). | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value from the Customer object (e.g., \['1', '2', '10']). | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Purchase` Integration name: **QUICKBOOKS\_GET\_PURCHASE** Tool to fetch details of a specific purchase by ID in QuickBooks Online. Use when you need to retrieve complete purchase information including line items, payment details, and metadata. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------- | | `purchase_id` | string | ✅ | `"20"` | ID of the purchase to retrieve | | `minorversion` | integer | | `65` | API minor version to use for the request. If not provided, uses the version from metadata headers. | *** ### `Quickbooks Get Purchase Order` Integration name: **QUICKBOOKS\_GET\_PURCHASE\_ORDER** Tool to fetch a QuickBooks purchase order by ID. Use when needing full purchase order details including line items, vendor information, and metadata. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | ------- | ---------------------------------------- | | `minorversion` | integer | | `65` | API minor version to use for the request | | `purchase_order_id` | string | ✅ | `"15"` | ID of the purchase order to retrieve | *** ### `Quickbooks Get Purchase Order Pdf` Integration name: **QUICKBOOKS\_GET\_PURCHASE\_ORDER\_PDF** Tool to download a QuickBooks purchase order as a PDF file. Use when you need to retrieve the printable PDF version of a purchase order. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `minorversion` | string | | `"70"` | API minor version to use for the request (e.g., '70', '75'). If not specified, uses the default API version. | | `purchase_order_id` | string | ✅ | `"25"` | The ID of the purchase order to retrieve as PDF (e.g., '25', '123'). | *** ### `Quickbooks Get Refund Receipt` Integration name: **QUICKBOOKS\_GET\_REFUND\_RECEIPT** Tool to fetch a QuickBooks refund receipt by ID. Use when needing details of a specific refund issued to a customer. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | ------- | ---------------------------------------- | | `minorversion` | integer | | `75` | API minor version to use for the request | | `refund_receipt_id` | string | ✅ | `"9"` | ID of the refund receipt to retrieve | *** ### `Quickbooks Get Refund Receipt Pdf` Integration name: **QUICKBOOKS\_GET\_REFUND\_RECEIPT\_PDF** Tool to download a QuickBooks refund receipt as a PDF file. Use when you need to retrieve the printable PDF version of a refund receipt. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `minorversion` | string | | `"70"` | API minor version to use for the request (e.g., '70', '75'). If not specified, uses the default API version. | | `refund_receipt_id` | string | ✅ | `"22"` | The ID of the refund receipt to retrieve as PDF (e.g., '22', '123'). | *** ### `Quickbooks Get Report Account List` Integration name: **QUICKBOOKS\_GET\_REPORT\_ACCOUNT\_LIST** Retrieve the AccountList report from QuickBooks showing a list of all accounts. This report displays all account details including name, type, and balance information. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `columns` | string | | — | Comma-separated list of column names to include in the report. Valid column names: 'account\_name', 'account\_type', 'detail\_acc\_type', 'account\_desc', 'account\_bal'. If not specified, all columns are included. Example: 'account\_name,account\_type,account\_bal' | | `sort_order` | string | | — | The sort order for the accounts. Valid values: 'ascend' (ascending, A-Z) or 'descend' (descending, Z-A). If not specified, accounts are returned in their default order. | *** ### `Quickbooks Get Report Aged Payable Detail` Integration name: **QUICKBOOKS\_GET\_REPORT\_AGED\_PAYABLE\_DETAIL** Generate an aged payable detail report showing aging detail for accounts payable. Use when you need to analyze outstanding vendor bills grouped by aging periods. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `appaid` | string | | — | Status of the payable balance. | | `columns` | string | | — | Column types to be shown in the report. Supported Values: bill\_addr, create\_by, create\_date, vend\_bill\_email, vend\_comp\_name, vend\_phone\_other, vend\_tel, vend\_name, doc\_num\*, due\_date\*, last\_mod\_by, last\_mod\_date, memo\*, term\_name, tx\_date\*, txn\_type\*. Additional columns with custom fields enabled: purch\_vend1, purch\_vend2, purch\_vend3. Additional columns with location tracking enabled: dept\_name\* | | `sort_by` | string | | — | The column type used in sorting report rows. Specify a column type as defined with the columns query parameter. | | `term_ids` | array | | — | One or more comma separated term IDs. Filters report contents based on term or terms supplied. | | `date_macro` | string | | — | Predefined date range for the report. Examples: 'Today', 'This Month', 'Last Month', 'This Fiscal Quarter', etc. | | `sort_order` | string | | — | The sort order. | | `vendor_ids` | array | | — | One or more comma separated vendor IDs. Filters report contents to include information for specified vendors. | | `end_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `num_periods` | integer | | — | Number of aging periods to display in the report. Each period represents a time bucket for aging calculations (e.g., 0-30 days, 31-60 days). | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `aging_method` | string | | — | The date upon which aging is determined. | | `aging_period` | integer | | — | Number of days per aging period. Default is typically 30 days. For example, setting this to 30 creates buckets like 0-30, 31-60, 61-90 days. | | `duedate_macro` | string | | — | Predefined date range for filtering by due date. Examples: 'Today', 'This Month', 'Last Month', 'This Fiscal Quarter', etc. | | `start_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. Supported values: Cash, Accrual. | *** ### `Quickbooks Get Report Aged Payables` Integration name: **QUICKBOOKS\_GET\_REPORT\_AGED\_PAYABLES** Retrieve an Aged Payables aging summary report from QuickBooks showing outstanding vendor balances grouped by age. Shows amounts owed to vendors categorized by aging periods (e.g., current, 1-30 days, 31-60 days overdue). #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `appaid` | string | | — | Filters vendors by payment status. Use 'All' for all vendors, 'Paid' for vendors with fully paid balances, or 'Unpaid' for vendors with outstanding balances. Default is 'Unpaid'. | | `date_macro` | string | | — | Predefined date macro like 'Today', 'This Month', etc. Alternative to report\_date for specifying the report date using a macro. | | `vendor_ids` | array | | — | Filters report contents to include information for specified vendors. Provide one or more comma-separated vendor IDs as returned in the Vendor.Id attribute. | | `num_periods` | integer | | — | Number of aging periods to display in the report. Must be between 1 and 10. Defaults to 4 if not specified. Each period shows payables within that age range. | | `report_date` | string | | — | Date for the aged payables report in YYYY-MM-DD format. Defaults to today if not provided. This is the as-of date for calculating aging. | | `aging_method` | string | | — | Method for calculating aging. 'Report\_Date' calculates aging from the report date, 'Current' calculates aging from the current date. Defaults to 'Report\_Date' if not specified. | | `aging_period` | integer | | — | Number of days per aging period. Must be at least 1. Defaults to 30 days if not specified. For example, with 30 days you get periods like 0-30, 31-60, etc. | | `minorversion` | string | | — | API minor version number. Optional - defaults to x-minor-version header if not provided. Use this to access features from specific minor versions of the QuickBooks API. | *** ### `Quickbooks Get Report Aged Receivable Detail` Integration name: **QUICKBOOKS\_GET\_REPORT\_AGED\_RECEIVABLE\_DETAIL** Generate an aged receivable detail report showing aging detail for accounts receivable. Use when you need to analyze outstanding customer invoices grouped by aging periods. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `arpaid` | string | | — | Status of the receivable balance. | | `columns` | string | | — | Column types to be shown in the report. Supported Values: bill\_addr, create\_by, create\_date, cust\_bill\_email, cust\_comp\_name, cust\_msg, cust\_phone\_other, cust\_tel, cust\_name, deliv\_addr, doc\_num\*, due\_date\*, last\_mod\_by, last\_mod\_date, memo\*, sale\_sent\_state, ship\_addr, ship\_date, ship\_via, term\_name, tracking\_num, tx\_date\*, txn\_type\*. Additional columns with custom fields enabled: sales\_cust1, sales\_cust2, sales\_cust3. Additional columns with location tracking enabled: dept\_name\* | | `custom1` | string | | — | Filter by the specified custom field as defined by the CustomField attribute in transaction entities where supported. Supported Values: Name of custom field. | | `shipvia` | string | | — | Filter by the shipping method as stored in Invoice.ShipMethodRef.Name. | | `sort_by` | string | | — | The column type used in sorting report rows. Specify a column type as defined with the columns query parameter. | | `term_ids` | array | | — | One or more comma separated term IDs. Filters report contents based on term or terms supplied. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use report\_date to specify an explicit report date. | | `sort_order` | string | | — | The sort order. | | `end_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `num_periods` | integer | | — | Number of aging periods to display in the report. Each period represents a time bucket for aging calculations (e.g., 0-30 days, 31-60 days). | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `aging_method` | string | | — | The date upon which aging is determined. | | `aging_period` | integer | | — | Number of days per aging period. Default is typically 30 days. For example, setting this to 30 creates buckets like 0-30, 31-60, 61-90 days. | | `customer_ids` | array | | — | One or more comma separated customer IDs. Filters report contents to include information for specified customers. | | `duedate_macro` | string | | — | Predefined date range of due dates for receivables to include in the report; otherwise, use the start\_duedate and end\_duedate to cover an explicit report date range. | | `start_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | *** ### `Quickbooks Get Report Cash Flow` Integration name: **QUICKBOOKS\_GET\_REPORT\_CASH\_FLOW** Generate a cash flow report in QuickBooks showing cash inflows and outflows categorized by operating, investing, and financing activities. Use when you need to analyze cash movement and liquidity over a specified period. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Report Class Sales` Integration name: **QUICKBOOKS\_GET\_REPORT\_CLASS\_SALES** Generate a ClassSales report in QuickBooks showing sales amounts grouped by class. Use when you need to analyze sales performance by class tracking categories. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `class_ids` | array | | — | One or more comma separated class IDs to filter the report. If not provided, the report includes all classes. Each ID should be the Class.Id value from the Class object. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Report Customer Income` Integration name: **QUICKBOOKS\_GET\_REPORT\_CUSTOMER\_INCOME** Generate a customer income report in QuickBooks showing revenue by customer. Use when you need to analyze income generated from each customer over a specified period. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `end_date` | string | | — | Report end date in YYYY-MM-DD format. Use together with start\_date to specify a custom date range. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `start_date` | string | | — | Report start date in YYYY-MM-DD format. Use together with end\_date to specify a custom date range. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value from the Customer object (e.g., \['1', '2', '10']). | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Report Customer Sales` Integration name: **QUICKBOOKS\_GET\_REPORT\_CUSTOMER\_SALES** Generate a customer sales report in QuickBooks showing sales transactions and totals for customers. Can filter by specific customers, date ranges, and accounting method. Returns a hierarchical report with customer names, IDs, and their sales amounts. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `end_date` | string | | — | Report end date in YYYY-MM-DD format. Use together with start\_date to specify a custom date range. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `start_date` | string | | — | Report start date in YYYY-MM-DD format. Use together with end\_date to specify a custom date range. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value from the Customer object (e.g., \['1', '2', '10']). | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Report Department Sales` Integration name: **QUICKBOOKS\_GET\_REPORT\_DEPARTMENT\_SALES** Generate a department sales report in QuickBooks showing sales data broken down by department. Use when you need to analyze sales performance across different departments within a date range. Note: Department tracking must be enabled in the QuickBooks company file for this report to return data. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | `end_date` | string | | — | End date for the report period in YYYY-MM-DD format. Use this with start\_date to specify a custom date range, or use date\_macro for predefined ranges. | | `date_macro` | string | | — | Predefined date range for the report (e.g., 'This Month', 'Last Quarter'). Use this as an alternative to specifying start\_date and end\_date explicitly. | | `sort_order` | string | | — | The sort order for the report results (ascend or descend). | | `start_date` | string | | — | Start date for the report period in YYYY-MM-DD format. Use this with end\_date to specify a custom date range, or use date\_macro for predefined ranges. | | `department_ids` | array | | — | List of department IDs to filter the report. Filters report contents to include information for specified departments if configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report (Cash or Accrual). | | `summarize_column_by` | string | | — | The criteria by which to group the report results (e.g., Total, Month, Quarter). | *** ### `Quickbooks Get Report Item Sales` Integration name: **QUICKBOOKS\_GET\_REPORT\_ITEM\_SALES** Generate an ItemSales report showing sales data for products and services. Use when you need to analyze sales performance by item including quantity sold, revenue, COGS, and gross margin. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `item_ids` | array | | — | List of item IDs to filter the report. If not provided, the report includes all items. Each ID should be the Item.Id value from the Item object (e.g., \['1', '2', '10']). | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Reports` Integration name: **QUICKBOOKS\_GET\_REPORTS** Retrieve QuickBooks reports such as TransactionList, BalanceSheet, ProfitAndLoss, and others. Use when you need to access standardized financial or transaction reports with flexible filtering options. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `vendor` | string | | `"5"` | Vendor ID or comma-separated list of vendor IDs to filter the report. Only transactions related to these vendors will be included. Use Vendor.Id value from the Vendor object. | | `cleared` | string | | `"All"` | Filter for transaction cleared status. Options: 'All', 'Cleared', 'Uncleared', 'Reconciled'. Note that 'cleared' can only be used as a filter parameter, not as a column in the result. | | `columns` | string | | `"tx_date,txn_type,amount"` | Comma-separated list of column types to include in the report. For example: 'tx\_date,txn\_type,doc\_num,name,memo,account,amount'. If not specified, the report uses default columns. | | `sort_by` | string | | `"tx_date"` | Column type to use for sorting report rows. Common values include 'tx\_date', 'txn\_type', 'amount', etc. Must be a column that exists in the report. | | `customer` | string | | `"1"` | Customer ID or comma-separated list of customer IDs to filter the report. Only transactions related to these customers will be included. Use Customer.Id value from the Customer object. | | `end_date` | string | | `"2024-12-31"` | Report end date in YYYY-MM-DD format. Used to filter transactions or data up to this date. If not provided, the report uses its default end date or date\_macro setting. | | `group_by` | string | | `"Customer"` | Column type to use for grouping report rows. Common values include 'Customer', 'Vendor', 'Account', etc. Groups transactions by the specified entity type. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `start_date` | string | | `"2024-01-01"` | Report start date in YYYY-MM-DD format. Used to filter transactions or data from this date onwards. If not provided, the report uses its default start date or date\_macro setting. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `report_name` | string | ✅ | `"TransactionList"` | The name of the report to retrieve. For example: 'TransactionList', 'BalanceSheet', 'ProfitAndLoss', 'CashFlow', etc. This is the report type identifier used in the QuickBooks API endpoint. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Report Trial Balance` Integration name: **QUICKBOOKS\_GET\_REPORT\_TRIAL\_BALANCE** Generate a Trial Balance report showing account debits, credits, and balances for a specified period. Use when you need to verify that total debits equal total credits across all accounts for accounting reconciliation. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `end_date` | string | | — | Report end date in YYYY-MM-DD format. If not provided, defaults to today's date. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `start_date` | string | | — | Report start date in YYYY-MM-DD format. If not provided, defaults to the start of the current fiscal year. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks Get Sales Receipt` Integration name: **QUICKBOOKS\_GET\_SALES\_RECEIPT** Tool to fetch a QuickBooks sales receipt by ID. Use when needing full sales receipt details including customer info, line items, payment details, and metadata. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ------- | ----------------------------------------------- | | `minorversion` | integer | | `65` | API minor version to use for the request | | `sales_receipt_id` | string | ✅ | `"26"` | ID of the sales receipt to read from QuickBooks | *** ### `Quickbooks Get Salesreceipt Pdf` Integration name: **QUICKBOOKS\_GET\_SALESRECEIPT\_PDF** Tool to download a QuickBooks sales receipt as a PDF file. Use when you need to retrieve the printable PDF version of a sales receipt. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------ | | `minorversion` | string | | `"70"` | API minor version to use for the request (e.g., '70', '75'). If not specified, uses the default API version. | | `sales_receipt_id` | string | ✅ | `"31"` | The ID of the sales receipt to retrieve as PDF (e.g., '31', '123'). | *** ### `Quickbooks Get Tax Rate` Integration name: **QUICKBOOKS\_GET\_TAX\_RATE** Tool to read details of a specific tax rate by ID in QuickBooks Online. Use when you need to retrieve information about a tax rate. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ---------------------------------------- | | `tax_rate_id` | string | ✅ | `"1"` | The ID of the tax rate to retrieve. | | `minorversion` | integer | | `65` | API minor version to use for the request | *** ### `Quickbooks Get Term` Integration name: **QUICKBOOKS\_GET\_TERM** Read details of a specific payment term by ID in QuickBooks Online. Terms define payment conditions like Net 30 or Due on Receipt. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------- | --------------------------------------- | | `term_id` | string | ✅ | — | The ID of the payment term to retrieve. | *** ### `Quickbooks Get Time Activity` Integration name: **QUICKBOOKS\_GET\_TIME\_ACTIVITY** Tool to read details of a specific time activity by ID in QuickBooks Online. Returns complete time tracking information including employee/vendor reference, hours worked, billing rate, and associated customer. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | -------------- | ----------------------------------------------------------- | | `minorversion` | integer | | `65` | Optional API minor version parameter to use for the request | | `time_activity_id` | string | ✅ | `"1073741824"` | The unique identifier of the time activity to retrieve | *** ### `Quickbooks Get Transaction List Report` Integration name: **QUICKBOOKS\_GET\_TRANSACTION\_LIST\_REPORT** Get the Transaction List report showing all transactions in the company. Use when you need a comprehensive view of all transactions with flexible filtering by date, customer, vendor, account, or other criteria. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------ | :------: | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `cleared` | string | | `"All"` | Filter for transaction cleared status. Options: 'All', 'Cleared', 'Uncleared', 'Reconciled'. Note that 'cleared' can only be used as a filter parameter, not as a column in the result. | | `columns` | string | | `"date,transaction_type,number,name,memo,account,amount"` | Comma-separated list of columns to include in the report. Supports both user-friendly names and QuickBooks API identifiers: date/tx\_date (Date), transaction\_type/txn\_type (Transaction Type), number/num/doc\_num (Number), name (Name), memo/description (Memo/Description), account/account\_name (Account), amount/subt\_nat\_amount (Amount), net\_amount (Net Amount), split (Split), balance (Balance), customer (Customer), vendor (Vendor), employee (Employee), product\_service (Product/Service), quantity (Quantity), rate (Rate), class (Class), department/dept (Department), location (Location). If not specified, report uses default columns. | | `sort_by` | string | | `"date"` | Column to sort report rows by. Supports both user-friendly names (date, transaction\_type, amount, account, etc.) and QuickBooks API identifiers (tx\_date, txn\_type, subt\_nat\_amount, account\_name, etc.). Must be a column that exists in the report. | | `end_date` | string | | `"2024-12-31"` | Report end date in YYYY-MM-DD format. Used to filter transactions up to this date. If not provided, the report uses its default end date or date\_macro setting. | | `group_by` | string | | `"Customer"` | Column type to use for grouping report rows. Common values include 'Customer', 'Vendor', 'Account', etc. Groups transactions by the specified entity type. | | `class_ids` | array | | — | List of class IDs to filter the report. If not provided, the report includes all classes. Each ID should be the Class.Id value (e.g., \['1', '2']). | | `date_macro` | string | | — | Predefined date range for the report. Use if you want the report to cover a standard report date range; otherwise, use start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order for rows (ascending or descending). Default is ascending. | | `start_date` | string | | `"2024-01-01"` | Report start date in YYYY-MM-DD format. Used to filter transactions from this date onwards. If not provided, the report uses its default start date or date\_macro setting. | | `vendor_ids` | array | | — | List of vendor IDs to filter the report. If not provided, the report includes all vendors. Each ID should be the Vendor.Id value from the Vendor object (e.g., \['5', '8', '12']). | | `account_ids` | array | | — | List of account IDs to filter the report. If not provided, the report includes all accounts. Each ID should be the Account.Id value from the Account object (e.g., \['1', '35', '82']). | | `customer_ids` | array | | — | List of customer IDs to filter the report. If not provided, the report includes all customers. Each ID should be the Customer.Id value from the Customer object (e.g., \['1', '2', '10']). | | `department_ids` | array | | — | List of department IDs to filter the report. If not provided, the report includes all departments. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report (Cash or Accrual). | *** ### `Quickbooks Get Transfer` Integration name: **QUICKBOOKS\_GET\_TRANSFER** Tool to fetch a QuickBooks transfer by ID. Use when needing to retrieve transfer details including from/to account references and transfer amount. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------- | | `transfer_id` | string | ✅ | `"1"` | ID of the transfer to retrieve from QuickBooks | | `minorversion` | integer | | `65` | API minor version to use for the request (e.g., 65, 70, 75). If not specified, uses the default from headers. | *** ### `Quickbooks Get Vendor Credit` Integration name: **QUICKBOOKS\_GET\_VENDOR\_CREDIT** Tool to fetch a QuickBooks vendor credit by ID. Use when needing to retrieve vendor credit details including vendor reference, line items, amounts, and balance status. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------- | | `minorversion` | integer | | `65` | API minor version to use for the request (e.g., 65, 70, 75). If not specified, uses the default from headers. | | `vendor_credit_id` | string | ✅ | `"27"` | ID of the vendor credit to retrieve from QuickBooks | *** ### `Quickbooks Get Vendor Expenses Report` Integration name: **QUICKBOOKS\_GET\_VENDOR\_EXPENSES\_REPORT** Retrieve a vendor expenses report from QuickBooks showing expense transactions by vendor. This report displays the total expenses incurred for each vendor, providing a detailed view of vendor-related spending. Filter by specific vendors, date ranges, payment status, and customize with various grouping and sorting options. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `qzurl` | string | | — | Specifies whether Quick Zoom URL information should be generated for rows in the report. | | `appaid` | string | | — | Filters vendors by payment status. Use 'All' for all vendors, 'Paid' for vendors with fully paid balances, or 'Unpaid' for vendors with outstanding balances. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `vendor_ids` | array | | — | Filters report contents to include information for specified vendors. Supported Values: One or more comma separated vendor IDs as returned in the attribute, Vendor.Id, of the Vendor object response code. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** ### `Quickbooks List Cards` Integration name: **QUICKBOOKS\_LIST\_CARDS** Tool to retrieve all payment cards on file for a customer in QuickBooks Payments API. Use when needing to list saved payment methods for a customer. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `customer_id` | string | ✅ | `"00205184c555f1660c42d19c2d324f86ac3567"` | The QuickBooks Payments V4IDPseudonym identifier for the customer. This is different from the QuickBooks Online customer ID - use the V4IDPseudonym field from the customer object. | *** ### `Quickbooks List Departments` Integration name: **QUICKBOOKS\_LIST\_DEPARTMENTS** Query Department entities in QuickBooks using SQL-like syntax. Use when you need to list departments or filter departments by criteria like active status, name patterns, or parent relationships. Supports WHERE clauses, pattern matching (LIKE with %), ORDERBY, and pagination. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `query` | string | | `"SELECT * FROM Department"` | SQL-like query string to filter and retrieve Department entities ONLY. IMPORTANT: This tool queries the Department entity exclusively - do NOT use it to query other entities. For querying other entity types, use their respective query tools. Query syntax: SELECT \[fields] FROM Department \[WHERE conditions] \[ORDERBY field] \[STARTPOSITION n] \[MAXRESULTS n] NOTE: QuickBooks API returns ALL fields with values regardless of SELECT clause - field projections are not supported. You can write 'SELECT Id, Name' but the API will return all available fields anyway. Commonly queryable Department fields: Id, Name, Active, FullyQualifiedName, SubDepartment, ParentRef, SyncToken. Supports: - WHERE clauses with operators (=, <, >, <=, >=, IN) - LIKE operator with % wildcard - Boolean operators (AND, OR) - ORDERBY for sorting - Pagination with MAXRESULTS (max 1000, default 100) and STARTPOSITION - Aggregate functions (COUNT) | *** ### `Quickbooks List Invoices` Integration name: **QUICKBOOKS\_LIST\_INVOICES** Tool to list invoices via QuickBooks Query endpoint. Use when retrieving invoices with optional pagination and custom fields. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------- | :------: | ------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | `fields` | array | | `["Id","DocNumber","TotalAmt"]` | List of fields to select in the query. Defaults to \['Id','SyncToken','DocNumber','TotalAmt','Balance','TxnDate']. | | `max_results` | integer | | `50` | Maximum number of records to return; default 50, max 1000. | | `start_position` | integer | | `1` | Starting position for pagination within the result set. Default is 1. | *** ### `Quickbooks Query Account` Integration name: **QUICKBOOKS\_QUERY\_ACCOUNT** Query Account entities in QuickBooks using SQL-like syntax. IMPORTANT: Queries the Account entity ONLY (chart of accounts). For other entities (Purchase, Invoice, Bill, Payment, etc.), use their respective query actions. NOTE: API returns ALL fields with values regardless of SELECT clause (projections not supported). CRITICAL RESTRICTIONS: Parentheses and OR operator are NOT supported. Use IN operator for multiple values: WHERE AccountType IN ('Bank', 'Credit Card') Supports: WHERE clauses (=, <, >, LIKE, IN), AND operator, pattern matching (%), ORDER BY, pagination (MAXRESULTS up to 1000, STARTPOSITION), COUNT. Common fields: Id, Name, AccountType, AccountSubType, Classification, Active, FullyQualifiedName, CurrentBalance, AcctNum, Description, SubAccount. Examples: - SELECT \* FROM Account WHERE AccountType = 'Expense' MAXRESULTS 100 - SELECT \* FROM Account WHERE Active = true ORDER BY Name - SELECT \* FROM Account WHERE AccountType IN ('Bank', 'Credit Card') #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `query` | string | ✅ | `"SELECT * FROM Account"` | SQL-like query string to filter and retrieve Account entities ONLY. Do NOT use for other entities (Purchase, Invoice, Bill, etc.) - use their respective query tools. Query syntax: SELECT \[fields] FROM Account \[WHERE conditions] \[ORDER BY field] \[STARTPOSITION n] \[MAXRESULTS n] CRITICAL SYNTAX RESTRICTIONS: - Parentheses for grouping are NOT supported - OR operator is NOT supported - use IN instead - Use: WHERE Active = true AND AccountType IN ('Bank', 'Credit Card') NOTE: QuickBooks API returns ALL fields regardless of SELECT clause. Commonly queryable fields: Id, Name, AccountType, AccountSubType, Classification, Active, FullyQualifiedName, CurrentBalance, AcctNum, Description, SubAccount. Supports: - WHERE with operators (=, <, >, <=, >=, IN) - LIKE with % wildcard - AND only (no OR - use IN for multiple values) - ORDER BY for sorting (MUST be two words, not 'ORDERBY'). Sortable fields: Name, Id. Non-sortable: AccountType, AccountSubType, Classification, and others. - MAXRESULTS (max 1000, default 100) and STARTPOSITION - COUNT | *** ### `Quickbooks Query Attachable` Integration name: **QUICKBOOKS\_QUERY\_ATTACHABLE** Query Attachable entities in QuickBooks using SQL-like syntax. Use when you need to retrieve multiple attachables or search for specific file attachments. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `query` | string | | `"SELECT * FROM Attachable"` | SQL-like query string to filter and retrieve Attachable entities ONLY. IMPORTANT: This tool queries the Attachable entity exclusively - do NOT use it to query other entities like Purchase, Invoice, Bill, Payment, etc. For querying other entity types, use their respective query tools. Query syntax: SELECT \[fields] FROM Attachable \[WHERE conditions] \[ORDERBY field] \[STARTPOSITION n] \[MAXRESULTS n] NOTE: QuickBooks API returns ALL fields with values regardless of SELECT clause - field projections are not supported. You can write 'SELECT Id, FileName' but the API will return all available fields anyway. Commonly queryable Attachable fields: Id, FileName, Note, Category, ContentType, Size, FileAccessUri, TempDownloadUri. Supports: - WHERE clauses with operators (=, <, >, <=, >=, IN) - LIKE operator with % wildcard - Boolean operators (AND, OR) - ORDERBY for sorting - Pagination with MAXRESULTS (max 1000, default 100) and STARTPOSITION - Aggregate functions (COUNT) | *** ### `Quickbooks Query Entities` Integration name: **QUICKBOOKS\_QUERY\_ENTITIES** Execute SQL-like queries on QuickBooks Online entities. Supports all entity types (Customer, Invoice, Bill, Payment, Purchase, Account, etc.) with WHERE clauses, pattern matching, ordering, and pagination. IMPORTANT: Many fields are NOT queryable in WHERE clauses including PrivateNote, AccountRef, CurrencyRef, DepartmentRef, ClassRef, etc. Use queryable fields like Id, TxnDate, PaymentType, DisplayName instead. For non-queryable field filtering, query by date range and filter client-side. See parameter description for full list of queryable vs non-queryable fields. Use entity-specific query tools when available for typed responses. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `query` | string | ✅ | `"SELECT * FROM Customer MAXRESULTS 5"` | SQL-like query string to retrieve data from QuickBooks Online entities. Generic query tool supporting all entity types: Customer, Invoice, Bill, Payment, Purchase, Account, Vendor, Employee, Item, and more. Query syntax: SELECT \[fields] FROM \[EntityName] \[WHERE conditions] \[ORDERBY field] \[STARTPOSITION n] \[MAXRESULTS n] NOTE: QuickBooks API returns ALL fields regardless of SELECT clause - field projections are not supported. Supported operators: = < > <= >= != LIKE (% wildcard) IN AND ORDERBY MAXRESULTS (max 1000, default 100) STARTPOSITION COUNT. CRITICAL: OR operator is NOT supported for most QuickBooks entities (including Item, Account, and many others). If you attempt to use OR in a query, the API will return a QueryParserError. Use IN operator instead for matching multiple specific values (e.g., 'WHERE Id IN ("1", "2", "3")' instead of 'WHERE Id = "1" OR Id = "2"'). For pattern matching across multiple terms with LIKE (e.g., finding items containing 'Larkspur' in FullyQualifiedName OR Description), query without the WHERE clause or with a broader filter, then filter results client-side. CRITICAL QUERY FIELD RESTRICTIONS: Top-level entity references like CustomerRef, VendorRef are queryable on transactions (e.g., 'SELECT \* FROM Invoice WHERE CustomerRef = "123"'). NON-QUERYABLE fields: PrivateNote, AccountRef, CurrencyRef, DepartmentRef, ClassRef on any entity; nested references like Line\[].ItemRef. Using these in WHERE causes QueryValidationError. WORKAROUND: Query by date range and filter results client-side, or use entity-specific GET actions. Purchase entity queryable fields: Id, TxnDate, PaymentType, DocNumber, TotalAmt, PrintStatus. NOT queryable: AccountRef, CurrencyRef, DepartmentRef, ClassRef, PrivateNote. These lists are common examples, not exhaustive. Consult the QuickBooks API documentation or test incrementally to discover all queryable fields. Reference fields are generally NOT queryable unless explicitly documented. IMPORTANT: Use entity-specific query tools when available (e.g., QueryAccount for Account entities) as they provide typed responses. This generic tool returns untyped data and should be used only when no specific query tool exists. | *** ### `Quickbooks Read Account` Integration name: **QUICKBOOKS\_READ\_ACCOUNT** Read an account in QuickBooks with the given account ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | ---------------------------- | | `account_id` | string | ✅ | — | ID of the account to be read | *** ### `Quickbooks Read Class` Integration name: **QUICKBOOKS\_READ\_CLASS** Read details of a specific class by ID in QuickBooks Online. Classes allow categorization of transactions. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------- | | `class_id` | string | ✅ | — | ID of the class to be read | | `minorversion` | integer | | `75` | API minor version to use for the request. If not provided, uses the version from metadata headers. | *** ### `Quickbooks Read Customer` Integration name: **QUICKBOOKS\_READ\_CUSTOMER** Read a customer in QuickBooks with the given customer ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------- | | `customer_id` | string | ✅ | — | ID of the customer to be read Must be the QuickBooks-assigned numeric system ID, not a customer display name or free-text identifier. | *** ### `Quickbooks Read Employee` Integration name: **QUICKBOOKS\_READ\_EMPLOYEE** Read an employee's details in QuickBooks with the given employee ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ------- | ---------------------------------- | | `employee_id` | string | ✅ | — | The ID of the employee to be read. | *** ### `Quickbooks Read Invoice` Integration name: **QUICKBOOKS\_READ\_INVOICE** Tool to fetch a QuickBooks invoice by ID or the most recent if no ID provided. Use when needing full invoice details including metadata and sync token. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | --------- | ---------------------------------------------------------------------- | | `invoice_id` | string | | `"12345"` | ID of the invoice to read; if not provided, fetches the latest invoice | | `minorversion` | integer | | `65` | API minor version to use for the request | *** ### `Quickbooks Read Vendor` Integration name: **QUICKBOOKS\_READ\_VENDOR** Read a vendor in QuickBooks with the given vendor ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------ | :------: | ------- | --------------------------- | | `vendor_id` | string | ✅ | — | ID of the vendor to be read | *** ### `Quickbooks Send Credit Memo` Integration name: **QUICKBOOKS\_SEND\_CREDIT\_MEMO** Tool to send a credit memo to a specified email address. Use when you need to email a credit memo to a customer. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------- | :------: | -------------------- | ---------------------------------------------------------------------------------------------------------------- | | `send_to` | string | | `"test@example.com"` | Optional email address to send the credit memo to. If not provided, sends to the customer's default email. | | `minorversion` | integer | | — | QuickBooks API minor version number (e.g., 65, 70, 75). If not specified, uses the default version from headers. | | `credit_memo_id` | string | ✅ | `"14"` | The ID of the credit memo to send | *** ### `Quickbooks Update Attachable` Integration name: **QUICKBOOKS\_UPDATE\_ATTACHABLE** Tool to update an existing attachable in QuickBooks Online. Use when you need to modify attachable properties like note text or entity references. Requires the attachable Id and current SyncToken for optimistic locking. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------ | | `Id` | string | ✅ | — | The ID of the attachable to update. | | `Lat` | string | | — | Latitude coordinate where the file was created. | | `Tag` | string | | — | Tag string for the attachable. | | `Long` | string | | — | Longitude coordinate where the file was created. | | `Note` | string | | — | Note text for the attachable. | | `Category` | string | | — | Category of the attachable (e.g., Image, Document, Sound, Receipt, Other, etc.). | | `PlaceName` | string | | — | Name of the place where the file was created. | | `SyncToken` | string | ✅ | — | The current SyncToken value for optimistic locking. Must match the latest value from QuickBooks. | | `AttachableRef` | array | | — | Array of references to entities this attachable is linked to. | *** ### `Quickbooks Update Company Info` Integration name: **QUICKBOOKS\_UPDATE\_COMPANY\_INFO** Tool to update company information in QuickBooks Online. Use when you need to update company details like name, address, or contact information. Requires Id and SyncToken from a previous read operation. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------- | | `Id` | string | ✅ | — | Unique identifier of the company info object. Typically '1' for the company record. | | `Email` | object | | — | Email address structure. | | `Country` | string | | — | Country where the company is registered (e.g., US, CA, UK). | | `WebAddr` | object | | — | Website address structure. | | `LegalAddr` | object | | — | Company address structure for update requests. | | `LegalName` | string | | — | Legal name of the company. | | `NameValue` | array | | — | List of name-value pairs containing additional company attributes. | | `SyncToken` | string | ✅ | — | Version number for optimistic locking. Must match current value to prevent concurrent update conflicts. | | `CompanyAddr` | object | ✅ | — | Company address object. Required for updates and must include PostalCode. | | `CompanyName` | string | | — | Name of the company. Optional for partial updates. | | `PrimaryPhone` | object | | — | Telephone number structure. | | `CompanyStartDate` | string | | — | Date when the company started business, in YYYY-MM-DD format. | | `SupportedLanguages` | string | | — | Comma-separated list of languages supported by the company. | | `FiscalYearStartMonth` | string | | — | Starting month of the company's fiscal year (e.g., January, February). | | `CustomerCommunicationAddr` | object | | — | Company address structure for update requests. | | `CustomerCommunicationEmailAddr` | object | | — | Email address structure. | *** ### `Quickbooks Update Department` Integration name: **QUICKBOOKS\_UPDATE\_DEPARTMENT** Tool to update an existing department in QuickBooks Online. Use when you need to modify department details. Requires the department Id and current SyncToken to prevent concurrent update conflicts. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------------------- | | `Id` | string | ✅ | — | The unique identifier of the department to update. Required for update operations. | | `Name` | string | ✅ | — | Updated name of the department. Maximum length is 100 characters. | | `Active` | boolean | | — | Whether the department is active. Inactive departments may be hidden from most display purposes. | | `sparse` | boolean | | — | Set to true to perform a partial update (only specified fields are updated). Defaults to true for update operations. | | `ParentRef` | object | | — | Reference to the parent department if this is a sub-department. Contains 'value' (ID) and optionally 'name'. | | `SyncToken` | string | ✅ | — | Version token for optimistic locking, obtained from a prior GET request. Prevents concurrent update conflicts. | | `SubDepartment` | boolean | | — | Whether this department is a sub-department. If true, ParentRef should be provided. | *** ### `Quickbooks Update Full Invoice` Integration name: **QUICKBOOKS\_UPDATE\_FULL\_INVOICE** Tool to fully replace an Invoice. Use when you need to update all aspects of an existing invoice in a single operation. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------- | ------- | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------- | | `invoice` | object | ✅ | — | Full Invoice JSON payload to update; must include Id and SyncToken. Any writable field omitted will be cleared. Do not set sparse=true. | | `requestid` | string | | — | Optional idempotency key (<=50 chars) to prevent duplicate writes on retries. | | `minorversion` | integer | | — | Optional QuickBooks API minorversion to access newer fields (e.g., 63). | *** ### `Quickbooks Update Payment Method` Integration name: **QUICKBOOKS\_UPDATE\_PAYMENT\_METHOD** Tool to update an existing payment method in QuickBooks Online. Use when you need to modify the name, status, or type of a payment method. Requires the payment method Id and current SyncToken. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------- | :------: | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | `Id` | string | ✅ | `"2"` | Unique identifier of the payment method to update. Required for updates. | | `Name` | string | ✅ | `"Business Check-Updated"` | User-recognizable name for the payment method (e.g., 'Business Check', 'Cash', 'Credit Card'). Maximum length is 31 characters. | | `Type` | string | | `"NON_CREDIT_CARD"` | Type of payment method. Valid values: 'CREDIT\_CARD', 'NON\_CREDIT\_CARD'. If not specified, defaults to 'NON\_CREDIT\_CARD'. | | `Active` | boolean | | — | Whether the payment method is active. Default is true. | | `SyncToken` | string | ✅ | `"0"` | Version number for optimistic locking. Must match the current version in QuickBooks to prevent conflicts. Required for updates. | *** ### `Quickbooks Update Preferences` Integration name: **QUICKBOOKS\_UPDATE\_PREFERENCES** Update company preferences in QuickBooks Online. Requires Id and SyncToken from a previous read. Use sparse=true for partial updates (only specified fields are changed) or sparse=false/omitted for full replacement. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------- | | `Id` | string | ✅ | — | ID of the preferences object, typically '1' for company preferences. | | `sparse` | boolean | | — | Set to true for sparse (partial) update, updating only provided fields. Set to false or omit for full update. | | `TaxPrefs` | object | | — | Tax preferences. | | `SyncToken` | string | ✅ | — | Version number for optimistic locking. Required to prevent concurrent update conflicts. | | `OtherPrefs` | object | | — | Other miscellaneous preferences. | | `ReportPrefs` | object | | — | Report preferences. | | `minorversion` | integer | | — | QuickBooks API minor version to use (e.g., 65, 70, 75). Uses default if not specified. | | `CurrencyPrefs` | object | | — | Currency preferences. | | `SalesFormsPrefs` | object | | — | Sales forms preferences. | | `TimeTrackingPrefs` | object | | — | Time tracking preferences. | | `EmailMessagesPrefs` | object | | — | Email message preferences for various transaction types. | | `AccountingInfoPrefs` | object | | — | Accounting information preferences. | | `ProductAndServicesPrefs` | object | | — | Product and services preferences. | | `VendorAndPurchasesPrefs` | object | | — | Vendor and purchases preferences. | *** ### `Quickbooks Update Sparse Invoice` Integration name: **QUICKBOOKS\_UPDATE\_SPARSE\_INVOICE** Tool to perform a sparse update of an existing invoice. Use when you need to update only specific invoice fields without overwriting other data. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------- | -------------------------------------------------------------------------- | | `invoice` | object | ✅ | — | Invoice object containing Id, SyncToken, sparse flag, and fields to update | *** ### `Quickbooks Update Term` Integration name: **QUICKBOOKS\_UPDATE\_TERM** Tool to update an existing payment term in QuickBooks Online. Use when you need to modify the name, status, type, or payment conditions of a payment term. Requires the payment term Id and current SyncToken. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------- | ------- | :------: | ------------ | ---------------------------------------------------------------------------------------------------------------------------------- | | `Id` | string | ✅ | `"1"` | Unique identifier of the payment term to update. Required for updates. | | `Name` | string | ✅ | `"Net 30"` | User-recognizable name for the payment term (e.g., 'Net 30', 'Due on receipt'). Maximum length 31 characters. | | `Type` | string | ✅ | `"STANDARD"` | Type of the sales term. Valid values: 'STANDARD' (if dueDays is not null) or 'DATEDRIVEN' (if dueDays is null). | | `Active` | boolean | | — | Whether the payment term is active. Default is true. | | `DueDays` | integer | | `0` | Number of days until payment is due. If specified, Type should be 'STANDARD'. Use 0 for 'Due on receipt'. | | `SyncToken` | string | ✅ | `"0"` | Version number for optimistic locking. Must match the current version in QuickBooks to prevent conflicts. Required for updates. | | `DiscountDays` | integer | | `0` | Number of days within which payment must be made to receive the discount. Used with discount\_percent for early payment discounts. | | `DayOfMonthDue` | integer | | — | Specific day of the month when payment is due. Used for DATEDRIVEN type terms. Valid range: 1-31. | | `DiscountPercent` | number | | `0` | Discount percentage available if paid within the discount days. Valid range: 0 to 100. | | `DueNextMonthDays` | integer | | — | Number of days in the month before the due date shifts to the next month. Used for DATEDRIVEN type terms. | | `DiscountDayOfMonth` | integer | | — | Specific day of the month when discount is available. Used for DATEDRIVEN type terms. Valid range: 1-31. | *** ### `Quickbooks Update Transfer` Integration name: **QUICKBOOKS\_UPDATE\_TRANSFER** Tool to update an existing transfer in QuickBooks Online. Use when you need to modify a transfer between accounts. Requires the transfer Id and current SyncToken to prevent concurrent update conflicts. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------ | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------- | | `Id` | string | ✅ | — | The unique identifier of the transfer to update. Required for update operations. | | `Amount` | string | ✅ | — | The monetary amount to transfer between accounts. Specified as a string (e.g., '35.00'). | | `TxnDate` | string | | — | The date of the transfer transaction in YYYY-MM-DD format. Defaults to current date if not specified. | | `SyncToken` | string | ✅ | — | Version token for optimistic locking, obtained from a prior GET request. Prevents concurrent update conflicts. | | `CurrencyRef` | object | | — | Reference to a currency for multi-currency transactions. | | `PrivateNote` | string | | — | Internal note about the transfer that is not visible to customers. | | `ExchangeRate` | — | | — | Exchange rate for multi-currency transactions. Default is 1 for home currency. Only applicable when using non-home currency. | | `ToAccountRef` | object | ✅ | — | Reference to the destination account to which funds are transferred. | | `DepartmentRef` | object | | — | Reference to a department for location tracking. | | `FromAccountRef` | object | ✅ | — | Reference to the source account from which funds are transferred. | *** ### `Quickbooks Vendor Balance Detail` Integration name: **QUICKBOOKS\_VENDOR\_BALANCE\_DETAIL** Generate a balance detail report for a vendor in QuickBooks with the given vendor ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `arpaid` | string | | — | Filter by payment status. Use 'All' for all balances, 'Paid' for fully paid balances, or 'Unpaid' for outstanding balances. | | `columns` | string | | — | Column types to be shown in the report. Supported Values: bill\_addr, create\_by, create\_date, vend\_bill\_email, vend\_comp\_name, vend\_msg, vend\_phone\_other, vend\_tel, vend\_name, deliv\_addr, doc\_num\*, due\_date\*, last\_mod\_by, last\_mod\_date, memo\*, vendor\_sent\_state, ship\_addr, ship\_date, term\_name, tracking\_num, tx\_date\*, txn\_type\*. Additional columns with custom fields enabled: purchase\_vend1, purchase\_vend2, purchase\_vend3. Additional columns with location tracking enabled: dept\_name\* | | `sort_by` | string | | — | The column type used in sorting report rows. Specify a column type as defined with the columns query parameter. | | `term_ids` | array | | — | One or more comma separated term IDs. Filters report contents based on term or terms supplied. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `vendor_ids` | array | | — | One or more comma separated vendor IDs. Filters report contents to include information for specified vendors. | | `end_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `num_periods` | integer | | — | Number of aging periods to display in the report. Each period represents a time bucket for aging calculations (e.g., 0-30 days, 31-60 days). | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `aging_method` | string | | — | Method for calculating age of payables. 'Report\_Date' calculates age based on the report date, while 'Current' calculates age based on the current date. | | `aging_period` | integer | | — | Number of days per aging period. Default is typically 30 days. For example, setting this to 30 creates buckets like 0-30, 31-60, 61-90 days. | | `duedate_macro` | string | | — | Predefined date range of due dates for balances to include in the report; otherwise, use the start\_duedate and end\_duedate to cover an explicit report date range. | | `start_duedate` | string | | — | The range of dates over which receivables are due, in the format YYYY-MM-DD. start\_duedate must be less than end\_duedate. If not specified, all data is returned. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | *** ### `Quickbooks Vendor Balance Report` Integration name: **QUICKBOOKS\_VENDOR\_BALANCE\_REPORT** Retrieve a vendor balance report from QuickBooks showing outstanding balances for vendors. This report displays the total amount owed to each vendor, providing a summary of accounts payable. You can filter by specific vendors, date ranges, payment status, and customize the report with various grouping and sorting options. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `qzurl` | string | | — | Specifies whether Quick Zoom URL information should be generated for rows in the report. | | `appaid` | string | | — | Filters vendors by payment status. Use 'All' for all vendors, 'Paid' for vendors with fully paid balances, or 'Unpaid' for vendors with outstanding balances. | | `date_macro` | string | | — | Predefined date range. Use if you want the report to cover a standard report date range; otherwise, use the start\_date and end\_date to cover an explicit report date range. | | `sort_order` | string | | — | The sort order. | | `vendor_ids` | array | | — | Filters report contents to include information for specified vendors. Supported Values: One or more comma separated vendor IDs as returned in the attribute, Vendor.Id, of the Vendor object response code. | | `report_date` | string | | — | Start date to use for the report, in the format YYYY-MM-DD. | | `department_ids` | array | | — | One or more comma separated department IDs. Filters report contents to include information for specified departments if so configured in the company file. | | `accounting_method` | string | | — | The accounting method used in the report. | | `summarize_column_by` | string | | — | The criteria by which to group the report results. | *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.toolhouse.ai/toolhouse/integrations/quickbooks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.