
HubSpot · CRM · Planned
From HubSpot deal to signed agreement.
Choose the agreement for a HubSpot deal and its contacts are sent it; when they sign, the deal hears about it. Today through Zapier or Make.
Today HubSpot works through Zapier or Make, which run on Free.
Why connect HubSpot
Three moments this is for.
The deal you send
Press Send for the deal and choose the agreement: its contacts are sent it, filled from the deal. Signed: a note on the deal says so, and nobody has to check.
The declined contract
The contact declines. A note on the deal says which document was declined and that the rest are on hold, the same day.
The record a lawyer wants
The note links each signed document in SignSealer, with its certificate and every event on the trail.
How it works
Today: an automation
A HubSpot deal-stage trigger in Zapier or Make runs SignSealer's Send a Form to Sign.
The signature comes back
SignSealer's Document Completed trigger updates the deal in HubSpot.
Built, waiting on our app
SignSealer's own HubSpot app: press Send for a deal and choose what goes, or name a stage that sends it, and a note goes on the deal when they have signed.
What it can do
Each thing the connection does, and where it stands today.
Send from the deal
Built, not connectable yetPaste a deal's address on the connection's page and choose what goes: any of your templates and forms, or what your rules say the deal needs, to its main contact or every contact on it. Nothing goes because a deal was dragged.
Or at a stage you choose
Built, not connectable yetOff unless you turn it on: a deal reaching a stage you name, such as Contract sent, sends its contacts what they owe, whoever moved it there.
Who signs
Built, not connectable yetThe deal's contacts, the first as the primary signer, up to twenty.
Your documents read the deal
Built, not connectable yetThe deal's name, stage, pipeline, amount, close date and type are facts your agreement and your rules can read.
A lost deal stops it
Built, not connectable yetA deal moved to Closed lost, or deleted, voids what nobody has signed. Moving a signed deal on to Closed won changes nothing.
A note on the deal
Built, not connectable yetWhen everything is signed, or one is declined, a note on the deal says so, with each document, who signed it, when, and a link to it.
The signed PDF on the deal
Built, not connectable yetWhen everything is signed, each signed PDF, sealed with its certificate, is attached to the note on the deal, kept private in a SignSealer folder in your file manager. A switch on the connection turns it off.
The deal moves on when signed
Built, not connectable yetName a stage, such as Closed won, and a signed deal is moved there; name a deal property of your own and it says Signed, or Declined when somebody declines. Both are off until you fill them in on the connection.
A Send card inside HubSpot
Not yetA card on the deal in HubSpot itself, so nobody leaves HubSpot to press Send, is not built yet: it comes with SignSealer's HubSpot app.
The signed PDF and its certificate
TodayEach signed document is sealed with a certificate anyone can check, and kept in SignSealer. Zapier's Document Completed hands the PDF on, to an email or to wherever you keep documents.
What comes across
What arrives from HubSpot, and what SignSealer does with it.
| From HubSpot | Used for |
|---|---|
| Deal and contact | Who signs, and the values filled into the agreement |
| Deal stage | What stops the agreement when the deal is lost, and starts it only at a stage you choose |
| Completed, declined | What moves the deal on |
Where it stands: planned
Built, and not yet connectable. The native connection is written and tested against stand-ins: you press Send for a deal and choose what goes, or name a stage that sends it, and a note goes on the deal when they have signed. It has not run against a live HubSpot account, and SignSealer's HubSpot app needs HubSpot's review and installs before listing. Until then Zapier and Make carry both directions, and the guide has the exact steps.
Start today
What you can do now, without waiting.
Step 1
In Zapier: trigger on a HubSpot deal stage change, then SignSealer's Send a Form to Sign.
Step 2
A second Zap: SignSealer's Document Completed, then update the HubSpot deal.
Step 3
Use the deal ID as your reference so each document leads back to its deal.
Read the full HubSpot guide How requirements decide what is sent
Questions
Will it write the signed PDF to HubSpot?
Yes, with the native connection: when everything is signed, each signed PDF, sealed with its certificate, is attached to the note it puts on the deal, and kept private in a SignSealer folder in your file manager. Today a Zap gets the signed PDF itself as a file from SignSealer's Document Completed, to hand to any later step that takes one, and can add the document's link and certificate code to the deal as a note.
Can I send different agreements by deal type?
Yes. With the native connection you choose the agreement each time you press Send, or your rules choose it from the deal's type, amount or pipeline. Today the Zap chooses the form, or one form's blanks are filled from the deal's properties.
Can it change a field on the deal when it is signed?
Yes, with the native connection. Name a deal property of your own, such as a single-line text property called SignSealer status, and it says Signed when everything is signed, or Declined when somebody declines; name a stage, such as Closed won, and a signed deal is moved there. Both are off until you fill them in on the connection, and a property HubSpot refuses is said in its activity while the note still goes.
Is this a HubSpot-certified app?
Not yet. It will be listed in HubSpot's marketplace when it passes HubSpot's review, and this page will say so then.


Ready when your next customer is.
Free for the first 10 signings a month. No card to start.


