[ Accounting ]
QuickBooks Desktop (via Conductor) integration for your workflows.
Connect QuickBooks Desktop (via Conductor) to Collabase once and use 8 actions and 2 triggers in your workflows. No code needed, hosted in Switzerland.
QuickBooks Desktop (via Conductor) in Collabase
Connect QuickBooks Desktop (via Conductor) to Collabase once and use 8 actions and 2 triggers in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Sync invoices, bills, customers, vendors and payments with QuickBooks Desktop through the Conductor API bridge.
How to connect it
- Open the integrations in the workspace settings.
- Choose QuickBooks Desktop (via Conductor) and connect your account.
- Add a trigger or an action to the workflow.
- In your Conductor dashboard, go to Settings → API Keys and copy your Secret Key.
- Under End-Users, select (or create) the end-user connected to this QuickBooks Desktop
- The end-user must have already completed Conductor's auth flow and installed the QuickBooks
- Top setup mistake — read before finishing step 3: when QuickBooks Desktop first asks to
QuickBooks Desktop (via Conductor) triggers
| Name | Description | Fields |
|---|---|---|
| New or Updated InvoiceChecks at intervals | Fires when an invoice is created or updated (e.g. line items, balance, or payment status changed) in QuickBooks Desktop. One event per invoice change, not create-only. | 0 |
| New PaymentChecks at intervals | Fires once when a new customer payment is recorded (Accounts Receivable) in QuickBooks Desktop — a "Receive Payment" transaction, e.g. from the Record Payment action's Customer Payment mode. Create-only: editing an existing payment does not re-fire it. Vendor bill payments (Accounts Payable) do not fire this trigger. | 0 |
QuickBooks Desktop (via Conductor) actions
| Name | Description | Fields |
|---|---|---|
| Upsert Customer | Creates a customer in QuickBooks Desktop, or updates it if one with the same name already exists. |
+ 4
|
| Upsert Vendor | Creates a vendor in QuickBooks Desktop, or updates it if one with the same name already exists. |
+ 4
|
| Create Invoice | Creates an invoice for a customer in QuickBooks Desktop. |
|
| Create Bill | Creates a vendor bill (accounts payable) in QuickBooks Desktop, expensed against one or more accounts. |
|
| Record Payment | Records a customer payment against open invoices, or a vendor bill payment by check or credit card, in QuickBooks Desktop. |
+ 6
|
| Query Transactions | Searches across all transaction types in QuickBooks Desktop (invoices, bills, payments, and more) with date and type filters. |
+ 1
|
| List Items | Lists Service and Non-Inventory items from QuickBooks Desktop, for finding the exact item name to use in Create Invoice's line items. |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Accounting ]
Related integrations
Tools that often share a workflow.
Questions about QuickBooks Desktop (via Conductor)
What can I automate with QuickBooks Desktop (via Conductor) in Collabase?
QuickBooks Desktop (via Conductor) brings 8 actions and 2 triggers, for example Upsert Customer, Upsert Vendor, Create Invoice, Create Bill and 4 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect QuickBooks Desktop (via Conductor) to Collabase?
You open the integrations in the workspace settings, choose QuickBooks Desktop (via Conductor) and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.
Can QuickBooks Desktop (via Conductor) start a workflow?
Yes. QuickBooks Desktop (via Conductor) provides 2 triggers, for example New or Updated Invoice and New Payment. The workflow runs as soon as the event happens.
Does the QuickBooks Desktop (via Conductor) integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.
