Zapier

Send a SignSealer form from a new booking, order or lead in any app, and let a completed signature move the next step in the tools you already use.

What the app does

Step	Kind	Calls
Document Completed · Signer Signed · Document Sent · Declined · Expired · Voided	Instant triggers (REST hooks)	Subscribes POST /v1/webhooks for the one event when the Zap is turned on; removes it with DELETE /v1/webhooks/{id}?reason= when it is turned off
Send a Form to Sign	Action	POST /v1/workflows/{id}/start
Add or Update a Reservation	Action	PUT /v1/subjects, then POST /v1/packets/{id}/start when “Send now” is yes
Find a Document	Search	GET /v1/documents by your reference, title or signer

Connecting

The app connects with OAuth 2.0 and PKCE. Zapier sends you to SignSealer's consent screen, where you choose the business and see what Zapier will be able to do; no key is copied anywhere. You can revoke it under Developers → Connected apps.

Until the app is listed

Webhooks by Zapier does the same job with an API key (Developers → API keys):

POST https://api.signsealer.com/v1/workflows/{form id}/start
Authorization: Bearer mk_live_…
Content-Type: application/json

{ "full_name": "Dana Reyes", "email": "dana@example.com", "external_ref": "RES-88213" }

To trigger a Zap on a signature, create a Catch Hook in Zapier and add its URL as a webhook in SignSealer (Developers → Webhooks) for signing.completed. Each delivery is the signed envelope described in Webhooks.

Recipes

• CRM deal won → agreement: trigger on the deal, Send a Form to Sign with the deal ID as your reference.
• Booking tool → waivers: trigger on the booking, Add or Update a Reservation with the booking ID; your requirements decide the rest.
• Signed → spreadsheet: Document Completed, then add a row with the title, reference and certificate.

For SignSealer: publishing

The app's source is integrations/zapier in SignSealer's repository (zapier-platform-core 19). Publishing needs an OAuth client registered in Ops with the redirect URI Zapier gives the app, CLIENT_ID and CLIENT_SECRET set with zapier-platform env:set, and Zapier's review.

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.