Available
VaseSign Built
Subscription

Google Workspace

Publisher: VaseSign • Category: Google Workspace • Type: Native Connector

Overview

Use VaseSign with Google Workspace to browse My Drive, import PDFs and Word files, export Google Docs to PDF for signing, and write signed PDFs, certificates and audit trails back to Drive. Optional Gmail envelope notifications and Calendar deadline events are available only when your deployment enables those features and users grant the additional OAuth scopes.

Best-fit use cases

  • Sales contracts
  • Supplier onboarding
  • Customer consent
What this connector can do
  • Create signing request
  • Send document for signature
  • Track envelope status
  • Save signed PDF
  • Save audit trail
  • Trigger Workflow Manager workflow
Events and triggers
  • envelope.created
  • envelope.sent
  • envelope.viewed
  • envelope.signed
  • envelope.completed
  • envelope.declined
Data accessed & authentication

Data accessed

  • Documents
  • Attachments
  • Contacts
  • Metadata
  • Audit events
  • Webhook status

Auth methods

  • OAuth 2.0
  • Webhook Signing Secret
Workflow Manager support

Workflow IDs: N8N-GOOGLE-WORKSPACE-01

  • Google Workspace agreement completion sync: Create signing request from source record and write completed package back.
  • Google Workspace reminder and escalation: Notify stakeholders when signatures remain pending.
Installation steps
  1. Select workspace
  2. Review connector details
  3. Review permissions and data accessed
  4. Authenticate with provider
  5. Configure field mapping
  6. Configure document template mapping
  7. Configure event triggers
  8. Run test connection
  9. Activate connector
Governance and trust

Designed to support ECTA-aligned signing workflows.

POPIA-aligned controls depend on tenant configuration, data routing and subprocessors.

eIDAS-aware architecture for future regional and assurance-level expansion.

Connector permissions should be reviewed by a workspace administrator before activation.

Legal suitability depends on document type, identity controls and organisational policy.