HubSpot
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.
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.
Today, step by step
- In Zapier: trigger on a HubSpot deal stage change, then SignSealer's Send a Form to Sign.
- A second Zap: SignSealer's Document Completed, then update the HubSpot deal.
- Use the deal ID as your reference so each document leads back to its deal.
The signature coming back
A second Zap or scenario: SignSealer's Document Completed (or a SignSealer webhook) → update the HubSpot deal, using the reference you sent. A declined document carries the signer's reason.
What the native connection does
It is built, and waits on
SignSealer's HubSpot app. A deal goes when somebody sends it: on the connection's page in SignSealer, paste the deal's
id or the address of its page, then choose what goes, any of your templates and forms, or what your rules say it needs, and whether to the deal's main contact or
every contact on it. A deal sends at a stage only if you name that stage on the connection's page; a deal moved to
Closed lost, or deleted, voids what nobody has signed. When everything is signed, or one is declined, a note goes on the
deal; when everything is signed, each signed PDF, sealed with its certificate, is attached to that note and kept private
in a SignSealer folder in your file manager (a switch on the connection turns that off). On the connection's page you can
also name a stage a signed deal moves to, by its internal name such as closedwon (not one that sends or
cancels), and a deal property of your own, such as a single-line text property signsealer_status, that says
Signed when everything is signed or Declined when somebody declines; both are off until you fill them in,
and a property HubSpot refuses is said in the connection's activity while the note still goes. Every delivery is checked against HubSpot's X-HubSpot-Signature-v3. A Send card inside HubSpot
itself comes with the app.
Once it can be connected, connecting it comes with the membership, like every system SignSealer connects to; Zapier, Make and the API work on Free today.
With the API directly
PUT https://api.signsealer.com/v1/subjects
Authorization: Bearer mk_live_…
{ "provider": "hubspot", "external_id": "…", "starts_on": "2026-10-10",
"participants": [{ "ref": "…", "full_name": "…", "email": "…", "is_primary": true }] }
POST https://api.signsealer.com/v1/packets/{packet_id}/start
Keyed on the HubSpot ID, so sending the same record twice is one reservation, and starting again sends nothing already sent. See Reservations and packets and Webhooks for the signature coming back.
Texting and consent
Signing links go by email. They also go by text only when SignSealer holds that guest's consent to
receive texts from your business, recorded with the exact words they agreed to — at your counter, on your
booking form through POST /v1/sms-consents, or on SignSealer's own opt-in. That check runs when
the link is queued (app.may_text), not in the integration.
No booking system can give SignSealer that consent, so none is treated as if it could. Each adapter
records what the provider's data said — VERIFIED_CONSENT, NO_CONSENT or
INSUFFICIENT_EVIDENCE — and only NO_CONSENT changes anything: the guest's number is
not written at all. Every provider built so far can only ever say INSUFFICIENT_EVIDENCE. The
connection's activity shows, for each guest with a number, whether the link was also texted and why not.
How to record consent you took yourself.
This page as Markdown Ask an AI about it: ChatGPT · Claude · Perplexity · Google AI · Grok
Ready to build? An API key takes a minute in the portal, and the free plan covers the first 10 agreements a month.
Get an API key