Make · Automation · Beta
Put signing in the middle of any scenario.
Watch for a signature in Make and branch on it, or send a form from any module's data — with the same API, and the same evidence, as everything else in SignSealer.
Why connect Make
Three moments this is for.
The branch on declined
A guest declines the agreement. The scenario routes that to your team's channel with the reason, and the booking is flagged before anyone travels.
The nightly batch
Tomorrow's arrivals come out of your booking tool as a list. Each becomes a reservation, and what they owe is sent.
The archive
Every completed document's ID and title lands in the database or drive your scenario writes to.
How it works
Connect with an API key
Make a SignSealer API key with the scopes the modules need and paste it once. It is checked against your account and kept out of Make's logs.
Watch events instantly
Watch Signing Events registers a SignSealer webhook for the event you choose, and removes it when the scenario is deleted.
Act through the API
Send a Form to Sign, Add or Update a Reservation, Send What a Reservation Owes and Search Documents.
Triggers, actions and searches
What the Make app can do.
| Step | What it does |
|---|---|
| Watch Signing Events | Sent, signed, completed, declined, expired, voided — or every event |
| Send a Form to Sign | One of your forms, to a person, with blanks filled |
| Add or Update a Reservation | A booking and its main guest, keyed on the booking's ID |
| Send What a Reservation Owes | Everything a packet still owes, safely repeatable |
| Search Documents | By your reference, a title, a signer or a state |
Where it stands: beta
Built, and awaiting publication as a Make app, which follows Make's review. Until it is listed, Make's HTTP module calls SignSealer's API with an API key and does the same job; the guide shows each call. 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
Make an API key in SignSealer: Developers → API keys, with Read, Write, Workflows, Subjects and Webhooks.
Step 2
Until the app is listed, use Make's HTTP module with that key against the calls in the guide.
Step 3
To trigger on a signature, add a SignSealer webhook pointing at a Make custom webhook.
Read the full Make guide How requirements decide what is sent
Questions
Why an API key rather than OAuth?
It is the simplest connection Make supports and needs nothing registered on either side. The key's scopes limit exactly what the scenario may do, and revoking it in SignSealer stops it at once.
Can it send texts?
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.
Does a failed run lose the event?
SignSealer retries a webhook delivery that Make does not accept, on a schedule, and shows each attempt on the webhook's page in SignSealer.
Ready when the next guest is.
Free for the first 25 agreements a month. No card to start.