Skip to content
QuickBooks Desktop (via Conductor) logo

QuickBooks Desktop (via Conductor) integration

Sync invoices, bills, customers, vendors and payments with QuickBooks Desktop through the Conductor API bridge.

Actions
8
Triggers
2
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the QuickBooks Desktop (via Conductor) integration

Add the QuickBooks Desktop (via Conductor) piece to a flow, connect your account once, and the rest of the builder can read from it and write to it. Because the piece is open source you can run it on our cloud or self-host it, and combine QuickBooks Desktop (via Conductor) with 760+ other apps in the same flow.

Triggers

Start a flow the moment something happens in QuickBooks Desktop (via Conductor)

Each trigger below can start a flow on its own, either instantly or on a schedule.

  • New or Updated Invoice

    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.

  • New Payment

    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.

Actions

Everything Activepieces can do in QuickBooks Desktop (via Conductor)

Drop any of these into a flow and fill in the fields. No code is required.

  • Upsert Customer

    Creates a customer in QuickBooks Desktop, or updates it if one with the same name already exists.

    10 fields

  • Upsert Vendor

    Creates a vendor in QuickBooks Desktop, or updates it if one with the same name already exists.

    10 fields

  • Create Invoice

    Creates an invoice for a customer in QuickBooks Desktop.

    6 fields

  • Create Bill

    Creates a vendor bill (accounts payable) in QuickBooks Desktop, expensed against one or more accounts.

    6 fields

  • Record Payment

    Records a customer payment against open invoices, or a vendor bill payment by check or credit card, in QuickBooks Desktop.

    12 fields

  • Query Transactions

    Searches across all transaction types in QuickBooks Desktop (invoices, bills, payments, and more) with date and type filters.

    7 fields

  • 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.

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Use QuickBooks Desktop (via Conductor) in a flow

Connect QuickBooks Desktop (via Conductor) once and every trigger and action above is yours to drop into the builder, alongside 760+ other apps. Free to start, on our cloud or your own servers.

QuickBooks Desktop (via Conductor), answered.

Yes. Activepieces is open source and free to start, and the QuickBooks Desktop (via Conductor) piece is included on every plan, from the free cloud tier to any self-hosted deployment.

Add the QuickBooks Desktop (via Conductor) piece to a flow, then authenticate with Custom auth. Once connected, its 2 triggers and 8 actions are available anywhere in the builder.

"New or Updated Invoice" can start a flow that runs "Upsert Customer", and you can chain QuickBooks Desktop (via Conductor) together with any of 760+ other apps and AI steps in between.

Yes. Activepieces is fully self-hostable, so you can run the QuickBooks Desktop (via Conductor) piece on your own infrastructure with your connections and your data staying in your environment.

Yes. Every piece you connect can be exposed over one Activepieces MCP server, so Claude, Cursor, Windsurf or any MCP client can call QuickBooks Desktop (via Conductor) actions as tools.