Move the HubSpot deal to closed won on signature
When the last signer signs, Document Signing Complete starts a Zap that finds the deal and updates its stage, amount and close date, so the pipeline is right without anyone touching it.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
Build a Zap with QuoteCloud's Document Signing Complete trigger, which fires once every signer has signed. Add HubSpot's Find Deal search to find the deal by the ID the quote kept, then Update Deal to set the stage to closed won, the amount to the signed total and the close date. Test with a test deal first.
Last reviewed by the QuoteCloud team
Two overlapping panels with sample data. Behind, Plinthwork's order form PW-2372 for Tidemark Property Services: 60 Growth plan seats, implementation and training, $38,566.00 including tax, signed by Lena Albright and Marcus Oyelaran. In front, an illustration of the deal at Closed won, its amount $38,566.00 and close date 22 Oct 2026 updated by a Zap.
Order summary
| Item | Qty | Rate | Amount |
|---|---|---|---|
| Subscription, first year | $27,360 | ||
Growth planAnnual subscription per seat, invoiced by Plinthwork
|
60 seats | $456 | $27,360.00 |
| Onboarding | $7,700 | ||
Implementation packageSet-up, data import and two working sessions
|
1 | $6,500 | $6,500.00 |
Admin trainingTwo sessions for up to eight admins
|
1 | $1,200 | $1,200.00 |
- Subtotal
- $35,060.00
- Tax (10%)
- $3,506.00
- Total
- $38,566.00
- Plus, monthly
- $0.00/mo
Accept and sign
2 of 2 signed
- LA Lena AlbrightChief Operating Officer Signed21 Oct 2026
- MO Marcus OyelaranFinance director Signed22 Oct 2026
Certificate of authenticity and audit trail attached
Deal · ID 31533190Tidemark Property Services · Growth plan, 60 seats
- Qualified
- Demo
- Proposal
- Quote sent
- Closed won
- Amount
- $38,566.00 Updated by a Zap
- Deal owner
- Theo Marchetti
- Contact
- Lena Albright
- Company
- Tidemark Property Services
- Close date
- 22 Oct 2026 Updated by a Zap
- Quote status
- Signed by every signer
Illustration with sample data: a generic CRM record, not HubSpot’s screen.
The pipeline is only as right as its last update
Plinthwork sells maintenance planning software. Account executive Theo Marchetti's order form for Tidemark Property Services needs two signatures, Lena Albright's and Marcus Oyelaran's. The deal should be closed won when the second one lands, not when someone remembers to update it.
QuoteCloud's Document Signing Complete waits for every signer. Recipient Signed Document fires for each one, which suits a note on the deal, not a stage change.
The recipe: signing complete to closed won
Three steps. Two optional ones file the signed PDF in the same Zap.
ZapSigning complete: deal closed won
-
When
QCQuoteCloudTriggerDocument Signing CompleteFires once every signer has signed.Passes on
- Document reference
- Total
- Signed date
- HubSpot deal ID (data item)
-
Then
HubSpotSearchFind DealSearches on Record ID, using the deal ID the quote kept in a data item.Searches on- Record ID
-
Then
HubSpotActionUpdate DealMapped in- Deal stage: Closed won
- Amount
- Close date
- Quote status
-
Or
QCQuoteCloudAction · optionalGenerate or Fetch Document PDF LinkThe link is short-lived, so the next step uses it straight away.Mapped in
- Document
-
Or
GDGoogle DriveAction · optionalUpload FileFile the signed PDF in the customer's folder.Mapped in
- File (the PDF link)
- Folder
Lena signs on Wednesday morning and nothing happens in HubSpot, by design. When Marcus signs on Thursday at 11:17 am, Document Signing Complete fires, and a minute later the Tidemark deal is closed won at $38,566.00.
Result
The deal's stage, amount and close date match the signed order form, and the signed PDF is in Drive, with nobody retyping anything.
Zapier access: Essentials and up
How software vendors connect QuoteCloudSigned in QuoteCloud, won in HubSpot
Accept and sign
2 of 2 signed
- LA Lena AlbrightChief Operating Officer Signed21 Oct 2026
- MO Marcus OyelaranFinance director Signed22 Oct 2026
Certificate of authenticity and audit trail attached
Activity
- Sent to Lena Albright and Marcus OyelaranMon 19 Oct, 2:30 pm
- First viewed by LenaMon 19 Oct, 5:12 pm
- Signed by Lena AlbrightWed 21 Oct, 9:48 am · 1 of 2
- Signed by Marcus OyelaranThu 22 Oct, 11:17 am · 2 of 2
- Signing completeThu 22 Oct, 11:17 am
Zap
- Document Signing Complete
- Find Deal
- Update Deal
Deal · ID 31533190Tidemark Property Services · Growth plan, 60 seats
- Qualified
- Demo
- Proposal
- Quote sent
- Closed won
- Amount
- $38,566.00 Updated by a Zap
- Deal owner
- Theo Marchetti
- Contact
- Lena Albright
- Company
- Tidemark Property Services
- Close date
- 22 Oct 2026 Updated by a Zap
- Quote status
- Signed by every signer Updated by a Zap
Activity timeline
- Close date set to 22 Oct 2026The signing dateThu 22 Oct · 11:18 am · Added by a Zap
- Amount set to $38,566.00The signed document's totalThu 22 Oct · 11:18 am · Added by a Zap
- Stage changed to Closed wonPW-2372 signed by Lena Albright and Marcus OyelaranThu 22 Oct · 11:18 am · Added by a Zap
- Stage changed to Quote sentBy Theo MarchettiMon 19 Oct · 2:32 pm
- Deal createdBy Theo MarchettiMon 5 Oct · 10:20 am
Illustration with sample data: a generic CRM record, not HubSpot’s screen.
Before the last signature
Until every signer has signed, the deal stays where your rep left it: Quote sent, with the amount from the negotiation. Nothing in this Zap fires on the first signature.
That's the difference between Document Signing Complete and Recipient Signed Document, and why this recipe uses the first.
Log each signature as it landsDeal · ID 31533190Tidemark Property Services · Growth plan, 60 seats
- Qualified
- Demo
- Proposal
- Quote sent
- Closed won
- Amount
- $34,000.00
- Deal owner
- Theo Marchetti
- Contact
- Lena Albright
- Company
- Tidemark Property Services
- Close date
- 30 Oct 2026
- Quote status
- Sent
Activity timeline
- Stage changed to Quote sentBy Theo MarchettiMon 19 Oct · 2:32 pm
- Deal createdBy Theo MarchettiMon 5 Oct · 10:20 am
Illustration with sample data: a generic CRM record, not HubSpot’s screen.
Field map for this recipe
| Direction | QCQuoteCloud: QuoteCloud field | Goes into | Example (sample data) | Note | |
|---|---|---|---|---|---|
| Record ID (Find Deal) | QuoteCloud to HubSpot | HubSpot deal ID | Search value | 31533190 |
The data item the quote kept when it was created. |
| Deal stage | QuoteCloud to HubSpot | A fixed value | Deal property | Closed won |
Pick the stage from your pipeline in the Update Deal step. |
| Amount | QuoteCloud to HubSpot | Document total | Deal property | $38,566.00 |
Check the trigger's test data shows the total, and map the figure your team reports on. |
| Close date | QuoteCloud to HubSpot | Signed date | Deal property | 22 Oct 2026 |
|
| Quote status (custom property) | QuoteCloud to HubSpot | A fixed value | Deal property | Signed by every signer |
All values are sample data.
Variations on this recipe
File the signed PDF
Add Generate or Fetch Document PDF Link, then Google Drive's Upload File, in the same Zap: the link is short-lived.
Celebrate in the channel
Add Send Channel Message for Slack or Microsoft Teams: who signed, the total and the deal.
Paid, not just signed
If the quote takes a payment on signing, a second Zap on QuoteCloud's Document Paid trigger can set a Deposit paid property on the deal. QuoteCloud Payments is on Essentials and up.
Each signer on the timeline
Add a Zap on Recipient Signed Document for a note per signature, and keep this one for the stage.
Build it with a free trial
Zapier access is on QuoteCloud's Essentials plan and up. Start a free 14-day trial, connect HubSpot and test with a sample deal.
Build it in five steps
- 1
Keep the deal ID in the quote
Quotes created from the deal carry its Record ID in a data item.
- 2
Start with Document Signing Complete
In Zapier, choose QuoteCloud and Document Signing Complete, and test it with a fully signed test quote.
- 3
Find the deal
Add HubSpot's Find Deal, searching on Record ID mapped from the data item.
- 4
Update the deal
Add Update Deal: the closed won stage, the amount from the total and the close date from the signed date.
- 5
Test with two signers
Send a test quote to two @example.com signers, sign as both, check the test deal, then switch the Zap on.
Questions about this recipe
Should I use Document Signing Complete or Recipient Signed Document?
Use Document Signing Complete to change the deal's stage: it fires once every signer has signed. Recipient Signed Document fires for each signer, so with two signers the deal would close after the first. It's the right trigger for a note per signature.
Can the deal amount be the signed total?
Yes, when the trigger carries the document's total, which you can check in the Zap's test data. Map it into the Amount field in Update Deal. The total includes the optional items the buyer ticked, so the deal shows what was actually signed.
Can the signed PDF go into HubSpot or Google Drive?
QuoteCloud's Generate or Fetch Document PDF Link gives a short-lived link, so upload the file in the same Zap, for example with Google Drive's Upload File. Don't store the link itself: it stops working.
Does this Zap carry a QuoteCloud document fee?
No. It reads a signed document and updates HubSpot; it doesn't create a document. The per-document fee applies to documents created through Zapier or the API. Zapier access itself is on the Essentials plan and up.
More on QuoteCloud and HubSpot
Six recipes with the exact Zapier steps, then how to connect, test and what it costs.
- Create quotes from HubSpot dealsA deal reaches your proposal stage and a draft quote is created from your template, filled with the deal's details.
- See quote activity on the HubSpot dealFirst views and signatures logged on the deal, so the owner knows when to follow up.
- Keep HubSpot and QuoteCloud contacts matchedNew HubSpot contacts found or created in QuoteCloud, and new QuoteCloud contacts created or updated in HubSpot.
- Follow up expired and lost quotesAn expired quote becomes a task for the deal owner; a lost one moves the deal to closed lost.
- Send document form answers to HubSpotAnswers from a form in a QuoteCloud document update the contact's or deal's properties.
- Connect HubSpot to QuoteCloud, step by stepSign in to both apps in Zapier, pick a trigger, map the fields, test with sample data and turn it on.
- HubSpot to QuoteCloud field mapEvery field the recipes on this site pass, which way it goes and where it lands.
- Test and troubleshoot your HubSpot ZapsTest with sample data, then fix the usual problems: no deal found, echoes, missing fields, expired PDF links.
- What the HubSpot connection can and can't doThe honest limits: one way per Zap, no ticking options, short-lived PDF links, plans and fees.
- What the HubSpot connection costsThe plan you need and the per-document fee for documents created through Zapier, worked out for your volume.
- FAQAnswers to the questions teams ask before connecting QuoteCloud and HubSpot.
Closed won, the minute it's signed.
Start a free 14-day trial and build the Zap that closes your HubSpot deals on signature.
Closed won on signatureFree 14 days · no card
Start free trial