Zapier and workflow automation
Signing is rarely the whole workflow. A form is submitted, a document is generated, somebody signs it, and the sealed copy has to land somewhere: a Drive folder, a CRM record, an accounting system, a Slack channel.
Drop your document here and sign it now. PDF, Word and Excel all work: a .docx or .xlsx is laid out in your browser exactly as it was written, so there is nothing to convert first. Add a signature, a date, a company stamp or a watermark, then download it sealed. Free to start, no account, and the file is never uploaded to open it.
There is no published Zapier app yet. What exists today is a REST API and outbound webhooks, which Zapier connects to with Webhooks by Zapier, and that covers both directions.
How it works with Zapier
- Trigger the send A Zap fires on your form, CRM or spreadsheet event and calls the API to create the document with the signer and the fields already placed.
- Let us chase Reminders go out automatically, so the Zap does not need to poll and you do not need to nudge.
- Catch the completion Our webhook posts the document id, the completion time, the signer record and the SHA-256 fingerprint to a Catch Hook step.
- File it The rest of the Zap does what it always does: save the sealed PDF, update the record, post to the channel, store the fingerprint alongside it.
What you get
- REST API included on the Business plan rather than sold as an add-on
- Outbound webhooks on completion, decline and expiry
- The fingerprint in the payload is the same value the public verification page checks
- Works with any automation tool that can call a URL, not only Zapier
Questions people ask
Is there an official PDF Verified Zapier app?
Not yet. Webhooks by Zapier plus the REST API does the same work today, and it is honest to say which one you are getting rather than listing a logo.
What does the completion webhook contain?
The document id, when it completed, each signer with the time and address their signature came from, which verification steps they passed, and the SHA-256 fingerprint of the sealed file. Verify the signature header against the raw body before trusting any of it.
Can I use Make or n8n instead?
Yes. Anything that can send an HTTP request and receive one works, because the integration is a documented API rather than a proprietary connector.