QuickBooks
Create invoices, manage customers, and sync accounting data with QuickBooks Online. In Appbricx, your workflows and server functions call it by name once it is connected.
What you can do
6 actions, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.
- Create InvoiceCreates an invoice in QuickBooks.
create_invoice - Create ExpenseCreates an expense transaction (purchase) in QuickBooks.
create_expense - Find CustomerSearch for a customer by display name in QuickBooks.
find_customer - Find InvoiceSearch for an invoice by its number in QuickBooks.
find_invoice - Find PaymentFinds an existing payment in QuickBooks.
find_payment - Custom API CallMake a custom API call to a specific endpoint
custom_api_call
Set it up
About two minutes, once per project or once for the whole workspace.
- Open Integrations in the builder
Backend panel, Integrations tab, then QuickBooks. To connect it for every project, use Workspace settings, Integrations.
- Sign in to QuickBooks
You sign in to QuickBooks and approve access. Appbricx keeps the tokens, encrypted, and refreshes them.
com.intuit.quickbooks.accounting
This uses an OAuth app: the platform's, or your own from the admin panel, and you can bring your own credentials.
- Call an action
From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.
Workflow // .workflow.js (native ctx) export async function run(ctx) { const res = await ctx.integrations.invoke("quickbooks", "create_invoice", { "customerRef": "<customerRef>", "lineItems": [] }); if (!res.success) throw new Error(res.error); ctx.log.info("QuickBooks answered", { output: res.output }); }
More in Finance and payments
QuickBooks and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.