Verified n8n community node

Google Forms e-signature in n8n

Turn every intake form into a signed document. When a Google Forms response arrives, the verified TurboDocx node builds the agreement, waiver, or NDA from your template, sends it for signature with TurboSign, and files the executed PDF to Google Drive, with no code and no per-seat e-signature add-on.

Verified by n8n on the official n8n integrations directory.

Google Forms is where a lot of real business starts: a new client fills out an intake form, an event attendee accepts a liability waiver, a contractor submits their details, a partner requests an NDA. The problem is what happens next. Someone reads the response, opens a template, retypes the answers, exports a file, attaches it to an email, and chases the signature by hand. That manual gap is where deals stall and where copy-paste mistakes creep into legal documents. This page shows how to close the gap in n8n, so a form submission becomes a personalized, signed, and filed document with no one touching a keyboard in between.

Unlike a CRM flow, there is no deal stage here to lean on. The form response is the whole trigger, which means the value is in doing the rest in one pass. A signature-only tool would still need a separate step to build the document from the answers first, so you end up wiring Google Docs or a mail-merge node in front of it. The verified TurboDocx node generates the agreement and collects the signature through a single credential, so an intake form and a signed contract are the two ends of one short workflow.

It also keeps the paperwork where the rest of the response already lives. The signed PDF and its audit trail are filed straight back to Google Drive, in a folder you choose, named from the form answers. There is no separate signing portal to log into and no executed copy left sitting in someone's inbox.

The workflow, end to end

  • 1A respondent submits your intake form, and the Google Forms trigger starts the n8n workflow.
  • 2A Set or Code node shapes the answers, matching field names and formats to what your template expects.
  • 3The TurboDocx Generate Document operation merges those answers into your agreement, waiver, or NDA template and returns a finished DOCX or PDF.
  • 4The TurboSign Send Signature operation emails the document to the respondent and starts tracking status.
  • 5On the Document Signed event, Download Document fetches the executed PDF and a Google Drive node files it in the folder you choose.

Build it in four steps

Install the verified node

In n8n open Settings, then Community Nodes, click Install, and enter @turbodocx/n8n-nodes-turbodocx. It is verified for installation on n8n Cloud, so it installs directly with no self-hosting.

Trigger on a new response

Add the Google Forms trigger that fires when a new response is submitted, then a Set or Code node to shape the answers into the fields your template needs.

Generate the document

Add a TurboDocx node with the Generate Document operation, pick your agreement or waiver template, and map the form answers to the template variables.

Send and file the signed copy

Send the document with TurboSign Send Signature. On the Document Signed trigger, download the executed PDF and upload it to Google Drive.

From intake to signed document in one flow

A signature-only tool still needs a separate document generator sitting in front of the form. The verified TurboDocx node builds the document from your template and collects the signature through a single credential, so a raw form answer becomes a personalized, signed agreement without leaving n8n or reconciling two vendors.

That difference matters most on intake forms, because the document body has to change with every response. A waiver names the participant and the activity. An NDA names the counterparty and the effective date. A service agreement lists the plan the respondent selected. A signature-only tool cannot vary that body, so it forces you to generate the file somewhere else first and then hand it over. With TurboDocx the Generate Document step reads the shaped form answers, writes them into the exact places your template defines, and passes the finished file straight to TurboSign in the same run. You maintain one credential, one template, and one workflow, and the respondent receives a document that reads as if it were drafted just for them.

  • Build a personalized agreement, waiver, or NDA from every form answer, no manual editing.
  • Send, track, remind, and download the signed PDF from the same node.
  • The Document Signed event files the executed copy to Google Drive automatically.

Frequently asked questions

How do I turn a Google Forms response into a signed document in n8n?

Use the Google Forms trigger in n8n to start the workflow when a new response arrives. A Set or Code node shapes the answers into the fields your template expects, the TurboDocx Generate Document operation builds the agreement, and the TurboSign Send Signature operation emails it to the respondent. Every step is a drag-and-drop node, so no code is required.

Can the signed PDF be filed to Google Drive automatically?

Yes. When the respondent signs, the TurboDocx trigger fires a Document Signed event. Your workflow then uses the TurboSign Download Document operation to retrieve the executed PDF and a Google Drive node to upload it to the folder you choose, so the signed copy is filed with no manual download or upload.

What kinds of documents can I generate from a form response?

Any document you can build from a TurboDocx template works, such as a liability waiver, an NDA, a service agreement, a consent form, or an intake contract. The form answers map to the variables in the template, so a single intake form can drive a fully personalized document for every respondent.

Is the TurboDocx n8n node verified for n8n Cloud?

Yes. TurboDocx publishes @turbodocx/n8n-nodes-turbodocx as a community node verified for installation on n8n Cloud. You install it from Settings, Community Nodes, with no self-hosting required, and it also runs on self-hosted n8n.

Which form answers can I merge into the document?

Any answer the Google Forms trigger returns, such as name, email, date, address, and any short or long text response, can be mapped to the variables in your TurboDocx template. Shape the answers in n8n first with a Set or Code node so their names and format match what the template expects.

Automate Google Forms agreements in n8n

Install the verified TurboDocx node, connect Google Forms, and turn every response into a signed document filed to Drive without leaving your workflow.

Get started free