
Integration
Via Zapier / APISign Documents Stored in Google Drive
WoltSign connects to Google Drive via Zapier or REST API. A direct Google Drive file picker is on the roadmap.
Use cases
What teams do with WoltSign and Google Drive
- Pick a PDF or Word document from a Google Drive folder and send it for signing without downloading it first
- Save completed signed documents back to a specific Drive folder automatically
- Share the signed document link with a Google Workspace team
Workflow
How it works
Three steps from trigger to completed signature. Full setup detail lives in the documentation.
- 1
In Zapier, create a Zap that triggers when a new file appears in a specific Drive folder. The action creates a WoltSign signing request with the file attached.
- 2
WoltSign sends the document for signature. Completion triggers another Zap step that uploads the signed PDF back to a designated Drive folder.
- 3
The signed document lands in Drive with the same filename plus " - Signed" appended.
FAQ
Google Drive integration FAQ
- Can I pick a file from Google Drive directly inside WoltSign?
- A native Drive file picker inside WoltSign is on the roadmap. Currently, connect via Zapier to automate file handoff, or download from Drive and upload directly to WoltSign.
- Does WoltSign work with Google Docs (not just PDFs)?
- WoltSign accepts PDFs and common document formats. If your document is in Google Docs format, export it to PDF from Google Docs before uploading, or use Zapier to automate the export step.
- Can completed documents save automatically back to Drive?
- Yes, via a Zapier step triggered by WoltSign's signing completed event. The step uploads the completed PDF to a folder you specify in Drive.
- Is this integration suitable for Google Workspace teams?
- Yes. Most Google Workspace teams use this Zapier pattern to keep signed documents organized in Drive without a separate filing step.
Get started
Connect Google Drive to WoltSign
Open your WoltSign account, connect via Zapier or the REST API, and follow the setup guide at /documentation.