n8n bulk e-signature from Google Sheets
Send 200 agreements from a spreadsheet without touching 200 documents. Point n8n at a Google Sheet, and the verified TurboDocx node loops over every row, generates a personalized document from your template, and sends it for signature with TurboSign. As each recipient signs, the signed status is written straight back to the row, no copy-paste mail merge and no per-seat e-signature add-on.
Verified by n8n on the official n8n integrations directory.
Some documents go out one at a time, tied to a single deal. Plenty of others go out by the hundred: renewal notices to every customer, offer letters to a new cohort of hires, NDAs to a list of vendors, waivers to every registrant. The data for all of them already lives in a spreadsheet, one row per person, one column per field. The painful part has never been the data. It is turning that sheet into hundreds of individual, correctly personalized documents, getting each one to the right inbox, and then knowing who actually signed.
This workflow treats the spreadsheet as the source of truth and works down it row by row. n8n reads the sheet, loops over the rows with Split In Batches, and for each row the TurboDocx Generate Document operation merges that row of fields into your template. Because the loop hands the node a single row at a time, every document is personalized to exactly one recipient: their name, their amount, their dates, their terms. The TurboSign Send Signature operation then emails that document to the recipient address in the same row, so the person the document is about is always the person who receives it. Nobody re-types a name into a Word file, and nobody sends the Johnson contract to the Smith address.
The part a traditional mail merge never handled is the return trip, and that is where the sheet earns its keep. When a recipient finishes signing, the TurboDocx trigger fires a Document Completed event, and a Google Sheets node writes the signed status, the completion date, and a link to the executed document back onto that exact row. The rows that stay blank are your outstanding signers, so the same sheet you sent from becomes your live tracker. You follow up on the handful still open instead of reconciling a folder of files against a list by hand, and the whole batch is visible in one place from send to signed.
The workflow, end to end
- 1A Google Sheets trigger fires on new rows, or a scheduled or manual run reads a sheet where each row is one recipient with the fields their document needs.
- 2A Split In Batches node loops over the rows so the workflow handles one recipient at a time.
- 3For the current row, the TurboDocx Generate Document operation merges that row of fields into your template and returns a finished DOCX or PDF personalized for that recipient.
- 4The TurboSign Send Signature operation emails that document to the recipient address from the same row and starts tracking status.
- 5On the Document Completed event, a Google Sheets node writes the signed status and a link back to that row, and optionally files the executed PDF to Google Drive.
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.
Read the sheet and loop
Add a Google Sheets trigger for new rows, or a scheduled run that reads the recipient sheet, then a Split In Batches node so the workflow processes one row at a time.
Generate a document per row
Inside the loop add a TurboDocx node with the Generate Document operation, pick your template, and map the columns of the current row to the template variables.
Send, then write status back
Send each document with TurboSign Send Signature to the address from the same row. On the Document Completed trigger, update that row with the signed status and a link to the executed document.
One loop for generate, send, and track
A copy-paste mail merge stops at a stack of files. You still send each one, chase the signatures, and record who signed by hand. The verified TurboDocx node runs the whole batch inside one loop: generate the document, send it for signature, and write the outcome back to the row, so the same sheet you started from ends up showing exactly who has signed and who has not.
- Generate one personalized document per row, no manual editing.
- Send each one to the recipient address from the same row automatically.
- Signing writes the status and a document link straight back to the sheet.
Frequently asked questions
How do I send documents for signature in bulk from a Google Sheet in n8n?
Point a Google Sheets trigger or a scheduled run at a sheet where each row is one recipient. n8n loops over the rows with the Split In Batches node, and for every row the TurboDocx Generate Document operation builds a personalized document from that row of fields and the TurboSign Send Signature operation emails it to that recipient. One sheet of 200 rows becomes 200 personalized documents out for signature, and every step is a drag-and-drop node, so no code is required.
How does the workflow track who has and has not signed?
The sheet is the source of truth. When a recipient finishes signing, the TurboDocx trigger fires a Document Completed event, and a Google Sheets node updates that recipient row with the signed status, the completion date, and a link back to the executed document. Rows that stay blank are the people who have not signed yet, so you can see the whole batch at a glance and follow up on only the outstanding ones.
How is this different from a mail merge in Google Docs or Word?
A classic mail merge produces a stack of documents, but you still have to send each one, chase the signatures, and record who signed by hand. This workflow closes that loop: it generates each document, sends it for signature, and writes the result back to the row automatically. You get personalization per row plus tracking and collection, not just a folder of files you now have to distribute yourself.
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.
Can I personalize each document with fields from the spreadsheet row?
Yes. Every column in the row maps to a variable in your TurboDocx template, so each recipient gets a document with their own name, amount, dates, and terms. Because the loop processes one row at a time, the Generate Document operation sees only that row of fields, and the recipient email for the Send Signature operation comes from the same row, so personalization and delivery always stay in sync.
Related
The full verified TurboDocx node: document generation, e-signature, quoting, and triggers.
Every TurboSign operation and signing trigger event the node exposes.
How the Generate Document operation turns template plus data into a finished file.
The same row-driven pattern, sending signatures from an Airtable base instead of a sheet.
Send your whole spreadsheet for signature
Install the verified TurboDocx node, connect Google Sheets, and turn every row into a personalized document that is generated, signed, and tracked without leaving your workflow.
Get started free