
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.
Make works on Free: it uses the SignSealer API, which every plan includes.
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 sealed PDF lands in the drive your scenario writes to, under the name SignSealer gives it, with its title and ID beside it.
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 you delete the webhook in Make.
Act through the API
Send a form, add a reservation and send what it owes, download the signed PDF, search documents and form answers, or call any other route with Make an API call.
What it can do
Each thing the Make app does, and where it stands today.
Watch signing events
Built, awaiting reviewSent, signed, completed, declined, expired, voided, or every event, the moment it happens.
Send a form to sign
Built, awaiting reviewOne of your forms, to a person, with its blanks filled.
Add or update a reservation
Built, awaiting reviewA booking and its main guest, keyed on the booking's ID, so running it twice is one reservation.
Send what a reservation owes
Built, awaiting reviewEverything a reservation's documents still owe, safely repeatable.
Download a signed PDF
Built, awaiting reviewA completed document's sealed PDF, as a file the next module attaches to an email or uploads to a drive.
Search documents
Built, awaiting reviewBy your reference, a title, a signer or a state, page after page up to the limit you set.
Search form answers
Built, awaiting reviewWhat the signer answered, one bundle per answer, to filter or route on; sensitive answers stay masked.
Make an API call
Built, awaiting reviewAny other route in SignSealer's API, with the connection's key, and only ever to SignSealer.
Make's HTTP module, today
TodayUntil the app is listed, Make's HTTP module calls SignSealer's API with an API key and does the same jobs; the guide shows each call.
Triggers, actions and searches
Each step, as it is named when you add one.
| 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 |
| Download a signed PDF | A completed document's sealed PDF, as a file to attach to an email or upload to a drive |
| Search documents | By your reference, a title, a signer or a state, page after page up to your limit |
| Search form answers | What the signer answered, one bundle per answer to filter or route on; sensitive answers masked |
| Make an API call | Any other route in SignSealer's API, with the connection's key |
Where it stands: beta
Built to what Make's review asks of an app, and awaiting publication as a Make app, which follows that 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. Texts go from your business's own number, which is coming soon.
Getting started
About five minutes.
Step 1
Make an API key in SignSealer: Integrations → 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 a scenario branch on what somebody answered?
Yes. Search form answers gives each answer on a document's form as a bundle of its own, so a router's filter can send a Yes one way and a No another. Answers are never in a trigger's data, and a sensitive answer stays masked as your staff see it.
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. Texts go from your business's own number, which is coming soon.
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.
Does Make work on Free?
Yes. Make uses the SignSealer API, which every plan includes, so each signing it starts counts toward your 10 free signings a month like any other.


Ready when your next customer is.
Free for the first 10 signings a month. No card to start.


