Loading...
New: API Access + Custom Branding now available on Business. Upgrade now →
Loading...
Connect SignBolt to Google Drive and every signed PDF lands automatically in your chosen folder. No downloading, no uploading — your signed contracts are always exactly where your team expects them.
Pro plan required · No per-integration fees · Cancel anytime
Three steps to have every signed document land in your Google Drive automatically.
Generate a SignBolt Pro API key from your dashboard. Use OAuth to authorise SignBolt to write files to your Google Drive. Only the folders you select are accessible.
Choose or create a Google Drive folder where signed PDFs will be saved automatically. You can set different destination folders for different document types.
Every time a document is signed via SignBolt, the completed PDF is pushed to your selected Drive folder within seconds. No manual downloading or uploading required.
Keep your signed contracts in the cloud storage your team already uses.
When a signing request completes, SignBolt fires a webhook and pushes the signed PDF directly to your configured Google Drive folder. Your signed contracts are always where you expect them.
Use the SignBolt API to fetch a PDF directly from a Drive file URL, process the signing request, and save the completed document back. No manual file handling required.
Route signed documents to team-shared Drive folders so your whole team has instant access to completed contracts. Set up separate folders per client, project, or document type.
Google Drive's built-in version history remains intact. Each signed PDF is saved as a new file — the original unsigned version stays in Drive alongside the completed document.
SignBolt fires document.signed, document.viewed, and document.declined events to your webhook endpoint. Trigger Drive operations, Sheets logging, or other Workspace automations on each event.
Google Drive auto-save and the underlying webhook infrastructure are included in the SignBolt Pro plan at $8/mo. No per-integration fees or add-ons required.
SignBolt fires these events to your webhook endpoint. Use them to trigger Drive uploads, Sheets logging, or any other automation in your workflow.
document.signedFires when all required signers have completed signing. Payload includes document ID, signer email, timestamp, and a download URL for the signed PDF ready to push to Drive.
document.viewedFires when a recipient opens the signing link. Use this to log viewing activity in a Google Sheet or trigger a Drive-based reminder workflow.
document.declinedFires when a recipient declines to sign. Move the document to a 'Declined' folder in Drive automatically and alert the sender.
Step-by-step instructions to auto-save signed documents from SignBolt into your Google Drive.
Log in to your SignBolt Pro dashboard. Navigate to Settings → API Keys and generate a new key. Store it securely as an environment variable — SIGNBOLT_API_KEY.
In Google Cloud Console, create a service account with the Drive API enabled. Download the JSON credentials file and add it as the environment variable GOOGLE_SERVICE_ACCOUNT_JSON. Share your target Drive folder with the service account email address to grant write access.
Configure your webhook URL in the SignBolt dashboard so that document.signed events are sent to your endpoint. In your handler, fetch the signed PDF from the downloadUrl in the payload and push it to your Google Drive folder using the snippet below.
// Auto-save signed PDF to Google Drive
// Run this in your server when you receive a document.signed webhook
import { google } from "googleapis";
import { Readable } from "stream";
const auth = new google.auth.GoogleAuth({
credentials: JSON.parse(process.env.GOOGLE_SERVICE_ACCOUNT_JSON!),
scopes: ["https://www.googleapis.com/auth/drive.file"],
});
const drive = google.drive({ version: "v3", auth });
export async function saveToDrive(
signedPdfUrl: string,
fileName: string,
folderId: string
) {
// Fetch the signed PDF from SignBolt
const pdfResponse = await fetch(signedPdfUrl, {
headers: {
Authorization: `Bearer ${process.env.SIGNBOLT_API_KEY}`,
},
});
const pdfBuffer = await pdfResponse.arrayBuffer();
const stream = Readable.from(Buffer.from(pdfBuffer));
// Upload to Google Drive
const file = await drive.files.create({
requestBody: {
name: fileName,
parents: [folderId],
mimeType: "application/pdf",
},
media: {
mimeType: "application/pdf",
body: stream,
},
});
return file.data.id;
}The document.signed payload contains everything you need to save the file to Drive and record the result. Here is the full event structure:
// SignBolt fires this payload when a document is signed
// POST to your configured webhook URL
{
"event": "document.signed",
"documentId": "doc_abc123",
"signerEmail": "client@example.com",
"signedAt": "2026-04-08T10:32:00Z",
"downloadUrl": "https://signbolt.store/api/documents/doc_abc123/download",
"fileName": "Service_Agreement_Signed.pdf",
"metadata": {
"driveFolderId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms"
}
}Use the metadata field in your signing requests to pass the target Drive folder ID. This lets you route different document types to different folders automatically. Suggested folder structure:
If your team already uses Google Drive as the single source of truth for documents, this integration keeps signed contracts exactly where they belong — without adding a new tool to your workflow.
Freelancers, small businesses, consultants, and agencies all benefit from having signed PDFs saved automatically without switching between apps.
Freelancers and Consultants
Keep client contracts in a dedicated Drive folder per client. Every signed agreement is archived automatically.
Small Business Owners
Share a signed contracts folder with your accountant or legal advisor without manual file transfers.
Operations and Ops Teams
Maintain an organised, searchable archive of all signed agreements across the business in Drive.
Remote and Distributed Teams
Everyone on the team has access to signed documents the moment they are completed — no email attachments.
API access, webhook events, and the ability to auto-save signed PDFs to Google Drive are all included in the SignBolt Pro plan. No add-ons, no per-save fees.
The Pro plan ($8/mo) includes API access, webhook support, and the infrastructure required to auto-save signed documents to Google Drive. No Business plan is required for Drive storage.
No. The OAuth flow requests only the permissions needed to write to the specific folders you select. SignBolt cannot read or modify files outside of the folders you explicitly authorise.
The SignBolt webhook endpoint retries failed Drive uploads up to three times with exponential backoff. The signed PDF is always available for manual download from your SignBolt dashboard regardless of Drive connectivity.
Yes. As long as your Google account has write access to the shared folder, SignBolt can save signed PDFs there. This makes completed contracts immediately accessible to your whole team.
Yes. Use the SignBolt REST API at /api/v1/sign. Fetch the file from Drive using the Drive API or a direct download URL, POST it to SignBolt with the signer's details, and the signed PDF is returned. You can then write it back to Drive programmatically.
Yes. The SignBolt API accepts a filename parameter in the signing request. Use it to set a consistent naming convention such as '[Client]_[DocType]_Signed_[Date].pdf' before the file is saved to Drive.
No. The original unsigned PDF in Drive is never modified. SignBolt creates a new signed PDF and saves it alongside or in a separate folder — your original document is always preserved.
More integrations to fit your existing workflow.
Start with the Pro plan and have your first signed PDF land in Google Drive today. The REST API and webhook documentation are ready.