[ QuickBooks / Invoicing ]

Won deal to QuickBooks invoice

When a deal closes in HubSpot or Salesforce, engini finds or creates the customer in QuickBooks Online and creates the invoice from the deal’s line items. An AI agent checks products and prices first. A scheduled run brings invoice and payment status back to the deal, so sales knows who has paid.

HubSpotSalesforceQuickBooksSlack
Read the QuickBooks guide →
A deal closes on Friday
  1. HubSpot logo
    Deal moved to Closed WonHubSpot, checked every 15 min
  2. Agent checks the dealproducts exist, prices agree
  3. QuickBooks logo
    Customer and invoice createdlines from the deal
  4. HubSpot logo
    Status back on the dealinvoice no., balance, paid
Illustration of the flow on this page, not a product screen.
What it does
Won deals become QuickBooks invoices; status returns to the CRM
Systems
HubSpot or Salesforce, QuickBooks Online, Slack or Teams
Built with
A workflow on the CRM trigger plus a scheduled read-back
Your control
Which deals, which items, what stops an invoice
[ 01 / The problem ]

Sales closes it. Someone re-types it.

Blurred landscape photo with the words Invoicing and the labels Trigger, Check, Create, Return

Small and mid-size teams often sell in HubSpot or Salesforce and bill from QuickBooks Online. Every won deal means creating the customer, copying the line items into an invoice, and later telling the account owner whether it was paid. HubSpot’s own help center notes the limits of its QuickBooks sync, such as a deal with several invoices showing only the latest one’s status (HubSpot).

Where invoicing slips

  • Invoices sent days after the deal closed.
  • Products or prices on the deal that QuickBooks does not have.
  • The same customer created twice under different names.
  • Reps who cannot see whether a customer has paid.

An agent between the CRM and QuickBooks

engini catches the closed deal (in real time from Salesforce, or as often as every 15 minutes from HubSpot), and an AI agent step reads the deal, its line items and the company, checks products and prices against QuickBooks, and finds the customer before creating one. Then it creates the invoice. Since QuickBooks has no engini triggers, a scheduled workflow reads invoice balances and writes status back to the deal.

[ 02 / How it works ]

Deal to invoice, and paid status back

01 / Trigger

The deal closes

A Salesforce outbound message, or a HubSpot deal update checked as often as every 15 minutes, starts the workflow.

02 / Check

Review before writing

An AI agent step reads the deal and its line items and checks products and prices against QuickBooks. Problems go to Slack or Teams.

03 / Create

Customer and invoice

It finds the customer, creates one only if none exists, and creates the invoice with the deal’s lines.

04 / Return

Status on the deal

A scheduled run reads invoice balances in QuickBooks and writes invoice number, balance and paid status to the deal.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
HubSpot or SalesforceDeal or opportunity, line items, company or accountReadUpdate
QuickBooksCustomers, itemsReadCreate
QuickBooksInvoices; balances on the way backCreateRead
Slack or TeamsNotes when a deal cannot be invoiced yetWrite

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the HubSpot logo, the engini mark and the QuickBooks logo joined by a thin line, labeled Closed Won: deal, check, invoice

Editorial image: closed won, invoice, paid.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when a HubSpot deal moves to Closed Won, read its line items and associated company, find the customer in QuickBooks by company name or create it, and create a QuickBooks invoice with the same line items. Write the invoice number to a deal property called qb_invoice_number.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect QuickBooks, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

How do HubSpot deals become QuickBooks invoices?

An engini trigger on updated deals starts a workflow when a deal reaches Closed Won. An AI agent checks it, and the workflow creates the customer if needed and the invoice in QuickBooks Online.

Does it work with Salesforce?

Yes. A Salesforce outbound message starts the same flow in real time when an opportunity closes.

Can reps see whether the customer paid?

Yes. A scheduled workflow reads invoice balances in QuickBooks and writes invoice number, balance and paid status to the deal.

What if a product is not in QuickBooks?

The agent stops before creating anything and posts the deal and the missing product to Slack or Teams.

Why is the status read on a schedule?

engini has no QuickBooks triggers, so changes in QuickBooks are read on the schedule you choose, for example every hour.