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. Automation tools and CRMs start signing from anything else, and Zapier, Make and the API work on Free. Each row says where it stands.
| System | Kind | What it does | Status |
|---|---|---|---|
| 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. | Beta |
| 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. | Beta |
| FareHarbor | Tours and activities | SignSealer's FareHarbor integration sends every booked guest your liability waiver before the tour. Built, and waiting on FareHarbor's partner approval. | Awaiting partner approval |
| Hospitable | Vacation rentals | SignSealer for Hospitable: rental agreements and waivers sent from each reservation. Built against Hospitable's API and waiting on vendor approval. | Awaiting partner approval |
| Zapier | Automation | SignSealer for Zapier: send a form to sign from any of 7,000 apps, and start a Zap when a document is signed, completed, declined or expires. | Beta |
| Make | Automation | SignSealer for Make: watch signing events instantly and send forms, add reservations or search documents from any Make scenario. | Beta |
| Lodgify | Vacation rentals | Lodgify and SignSealer: how to send rental agreements from Lodgify bookings today with Zapier or Make, and what the native integration will add. | Planned |
| Hostfully | Vacation rentals | Hostfully and SignSealer: send rental agreements and waivers from Hostfully reservations today through automation, with a native connection planned. | Planned |
| Peek Pro | Tours and activities | Peek Pro and SignSealer: get liability waivers signed for every Peek booking today through automation, with a native integration planned. | Planned |
| HubSpot | CRM | HubSpot and SignSealer: send an agreement when a deal moves and record the signature back, today through Zapier or Make, natively later. | Planned |
| Zoho CRM | CRM | Zoho CRM and SignSealer: send agreements from Zoho deals and move them on when signed, today with Zapier or Make, with a native connection planned. | Planned |
| Your application | API / embedded | Create agreements, add signers, launch signing and receive completion events without making staff switch systems. | Available |
| WordPress | Website | A block or a shortcode puts a form on a page, and the site keeps the status. | Available |
| DeckPOS | Point of sale | Start agreements, authorizations and waivers from a transaction or counter workflow. | Available |
On the roadmap
Not built, and listed so nobody has to ask. Until then, Zapier, Make and the API reach every one of them.
Salesforce
CRM. Agreements from opportunities, signatures back on the record.
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.
QuickBooks Online
Accounting. A signed estimate or agreement becomes an invoice.
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.
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. A true in-app embed should use origin-bound, short-lived sessions rather than weakening anti-phishing controls for everyone.
Today, the supported pattern is API-controlled hosted signing or white-label hosted signing. The embedded-signing architecture is documented separately so a future JavaScript component can be added without making the public signing page frameable by any site.
Ready when the next guest is.
Free for the first 25 agreements a month. No card to start.