n8n signature webhooks
Stop polling for status. The verified TurboDocx trigger node starts an n8n workflow the moment a document is sent, viewed, signed, completed, or voided, so the next step runs the instant the signing event happens, with no code.
Verified by n8n on the official n8n integrations directory.
Most automations treat a signature as something you have to go and check for. You send a document, then a scheduled job asks "is it signed yet?" every few minutes, burning executions and still reacting late. A signing event is the opposite: TurboSign tells n8n the instant something happens, and the workflow runs once, immediately, with the document details already in hand.
That is what the TurboDocx trigger node gives you. It registers a webhook with TurboSign for the events you care about and hands each one to your workflow, verified as genuine before a single downstream node fires. This is the piece a signature-only tool bolted onto a separate generator usually cannot give you cleanly: the signing lifecycle and the document live in the same place, so the event payload already knows which document, which recipients, and which template it came from.
Practically, that means the write-back half of every signing workflow becomes trivial. Instead of a rep remembering to download the executed PDF and update the record, the Document Completed event does it, every time, the moment the last party signs.
Every signing event you can react to
Select one or several on a single trigger. Each event carries the document payload, so the next node knows exactly what to act on.
signature.document.sentLog the send, start an SLA timer, or notify the account owner that the contract went out.
signature.document.viewedNudge sales when a prospect opens the contract, or update the CRM engagement timeline.
signature.document.recipient_signedTrack partial progress on a multi-party agreement and remind the parties still outstanding.
signature.document.signedKick off the next step the instant a signature lands.
signature.document.completedEveryone has signed: download the executed PDF, file it, and update the record. Run the finish step once, here.
signature.document.voidedReopen the deal, flag the opportunity, or alert the owner that the contract was voided.
signature.document.finalization_failedCatch failures immediately and route them to a person instead of letting a contract stall silently.
Set it up 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.
Add the TurboDocx Trigger
Start a new workflow with the TurboDocx Trigger node and connect your TurboDocx API credential. n8n provides the webhook URL; the node registers it for you.
Pick the events
Select one or several signing events to listen for, such as Document Signed or Document Completed. The node verifies each incoming webhook is genuinely from TurboSign before your workflow runs.
Build the reaction
Connect the next nodes: download the executed PDF, update a CRM, post to Slack, file to Drive, or chain another TurboDocx operation. The event payload carries the document details.
Frequently asked questions
How do I trigger an n8n workflow when a document is signed?
Add the TurboDocx Trigger node to a new workflow and select the Document Signed event. The verified node registers a webhook with TurboSign, so the moment a signer completes the document, TurboSign calls n8n and your workflow runs. There is no polling and no code; you just pick the event and connect the next node.
Which signing events can start a workflow?
The TurboDocx Trigger fires on seven TurboSign events: Document Sent, Document Viewed, Document Recipient Signed, Document Signed, Document Completed, Document Voided, and Document Finalization Failed. You can select one or several on a single trigger, so one workflow can react to the whole signing lifecycle or just the moment you care about.
What is the difference between Document Signed and Document Completed?
Document Recipient Signed fires when one signer finishes, Document Signed fires for the signature itself, and Document Completed fires when every required party has signed and the document is fully executed. For a multi-party contract, use Document Completed to run the final step, such as filing the executed PDF, so it only runs once everyone is done.
Are the webhooks secure?
Yes. TurboSign signs each webhook call so the TurboDocx Trigger can verify it came from TurboDocx and was not tampered with before your workflow acts on it. The node handles that verification for you, so you are not building signature checking by hand.
Do I need to host anything to receive the webhooks?
No. The TurboDocx node is verified for installation on n8n Cloud, and n8n provides the webhook URL. Install the node from Settings, Community Nodes, add your TurboDocx credential, and the trigger registers and receives events on its own. It also runs on self-hosted n8n.
Related
The full verified TurboDocx node: document generation, e-signature, quoting, and triggers.
Every TurboSign operation the node exposes, from send to download.
A recipe that uses the Document Signed trigger to close the opportunity and file the PDF.
Generate the document that later triggers these signing events.
React to signatures in real time
Install the verified TurboDocx node, add the trigger, and let every signing event drive the next step of your n8n workflow automatically.
Get started free