Can it raise the invoice as well?

No, on purpose. This package stops at the customer record so finance keeps control of what is billed and when. The invoicing packages in the finance category pick up from the customer record this one creates, and the two can run on the same stage change.

What happens if QuickBooks is down when a deal closes?

The workflow stops at that step and the error workflow posts the deal ID and the API response to your error channel. Re-run the execution from n8n once QuickBooks is back. Nothing was written back to the deal, so the retry starts clean; a deal that did finish is skipped by the check in step two.

Our pipeline has two Closed Won stages. Does that work?

Yes. The filter node holds a list of stage IDs rather than a single value, and the setup guide shows where to find each pipeline's stage ID in HubSpot. Deals from a pipeline you leave out are ignored.

Does it run on Make or Zapier?

Not as shipped. The seven-step flow with a write-back and a separate error path is built for n8n. Make can reproduce it with its HubSpot, QuickBooks, ClickUp and Slack modules; ask if you need that rebuild.

Do I need a paid n8n plan?

Any n8n Cloud plan runs it, and so does a self-hosted instance, where the community edition costs nothing. Self-hosted needs a public URL, or a tunnel, so HubSpot can reach the webhook.

HQBCUSMade to order

Sales & CRM hygiene

HubSpot Closed Won → QuickBooks customer, ClickUp onboarding + Slack #wins

Won deals hand themselves to finance and onboarding within a minute of the stage change.

Closed Won is where sales stops and two other teams should start. This package fires on that stage change in HubSpot. The customer is created in QuickBooks Online, an onboarding task with a checklist lands in ClickUp, and the win is posted to Slack with links to all three. The deal keeps the QuickBooks and ClickUp IDs, so a deal that is re-opened and re-closed is not processed twice.

How it works

H
Trigger
Deal stage changes to Closed Won (deal.propertyChange webhook on dealstage)
HubSpot
if
Step 1
Confirm the new stage is Closed Won
The webhook fires on every stage move, so the first node compares the new dealstage value with your pipeline's Closed Won stage ID and drops everything else.
H
Step 2
Fetch the deal, its company and contact, and check for a prior run
The deal's amount, close date, owner and custom ID properties are fetched, then the associated company's name and address and the first associated contact's name and email; a deal whose QuickBooks ID is already filled stops here.
QB
Step 3
Find or create the QuickBooks customer
Display name is queried first; when nothing matches, a new customer is created with the company name, address and the contact's email as the primary email.
CU
Step 4
Create the onboarding task with its checklist
Your Onboarding list receives a task named after the company, assigned to the onboarding owner, due five business days after the close date, with the deal amount, the HubSpot link and the checklist items you set at setup.
S
Step 5
Post the win to #wins
Deal name, amount, rep and three links go in the message: the HubSpot deal, the QuickBooks customer and the ClickUp task.
H
Step 6
Write the QuickBooks and ClickUp IDs back to the deal
Two custom deal properties receive the QuickBooks customer ID and the ClickUp task URL, which is what the check in step two reads on any later run.
S
Step 7
Report any failed step to an error channel
Failures are caught by a separate error workflow that posts the deal ID, the step that failed and the API response to a Slack channel you choose, so a handoff is never silently half-done.

What changes once it runs

The QuickBooks customer exists within a minute of the deal closing, spelled the way the CRM spells it.
Onboarding sees a task with a checklist and a due date instead of a forwarded email.
Every win is announced in one Slack channel with the three links people otherwise go hunting for.
A deal that is re-opened and re-closed does not create a second customer or a second task.
Failures are reported with the deal ID and the API error, not discovered at month-end.

What you get

The n8n workflow export plus the companion error workflow, tested end to end
Setup guide covering the HubSpot developer app, the webhook subscription and the two custom deal properties
Field-mapping sheet: which HubSpot properties feed which QuickBooks and ClickUp fields
Recorded walkthrough of a deal being closed and the three records appearing
An editable onboarding checklist template for the ClickUp task

Before you start

HubSpot on any tier, Free included, with a private app token scoped to deals, companies and contacts
A HubSpot developer account and app for the webhook subscription; free to create, and required by the n8n HubSpot Trigger node
QuickBooks Online, Simple Start or above, with an Intuit app connected through OAuth
ClickUp, Free Forever or above, with an API token and an Onboarding list already created
Slack with permission to install an app and post to the #wins channel and an error channel
An n8n instance, cloud or self-hosted, reachable from the public internet so HubSpot can deliver the webhook

Built for

Questions before you buy

Can it raise the invoice as well?: No, on purpose. This package stops at the customer record so finance keeps control of what is billed and when. The invoicing packages in the finance category pick up from the customer record this one creates, and the two can run on the same stage change.
What happens if QuickBooks is down when a deal closes?: The workflow stops at that step and the error workflow posts the deal ID and the API response to your error channel. Re-run the execution from n8n once QuickBooks is back. Nothing was written back to the deal, so the retry starts clean; a deal that did finish is skipped by the check in step two.
Our pipeline has two Closed Won stages. Does that work?: Yes. The filter node holds a list of stage IDs rather than a single value, and the setup guide shows where to find each pipeline's stage ID in HubSpot. Deals from a pipeline you leave out are ignored.
Does it run on Make or Zapier?: Not as shipped. The seven-step flow with a write-back and a separate error path is built for n8n. Make can reproduce it with its HubSpot, QuickBooks, ClickUp and Slack modules; ask if you need that rebuild.
Do I need a paid n8n plan?: Any n8n Cloud plan runs it, and so does a self-hosted instance, where the community edition costs nothing. Self-hosted needs a public URL, or a tunnel, so HubSpot can reach the webhook.

Nearby on the shelf

Whole catalog