Google Drive to TurboDocx e-Signature (n8n Workflow)

Send Google Drive documents for TurboDocx e-signature—and automatically save the signed PDF back to Drive

This n8n workflow monitors a Google Drive “To Sign” folder, triggers TurboDocx e-signature using anchor-based signature and date fields, then uploads the completed signed PDF into a “Signed” folder (with “(signed)” added to the filename).

What this workflow does

• Watches a Google Drive folder for newly created files using the Google Drive Trigger.
• Loads your signer details and anchor tokens that match placeholders in your TurboDocx document template (e.g., {client_sig} and {client_date}).
• Downloads the new contract file from Google Drive and sends it to TurboDocx to prepare the e-signature request.
• Waits for TurboDocx completion by handling a TurboDocx webhook callback when all required signatures are collected.
• Downloads the signed PDF from TurboDocx using the document ID provided in the webhook payload.
• Uploads the signed PDF to Google Drive into your selected “Signed” folder, appending (signed) to the filename.

Use cases

• Turn contract intake into a hands-off process: drop files into “To Sign,” receive completed PDFs in “Signed.”
• Batch agreements for customers or vendors where each document must be signed using consistent anchor fields.
• Operations teams running SaaS or services that need an auditable, automated e-signature pipeline tied to Google Drive.

Technical details

• Google Drive Trigger: monitors a specified “To Sign” folder for new files.
• Google Drive: downloads the input document and uploads the signed output to the “Signed” folder.
• TurboDocx: submits the document for e-signature with anchor-based signature/date fields, then uses a TurboDocx webhook trigger to detect completion and retrieve the signed PDF.
• Includes supporting nodes like Sticky Note and Set to structure signer details and anchor token configuration.

Setup notes: Provide Google Drive OAuth2 credentials, select the source/destination folders, configure TurboDocx credentials (API key + organization ID with admin permissions for webhook registration), and update signer name/email plus signature/date anchor tokens to match your template placeholders.