HubSpot

When a HubSpot deal reaches the right stage, the contact is sent your agreement; when they sign, the deal hears about it. Today through Zapier or Make.

Today, step by step

1. In Zapier: trigger on a HubSpot deal stage change, then SignSealer's Send a Form to Sign.
2. A second Zap: SignSealer's Document Completed, then update the HubSpot deal.
3. 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 integration will do

A HubSpot app from HubSpot's marketplace: send from a deal, write the status, the certificate code and the signed PDF back to the deal, with HubSpot's X-HubSpot-Signature-v3 checked on every delivery.

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.