Docs

Docs / Integrations / Zapier integration

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.

Beta. Built, and awaiting publication in Zapier's directory, which follows Zapier's own review. Until it is listed, we invite you to the app itself, which works on Zapier's Free plan; on a paid Zapier plan, Zapier's Webhooks step can also call SignSealer's API directly — the guide shows how. A phone number passed through a Zap is not consent to text. Links go by email. They go by text only to a guest whose consent to receive texts from you is on file in SignSealer: a booking system knowing a phone number is not that guest agreeing to be texted, and SignSealer never treats it as if it were. Texts go from your business's own number, which is coming soon.

On Free too. Zapier uses the SignSealer API, which every plan includes; each signing it starts counts toward your 10 free signings a month like any other.

What the app does

StepKindCalls
Document Completed · Signer Signed · Document Sent · Declined · Expired · VoidedInstant 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 SignActionPOST /v1/workflows/{id}/start with send_link: SignSealer emails the person their link (and texts it, where it may). Choose the form and each of its blanks is a box of its own, named as the form names it
Add or Update a ReservationActionPUT /v1/subjects, then POST /v1/packets/{id}/start when “Send now” is yes
Find a DocumentSearchGET /v1/documents by your reference, title or signer
Signed PDFFileOn Document Completed, Find a Document and Find Form Answers once the document is complete: the sealed PDF (GET /v1/documents/{id}/pdf), fetched only when a later step uses it, to attach to an email or save to Drive
Find Form AnswersSearchGET /v1/documents/{id}: what the signer answered on the form, each question a field of its own for a Filter or a Path, sensitive answers masked as your staff see them. Choose the form and every question is listed in its own words (GET /v1/workflows, GET /v1/templates/{id}). Answers are never in a trigger's data, because a webhook goes wherever it is pointed; a Zap that needs them asks with this step, by the document ID a trigger gives it

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 Integrations → Connected apps.

Until the app is listed

Ask us for an invitation to the app, which works on Zapier's Free plan. On a paid Zapier plan, Webhooks by Zapier (a paid feature of Zapier's) does the same job with an API key (Integrations → 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.signsealer.com", "external_ref": "RES-88213",
  "send_link": true }

send_link has SignSealer email Dana the signing link. Without it the link comes back in the answer, once, for a page that hands the person straight on to sign, and nobody is sent anything.

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

A delivery never carries the form's answers. With the document ID it does carry, the same key asks for what was answered (GET /v1/documents/{id}) and, once the document is complete, for the sealed PDF (GET /v1/documents/{id}/pdf).

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; the documents for bookings from the API decide the rest.
  • Signed → spreadsheet: Document Completed, then add a row with the title, reference and certificate.
  • Signed → the PDF in an email or a folder: Document Completed, then Gmail's attachment or Google Drive's upload with Signed PDF. It is the sealed copy, the same file every time.
  • A different next step for each answer: Document Completed, then Find Form Answers with its Document ID and the form chosen, then Paths, one per answer: “Are you married?” exactly matches “Yes” on one path and “No” on the other. A tick box is Yes or No, and one left alone is No once its signer has signed; a choice is the option exactly as the form lists it. A question several people answered, as each person in a party does, holds every different answer, sorted and joined with a comma: “exactly matches Yes” is everyone, “contains Yes” is anyone.
  • Answers to look at → a manager's inbox: Document Completed, then Find Form Answers with its Document ID, then a filter on “Number of answers to look at” above 0, then an email with “Answers to look at (text)”. Send it as plain text, or the lines run together.

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.

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