Docs

Docs / Integrations / Make integration

Make

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.

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.

On Free too. Make 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

ModuleKindCalls
Watch signing eventsInstant trigger (dedicated webhook)Attaches with POST /v1/webhooks for the event you choose (sent, signed, completed, declined, expired, voided, or every event); detaches with DELETE /v1/webhooks/{id}?reason= when you delete the webhook in Make. Each bundle is one delivery, the signed envelope described in Webhooks
Send a form to signActionPOST /v1/workflows/{id}/start with send_link: SignSealer emails the person their link (and texts it, where it may). The link is the signer's, and never handed to the scenario
Add or update a reservationActionPUT /v1/subjects, keyed on your booking ID
Send what a reservation owesActionPOST /v1/packets/{id}/start: safe to repeat
Download a signed PDFActionGET /v1/documents/{id}/pdf: a completed document's sealed PDF, as a file the next module can attach to an email or upload to a drive. The same bytes every time
Search documentsSearchGET /v1/documents by your reference, a title, a signer or a state, newest first. Pages through 200 at a time until your limit (10 unless you change it; empty for every one)
Search form answersSearchGET /v1/documents/{id}: one bundle per answer, for a filter or a router. A ticked box is Yes, one left alone is No once its signer has signed, and a sensitive answer is masked as your staff see it. Choose the form, and then one of its questions in its own words, to get only that question's answers (GET /v1/workflows/{id}/bundle)
Make an API callUniversalAny route in the API reference, with the connection's key: a path such as /v1/account on https://api.signsealer.com, and only there

Answers are never in a trigger's data, because a webhook goes wherever it is pointed and some answers are about somebody's health. A scenario that needs them asks with Search form answers, by the Document ID the trigger gives it.

Connecting

Create an API key under Integrations → API keys with the Read, Write, Workflows, Subjects and Webhooks scopes, and paste it when Make asks. It is checked against GET /v1/account, whose business name labels the connection, and kept out of Make's logs. A test key (mk_test_…) connects your sandbox, where nothing is sent to anybody. A refusal is shown in SignSealer's words, with what to do about it; a key that has been revoked stops the scenario and says so.

Recipes

  • Booking tool → waivers: your booking tool's trigger, then Add or update a reservation with the booking ID, then Send what a reservation owes with its Packet ID.
  • Signed → the PDF in an email or a folder: Watch signing events (Document completed), then Download a signed PDF with the document's ID, then an email attachment or a drive upload with its file.
  • A different next step for each answer: Watch signing events (Document completed), then Search form answers with the document's ID, the form and the question chosen, then a router: a filter on Answer equal to “Yes” on one route and “No” on the other. A question several people answered, as each person in a party does, gives one bundle each, with who answered it.
  • Answers to look at → a manager's inbox: Search form answers with the document's ID, a filter on To look at, then a text aggregator of Question and Answer into an email.

Until the app is listed

Make's HTTP → Make a request module does the same job with that key. For a trigger, create a Custom webhook in Make and add its address as a webhook in SignSealer for the event you want.

PUT https://api.signsealer.com/v1/subjects
Authorization: Bearer mk_live_…

{ "provider": "make", "external_id": "BK-1042", "starts_on": "2026-10-10",
  "participants": [{ "ref": "g1", "full_name": "Sam Tan", "email": "sam@example.signsealer.com", "is_primary": true }] }

Then POST /v1/packets/{packet_id}/start sends what the reservation owes. Both are safe to repeat.

For SignSealer: publishing

The app's source is integrations/make (Make's Apps SDK layout). Deploy it with the Make Apps Editor extension for VS Code, run the test scenarios Make's review asks for, then request the review; the folder's README lists each step.

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