n8n E-Signature with the Verified TurboSign Node
The verified TurboDocx n8n node sends and tracks TurboSign e-signature requests inside n8n, with no code. Prepare a document for review, send it for signature, track status, download the signed PDF, void or resend, and let signing events trigger the next step of any workflow.
Verified by n8n on the official n8n integrations directory.
This is the capability reference for e-signature in n8n. It covers what the TurboSign operations and trigger events actually are, why a verified node matters, and where the executed document ends up. If you want a full build, jump to the step-by-step guides further down. If you want to know exactly what the node can do before you wire anything up, you are in the right place.
The e-signature operations
Each operation is a drag-and-drop action on the TurboDocx node with typed fields. Together they cover the full signing lifecycle, from staging a draft to pulling back the executed PDF.
Prepare document for review
Stage a generated or uploaded file as a draft signature request so a person can eyeball it before it goes out. Useful when a workflow should pause for a human check ahead of dispatch.
Send signature request
Dispatch the document to one or more recipients with their signing anchors mapped. TurboSign emails each signer and returns a request id you use to track everything that follows.
Get and track status
Read the current state of a request on demand: who has viewed, who has signed, and whether it is completed. Handy for a scheduled check or a branch that decides what to do next.
Download signed PDF
Retrieve the executed PDF and its signature audit trail once every party has signed, then file it to Drive, SharePoint, a CRM record, or wherever the rest of the workflow sends it.
Void request
Cancel a request that is no longer valid, for example when a deal falls through or a document was sent in error. Voiding stops any further signing on that request.
Resend email
Send the signing invitation again to a recipient who lost or never opened it, without creating a duplicate request. This is the building block for a reminder or chase lane.
The TurboDocx trigger events
A trigger starts a workflow the instant something happens to a signature request. You pick one of these events, and the next step fires on the signing event itself, so there is no polling loop to build or maintain.
The request has been dispatched to recipients. Use it to log the send or post to a channel.
A recipient opened the document. Handy for engagement tracking and follow-up timing.
A signature was captured on the document. Often the cue to move the workflow forward.
A specific recipient completed their part, useful in multi-party flows where order matters.
Every party has signed. The usual point to download the executed PDF and update systems.
The document could not be finalized. Branch here to alert someone and recover gracefully.
The request was cancelled. Use it to reconcile records and close out the tracking row.
Why a verified node beats a bolt-on signature tool
Most n8n signing setups pair a signature-only vendor with a separate document generator. That means two credentials, two sets of billing, and glue steps to move a file from the generator into the signer. TurboDocx generates the document and sends it for signature through a single credential, so the whole job lives in one authenticated node.
- One credential generates the document and sends it for signature
- The document body varies per recipient from your template
- Verified for installation on n8n Cloud, nothing to self-host
- Signing events trigger the next step natively
- Two vendors, two credentials, two bills to reconcile
- Glue steps to hand a file from the generator to the signer
- Cannot produce a true per-recipient agreement on its own
- Status and signing events are stitched together by hand
A short example flow
Here is how the operations and triggers fit together in one workflow. This is a reference shape, not a tutorial. For the click-by-click build, see the guides below.
- 1A record is marked ready in your CRM, database, or spreadsheet and triggers the workflow.
- 2TurboDocx generates the agreement from your template through the same credential.
- 3The send signature request operation dispatches it to the signer with anchors mapped.
- 4The get and track status step, or a scheduled resend, keeps the request moving.
- 5The Document Completed trigger fires and the download signed PDF operation files the executed copy.
Step-by-step guides
Ready to build one? These walkthroughs turn the operations and triggers above into working workflows, start to finish.
Complete guide to eSignature automation with n8n and TurboSign
The end-to-end tutorial: build a full signing workflow from scratch.
Read the guiden8n e-signature from Airtable, filed back to Google Drive
Read Airtable rows, generate a contract per row, send, chase, and file signed PDFs.
Read the guiden8n e-signature from Excel with a Slack approval step
Route a spreadsheet-driven agreement through Slack approval before it is sent.
Read the guideFrequently asked questions
What e-signature operations does the TurboDocx n8n node expose?
The node exposes the TurboSign signing lifecycle as no-code operations: prepare a document for review, send a signature request, get and track request status, download the signed PDF, void a request, and resend the signing email. Each operation maps to a typed n8n field set, so you build the whole signing flow without touching the API.
Which TurboDocx trigger events can start the next step of a workflow?
The TurboDocx trigger fires on real signing events: Document Sent, Document Viewed, Document Signed, Document Recipient Signed, Document Completed, Document Finalization Failed, and Document Voided. You pick the event and the workflow continues the instant it happens, so you do not need a polling loop to react to a signature.
Why use a verified node instead of bolting a signature tool onto a separate document generator?
TurboDocx generates the document and sends it for signature through one credential, so a single node covers both halves of the job. A signature-only tool cannot vary the document body per recipient, which forces you to stitch a separate generator in front of it and manage two vendors and two sets of credentials. One verified node keeps generation and signing in the same authenticated workflow.
Do I need to write code to send documents for signature in n8n?
No. Every e-signature operation and trigger is available as a drag-and-drop n8n node with typed fields, so you send, track, and settle signature requests visually. You add a TurboDocx API credential once, and no API knowledge is required after that.
Where can I find step-by-step e-signature workflow guides?
This page is the capability reference for the node. For full walkthroughs, see the complete guide to e-signature automation with n8n and TurboSign, the Airtable to Google Drive contract flow, and the Excel to Slack approval flow. Each guide builds a working workflow end to end using the operations and triggers described here.
Explore more
Send your first signature request from n8n
Install the verified TurboDocx node, add your API key, and generate, send, and track e-signatures inside your n8n workflows with no code.