Loading...
New: API Access + Custom Branding now available on Business. Upgrade now →
Loading...
The SignBolt Google Workspace integration lets your team sign documents without leaving the tools they already use. Sign PDF attachments from Gmail, add signature fields in Google Docs, and save every completed document directly to Drive.
Business plan required · Admin install · No per-user fees · Cancel anytime
Admin installs once. Your whole team gets signing in Gmail, Docs, and Drive.
A Google Workspace admin installs the SignBolt add-on from your Google Admin console. Once installed, it appears in Gmail and Drive for all users in your organisation.
When a user receives an email with a PDF attachment, the SignBolt sidebar appears in Gmail. One click opens the signing flow without leaving Gmail — no downloads needed.
Completed signed documents are automatically saved back to a designated Google Drive folder. The signed PDF is also available in your SignBolt dashboard with a full audit trail.
Signing built into every Google app your team already works in.
Open an email with a PDF attachment and sign it from the SignBolt sidebar — without downloading the file, switching apps, or leaving your inbox. Recipients are notified by email when the signed copy is ready.
The SignBolt add-on lets you insert signature request fields into a Google Doc. Export to PDF, send for signing, and receive the completed document back — all without leaving Google Workspace.
Every signed document is automatically pushed to your configured Google Drive folder the moment signing is complete. Shared team folders mean the whole team has instant access.
Google Workspace admins can configure default Drive save locations, enforce signing templates, manage API keys centrally, and view signing activity across the whole organisation.
Signers receive a secure link by email and sign in their browser — no SignBolt account, no Google account, and no app install required on their end.
Every signing event — opened, signed, declined — is recorded with IP address, timestamp, and user agent. Downloadable audit certificates are available for compliance needs.
Google Workspace admins get centralised control over how SignBolt is used across the organisation. Set default behaviours, manage API keys, and view signing activity without asking individual users.
SignBolt fires these events to your webhook endpoint. Use them to trigger Drive uploads, Sheets logging, or other Workspace automations.
document.signedFires when all required signers have completed signing. Payload includes document ID, signer email, timestamp, and a download URL. Triggers the Drive save automatically.
document.viewedFires when a recipient opens the signing link from Gmail or email. Use this to log activity in Google Sheets or trigger a follow-up reminder workflow.
document.declinedFires when a recipient declines to sign. Route the document to a 'Declined' folder in Drive and notify the sender automatically.
Step-by-step instructions for your Workspace admin to deploy SignBolt across Gmail, Docs, and Drive.
Log in to your SignBolt Business dashboard. Navigate to Settings → API Keys and generate a key for your organisation. Store it as SIGNBOLT_API_KEY in your Apps Script project properties or server environment.
In Google Apps Script, create a new project and paste the Gmail add-on code below. This creates a sidebar that appears when users open emails with PDF attachments. Deploy it as a Workspace add-on from the Apps Script editor and install it domain-wide from the Google Admin console.
// Google Workspace Add-on: Gmail sidebar (Apps Script)
// Triggered when user opens an email with a PDF attachment
function onGmailMessage(e) {
const accessToken = e.gmail.accessToken;
const messageId = e.gmail.messageId;
// Fetch the attachment
GmailApp.setCurrentMessageAccessToken(accessToken);
const message = GmailApp.getMessageById(messageId);
const attachments = message.getAttachments({ includeInlineImages: false });
const pdfAttachment = attachments.find(
(a) => a.getContentType() === "application/pdf"
);
if (!pdfAttachment) {
return CardService.newCardBuilder()
.addSection(
CardService.newCardSection().addWidget(
CardService.newTextParagraph().setText("No PDF attachment found.")
)
)
.build();
}
// Build the signing card
const card = CardService.newCardBuilder()
.setHeader(CardService.newCardHeader().setTitle("Sign with SignBolt"))
.addSection(
CardService.newCardSection()
.addWidget(
CardService.newTextParagraph().setText(
`Ready to sign: ${pdfAttachment.getName()}`
)
)
.addWidget(
CardService.newTextButton()
.setText("Sign This Document")
.setOnClickAction(
CardService.newAction()
.setFunctionName("openSignBoltSigning")
.setParameters({ fileName: pdfAttachment.getName() })
)
)
)
.build();
return card;
}Set up your webhook URL in the SignBolt dashboard to receive document.signed events. The SignBolt Google Workspace webhook endpoint at /api/integrations/google-workspace/webhook handles these events and can trigger Drive uploads, Sheets logging, or other automations. Below is the full event payload structure:
// SignBolt fires this payload to your webhook URL
// when a document initiated from Gmail or Docs is signed
{
"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": "Consulting_Agreement_Signed.pdf",
"metadata": {
"source": "gmail",
"gmailMessageId": "18e9f1a2b3c4d5e6",
"driveFolderId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms",
"workspaceDomain": "yourcompany.com"
}
}In your SignBolt Business dashboard, set the default Google Drive folder ID for signed document storage and upload your organisation logo. The logo will appear on all signed PDFs sent from your Workspace domain.
If your team runs on Gmail, Docs, and Drive, adding a separate e-signature tool breaks their flow. SignBolt keeps signing inside the apps they already use.
Send quotes and contracts for signature directly from Gmail. Signed copies land in the client's shared Drive folder automatically. No CRM required.
Distribute employment offers, NDAs, and policy acknowledgements via Gmail. Collect signatures and auto-archive completed documents in Drive.
Route agreements through Gmail-based approval flows. Every signed document carries a full audit trail and is stored in a structured Drive folder hierarchy.
Approve purchase orders, vendor agreements, and service contracts without leaving Google Workspace. Signed PDFs feed directly into your Drive-based filing system.
Send client agreements as Gmail attachments, collect signatures via SignBolt, and deliver completed contracts to a shared Drive folder the client can access.
Collect consent forms, enrolment documents, and grant agreements via Gmail and store signed copies in Shared Drives for the whole team.
API access, webhook events, admin controls, custom branding, and unlimited documents — everything needed for full Google Workspace integration — is included in the Business plan.
The Business plan ($24/mo) includes API access, webhook support, admin controls, custom branding, and the infrastructure required for team-wide Google Workspace integration.
The integration uses the SignBolt REST API and webhooks. The Gmail sidebar experience is built using Google Workspace Add-ons (Apps Script), which your Workspace admin deploys from the Admin console. A formal Marketplace listing is on the roadmap.
No. Recipients receive a secure signing link by email and complete the process in their browser. No account of any kind is required on their end.
Yes. Workspace admins can set a default Google Drive folder for all signed documents across the organisation. Individual users can override this for their own documents if the admin permits.
The SignBolt sidebar in Gmail reads the attachment using Google's Gmail API (with the user's OAuth consent), sends it to the SignBolt API for signing, and saves the completed PDF back to Drive. The user never leaves Gmail.
Yes. The SignBolt add-on lets you insert signature request fields into a Google Doc via the sidebar. The document is exported to PDF, sent for signing via the SignBolt API, and the signed PDF is saved back to Drive.
SignBolt signs all outgoing webhooks using HMAC-SHA256 with your SIGNBOLT_WEBHOOK_SECRET. The signature is included in the X-SignBolt-Signature header. Requests that fail validation are rejected with a 401 response.
Yes. The Business plan includes custom branding. Upload your logo in the SignBolt dashboard and it will appear on all signed PDFs sent from your organisation — including those initiated from Gmail or Google Docs.
More integrations to fit your workflow.
Start with the Business plan and have your team signing from Gmail and Docs today. The REST API is documented, the webhook endpoint is live, and admin setup takes under an hour.