Smart, simple online accounting software for small business.
Changelog
19 versions
v1.8.0
Latest
- Rewrote the NewInvoice, UpdatedInvoice, NewCustomer and UpdatedCustomer triggers to use Appmixer listeners (context.addListener/removeListener) instead of shared service state, so webhook routing works through AuthHub's single shared endpoint. Webhook events are now delivered via context.triggerListeners filtered by realmId.
- Fixed webhook routing when a single payload carries more than one notification for the same company: entities are now merged per realm instead of the first notification being processed twice and the rest dropped. A notification without a dataChangeEvent no longer aborts the whole payload.
- Replaced the trigger output port definitions (dynamic source on the Customer triggers, options arrays on the Invoice triggers) with static JSON Schema including realistic example values, so the variable picker shows sample data for every field.
- Webhook signature verification accepts multiple verifier tokens (webhookVerifierToken as a comma-separated list and/or webhookVerifierTokenSandbox), so the Development (sandbox) and Production sections of the Intuit app can share one endpoint. The invalid-signature debug log no longer dumps the service configuration.
v1.7.0
- Added MakeApiCall component for performing arbitrary authorized API calls to the QuickBooks API.
v1.6.0
- Added test() (Flow Test Mode) to the NewInvoice, UpdatedInvoice, NewCustomer and UpdatedCustomer triggers.
v1.5.7
- Added output examples to component schemas.
v1.5.6
- Reduced icon size for better performance.
v1.5.5
- Added warning logs for deprecated minor versions.
v1.5.4
- Improve performance of receiving webhooks by eliminating wait for confirmation when message is sent to the New Customer, New Invoice, Updated Customer or Updated Invoice component.
v1.5.3
- CreateInvoice: fix input parameters.
v1.5.2
- Fixed an error when exporting records into a CSV file.
v1.5.1
- Fixed sandbox configuration to accurately determine and use the correct environment URLs based on the sandbox setting.
v1.5.0
- Added components: CreateCustomer.
v1.4.3
- Added components: NewInvoice, UpdatedInvoice, NewContact, UpdatedContact.
- Implemented webhook functionality.
- Added realmId to the Quickbooks account section when connecting a new component.
- Added missing outports in BillAddr and ShipAddr for ListCustomers, FindCustomers, UpdatedCustomer, NewCustomer, CreateInvoice, NewInvoice and UpdatedInvoice.
v1.3.0
- Added components: ListCustomers
- Improved error message when creating an invoice with no line items.
- Customer in CreateInvoice component is now selected from a list of existing customers.
v1.2.7
- Fixed exporting nested objects into CSV files.
v1.2.6
- Added components: ListVendors, CreateVendor, ListJournals, ListAccounts, ListClasses, CreateBill, GetBill, UpdateBill, AddAttachmentToBill
- Added an option in the backoffice to configure the base URL.
- Fixed Query component error when outputType is set to 'row'.
v1.1.2
- Fixed typos in quickbooks.accounting.Query component.json
v1.1.1
- Added an option in the backoffice to configure the base URL
v1.1.0
- Addressed issues with authentication flow and Query component output for improved functionality.
v1.0.0
- Initial version.
Authentication
| Type | Details |
|---|---|
| OAuth 2 |
Authentication Hub
Verified
This connector is globally authenticated and verified by Appmixer and is ready to use without registering your own OAuth application with the provider. Appmixer's Authentication Hub acts as an authentication proxy, so all OAuth-based connectors work out of the box. You can still use your own OAuth credentials (clientId and clientSecret) for enhanced customization or compliance — see the Connector Configuration section of the documentation. The Authentication Hub is enabled for all hosted Appmixer tenants; on self-managed installations it has to be explicitly set.
Scopes:
com.intuit.quickbooks.accounting
openid
profile
email
phone
address
|
Triggers
4Actions
17
Delete Bill
This operation deletes the bill object specified in the request body. Include a minimum of Bill.Id and Bill.SyncToken in the request body. You must unlink any linked transactions associated with the bill object before deleting it.