Zapier · Automation · Beta
Signing that fits any Zap.
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.
Why connect Zapier
Three moments this is for.
The form in your CRM
A deal reaches Won in your CRM. The customer is sent your service agreement, filled from the deal, without anyone opening SignSealer.
The signed waiver in a spreadsheet
Every completed waiver adds a row to the sheet your front desk reads, with the name, date and document ID.
The booking system we do not connect to
Your booking tool has a Zapier trigger. Add or Update a Reservation turns it into a reservation, and your requirements decide what each guest signs.
How it works
Connect with SignSealer
Zapier sends you to SignSealer's consent screen. You pick the business and see exactly what Zapier may do; no key is copied anywhere.
Triggers are instant
Turning a Zap on registers a SignSealer webhook for that event; turning it off removes it. Nothing polls.
Actions go through the API
Send a Form to Sign, Add or Update a Reservation and Find a Document call the same API your developers would.
Triggers, actions and searches
What the Zapier app can do.
| Step | What it does |
|---|---|
| Document Completed, Signer Signed | Triggers with the document, its title, state, your reference and the signer |
| Document Sent, Declined, Expired, Voided | Triggers for the rest of a document's life |
| Send a Form to Sign | Starts one of your forms for a person, with blanks filled from the Zap |
| Add or Update a Reservation | A booking and its guest, then what your rules say they owe |
| Find a Document | By your reference, a title or a signer's name |
Where it stands: beta
Built, and awaiting publication in Zapier's directory, which follows Zapier's own review. Until it is listed, Zapier's Webhooks step can 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.
Getting started
About five minutes.
Step 1
Until the app is listed: in a Zap, use Webhooks by Zapier to call SignSealer's API with an API key (Developers → API keys).
Step 2
To trigger on a signature, add a SignSealer webhook pointing at a Catch Hook URL.
Step 3
When the app is listed, search for SignSealer when you add a step.
Read the full Zapier guide How requirements decide what is sent
Questions
Does the Zapier app need an API key?
No. It connects with OAuth: you approve it on SignSealer's consent screen, choosing the business and seeing the permissions. You can revoke it from SignSealer's Connected apps screen at any time.
Is every trigger instant?
Yes. Each trigger subscribes a webhook when the Zap is turned on and removes it when the Zap is turned off, so a Zap runs within seconds of the event.
Can a Zap text a signing link?
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.
What if a Zap sends the same booking twice?
Add or Update a Reservation is keyed on the booking's ID, so twice is the same reservation, and starting what it owes again sends nothing already sent.
Ready when the next guest is.
Free for the first 25 agreements a month. No card to start.