Integrations
E-signatures inside the systems your team already uses.
A CRM should still feel like a CRM, a booking system should still own the reservation, a POS the sale. SignSealer runs the signing behind them and returns the result.
Connect the system you already use
Booking systems send us reservations and your requirements decide what each guest signs; connecting one comes with the membership. CRMs start it from a deal when somebody presses Send and field-service software from a quote, and Zapier, Make and the API reach everything else on Free.
Guesty
Vacation rentals
Connect Guesty to SignSealer: every confirmed reservation sends the guest a rental agreement and the waivers your property needs, tracked until signed.
Hostaway
Vacation rentals
Connect Hostaway to SignSealer so each new reservation sends the guest your rental agreement and property waivers, with signing tracked against the booking.
Zapier
Automation
SignSealer for Zapier: send a form to sign from any of 7,000 apps, start a Zap with its signed PDF once signed, and get each answer in a Find Form Answers step.
Make
Automation
SignSealer for Make: watch signing events, send forms and reservations, download the signed PDF, and search documents and form answers in any scenario.
Lodgify
Vacation rentals
Connect Lodgify to SignSealer: every booked stay, from your own site or any channel, sends the guest the rental agreement and waivers that property needs.
Hostfully
Vacation rentals
Connect Hostfully to SignSealer so each booked lead sends the guest your rental agreement and property waivers, with signing tracked against the booking.
Your application
API / embedded
Create agreements, add signers, launch signing and receive completion events without making staff switch systems.
WordPress
Website
A block or a shortcode puts a form on a page, and WooCommerce, booking plugins such as Amelia and LatePoint, and form plugins send what each order or booking needs.
DeckPOS
Point of sale
Start agreements, authorizations and waivers from a transaction or counter workflow.
Not connectable yet
Awaiting partner approval means it is built and waiting on the other company; Planned means it cannot be connected yet, and one whose summary says Built is finished and waits on SignSealer's own app with that company. Until then, Zapier, Make or the API carries most of them across, and each one's page says what works today.
Hospitable
Vacation rentals
SignSealer for Hospitable: rental agreements and waivers sent from each reservation. Built against Hospitable's API and waiting on vendor approval.
HubSpot
CRM
HubSpot and SignSealer: choose the agreement for a deal and its contacts are sent it, and a note records the signature. Built; Zapier or Make until it is live.
Jobber
Field services
Jobber and SignSealer: a quote sent to the client sends the agreement that goes with it, and a note records the signature. Built; Zapier until it is live.
Pipedrive
CRM
Pipedrive and SignSealer: a deal reaching your contract stage sends the agreement, and a note puts the signature on the deal. Built; Zapier or Make until live.
Salesforce
CRM
Salesforce and SignSealer: an opportunity at your stage sends its contacts the agreement, and a task records the signature. Built; Zapier or Make until live.
Zoho CRM
CRM
Zoho CRM and SignSealer: a deal at your stage, or a contact, lead or custom-module record you flag, sends the agreement. Built; Zapier or Make until it is live.
On the roadmap
Not built, and listed so nobody has to ask. Until then, Zapier, Make and the API reach every one of them.
Microsoft 365, SharePoint and OneDrive
Storage. Signed PDFs and certificates filed where your team keeps documents.
Google Drive
Storage. Each completed document saved to a folder you choose.
Dropbox
Storage. Each completed document saved to a folder you choose.
A phone number is not permission to text
None of these systems can tell us a guest agreed to receive texts from you, so none of them is treated as if it could.
Signing links go by email. They go by text only to a person whose consent to receive texts from your business is on file in SignSealer, in the words they agreed to. A booking system that says a guest opted out takes the number away. A booking system that has a guest's number gives SignSealer nothing more than the number.
The integration loop
The integration pattern is intentionally small: create the agreement, send the signer into the signing flow, then react when the state changes.
Trigger
A deal, booking, order, application or internal event says an agreement is needed.
Create
Your system calls SignSealer with the document values and signer roles.
Sign
The person receives a hosted or white-label signing link through the channel you choose.
Continue
A signed webhook tells your system what happened so the original workflow can move on.
Watch: Connect your software: the API, the SDK and the docs (2:38) →
Watch: Webhooks that you can debug (1:44) →
Hosted, white-label or platform-level
Choose the level of integration that matches the experience you want to own.
Hosted signing
Use the API to create and track agreements while SignSealer serves the hardened signer page.
White-label
Keep your brand and domains on the signer-facing experience while the signing and evidence engine stays SignSealer.
Platform integration
Use OAuth, scoped access and tenant-aware workflows when your product needs to offer signing to many customer accounts.
About iframe-style embedding
The hosted signer page deliberately blocks arbitrary framing. An in-app embed is bound to the sites a business has proven are its own, with a fresh link minted when the page is shown, rather than weakening anti-phishing controls for everyone.
Today, the supported patterns are API-controlled hosted signing, white-label hosted signing, and the signing page in a frame on one of those proven sites, telling the page around it when the person has signed. Anywhere else, the frame stays empty.
Ready when the next guest is.
Free for the first 10 agreements a month. No card to start.